Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused

[ryandesign (Ryan Carsten Schmidt)]

The buildbot builders cannot fetch FTP files, e.g.:

--->  Attempting to fetch h3dutil-1.3.0.tar.gz from ftp://www.h3dapi.org/pub/releases/source/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0DEBUG: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused

Daniel, is this an issue with your server or with Mac OS Forge's configuration of the buildbot builders?

[danielluke (Daniel J. Luke)]

yep, looks like sometime recently (last squid3 update)? it decided it needed to store files in /opt/local/var/squid/cache/squid (which didn't exist) presumably instead of /opt/local/var/squid/cache/

for now, I've just created /opt/local/var/squid/cache/squid and restarted it.

[danielluke (Daniel J. Luke)]

oh, actually it's worse than that. After fixing that and getting it to generate cache files, squid is failing on startup with:

FATAL: Ipc::Mem::Segment::create failed to ftruncate(/squid-cfmetadata.shm): (22) Invalid argument

[danielluke (Daniel J. Luke)]

This may be an upstream squid but (see also ​http://lists.apple.com/archives/darwin-dev/2004/Dec/msg00066.html and ​http://stackoverflow.com/questions/25502229/ftruncate-not-working-on-posix-shared-memory-in-mac-os-x)

[danielluke (Daniel J. Luke)]

May be related to ​http://bugs.squid-cache.org/show_bug.cgi?id=3805 ? jmr?

[danielluke (Daniel J. Luke)]

... and it's started up now (I didn't change anything, just waited). ipcs didn't show a dangling shared memory segment, so I'm not sure what was causing it to fail.

[jmroot (Joshua Root)]

Squid doesn’t (usually) clean up the segments when it exits due to an error. So probably it exited because of the missing dir initially, then the ftruncate failed the next time it ran because the segment already existed and had already been truncated, which makes it unlink the segment. This is what I mentioned in ​http://bugs.squid-cache.org/show_bug.cgi?id=3805#c17.

[danielluke (Daniel J. Luke)]

Replying to jmr@…:

Squid doesn’t (usually) clean up the segments when it exits due to an error. So probably it exited because of the missing dir initially, then the ftruncate failed the next time it ran because the segment already existed and had already been truncated, which makes it unlink the segment. This is what I mentioned in ​http://bugs.squid-cache.org/show_bug.cgi?id=3805#c17.

That's what I thought at first, but I didn't see the segment in the listing from ipcs ... maybe I just missed it.

[jmroot (Joshua Root)]

I don’t think ipcs will show posix segments, only sysv ones?

[danielluke (Daniel J. Luke)]

Replying to jmr@…:

I don’t think ipcs will show posix segments, only sysv ones?

yep, that's right. mystery solved (pbkac)

[supercalbu@…]

Squid was working for me then I just tried running it again and it wouldn't start.

Now I get alternating when I run sudo ./squid -z ...

FATAL: Ipc::Mem::Segment::create failed to shm_open(/squid-cf__queues.shm): (13) Permission denied
FATAL: Ipc::Mem::Segment::create failed to ftruncate(/squid-cf__metadata.shm): (22) Invalid argument

Saw in one of the links above that it seems that was a fixed bug in main squid if I understand correctly. Does that need to be applied to the port?

[supercalbu@…]

Is there any work around for this? Squid was working when I first installed it then this happened. Tried uninstalling and reinstalling and it still happens.

[ryandesign (Ryan Carsten Schmidt)]

Replying to supercalbu@…:

Is there any work around for this? Squid was working when I first installed it then this happened. Tried uninstalling and reinstalling and it still happens.

This ticket is about a fetch failure involving Daniel's ftp proxy server, and is closed. Your question appears to be about the squid program, so that's not relevant to this ticket. Please ask your question on the macports-users mailing list, or if you believe there is a bug in one of our ports, file a new ticket in this issue tracker.