[MacPorts] #47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused ----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+--------------------- 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? -- Ticket URL: <https://trac.macports.org/ticket/47080> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: fixed | Keywords: Port: | -----------------------------+--------------------- Changes (by dluke@…): * status: new => closed * resolution: => fixed Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+---------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Changes (by dluke@…): * status: closed => reopened * resolution: fixed => Comment: 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- cf__metadata.shm): (22) Invalid argument -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+---------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Comment (by dluke@…): 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) -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+---------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Changes (by dluke@…): * cc: jmr@… (added) Comment: May be related to http://bugs.squid-cache.org/show_bug.cgi?id=3805 ? jmr? -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Changes (by dluke@…): * status: reopened => closed * resolution: => worksforme Comment: ... 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. -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Comment (by 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]. -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Comment (by dluke@…): Replying to [comment:6 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. -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Comment (by jmr@…): I don’t think ipcs will show posix segments, only sysv ones? -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Comment (by dluke@…): Replying to [comment:8 jmr@…]:
I don’t think ipcs will show posix segments, only sysv ones?
yep, that's right. mystery solved (pbkac) -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Comment (by 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 [[BR]]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? -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Comment (by 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. -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X
#47080: Fetching distfile failed: Failed to connect to geeklair.net port 3690: Connection refused -----------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: closed Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: worksforme | Keywords: Port: | -----------------------------+--------------------- Changes (by ryandesign@…): * cc: supercalbu@… (added) Comment: Replying to [comment:11 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. -- Ticket URL: <https://trac.macports.org/ticket/47080#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts