ghostscript@9.52: Failed to fetch ghostscript: Connection timed out after 30006 milliseconds

[brislawn]

Connection timeout failures happen for ghostpdl-9.52.tar.gz at all mirror sites, and also happen during attempts to manually download the file from http://distfiles.macports.org/ghostscript/ using Firefox.  30 seconds isn't nearly enough time; I am stuck working from home on a slow internet connection. I'm only getting a bit over 10% downloaded before the connections time out and start over at a different mirror site.

I have attached 

/opt/macports/var/macports/logs/_opt_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_print_ghostscript/ghostscript/main.log

Thanks,
Chris Brislawn

[brislawn]

log file

[Dave-Allured (Dave Allured)]

Two mirrors worked fine for me on the first try. This included the first mirror in your list. I think you had temporary connection problems at your end. Please try again and let us know if we can close this ticket.

You can test this problem outside of Macports from the command line. Get the URL and file name from main.log, then try downloading manually in a temporary directory:

curl -O -R -L http://aus.us.distfiles.macports.org/macports/distfiles/ghostscript/ghostpdl-9.52.tar.gz

[brislawn]

Dave, thanks for responding. "port clean ghostscript" and "port install ghostscript" still fails for new, unintelligible reasons, but I now think it may be a proxy/firewall issue, although I have no idea why this is happening.

I originally set up Macports in my office, inside an institutional firewall, and macports has been insisting I continue to use the same proxy settings even though I've been working at home for months. I have been running macports commands through a VPN tunnel to work, which has seemed to succeed until this ghostscript issue. Your command line approach also failed until I shut down the VPN tunnel and forced macports to retrieve the ghostpdl file without routing through the institutional firewall. Now that the file is downloaded and relocated I have *restarted* VPN and am continuing with the build.

If these sorts of problems persist I may give up at some point, uninstall everything, and reinstall macports outside of the firewall.

Thanks for your help. You can close this ticket.

-Chris Brislawn

[Dave-Allured (Dave Allured)]

Yeah, that working at home thing. Me too. ;-)

If curl fails consistently, you have enough evidence to file a help request with your corporate network support team. If they tell you anything interesting, please let us know. Good luck.

I lack ticket closing privileges, so this awaits a Macports magician. ;-)

[jmroot (Joshua Root)]

The 30-second timeout, by the way, is not for the transfer itself but for just establishing the connection. If that timeout is reached, it's most likely because it's not possible to establish a connection at all, but no response is being received. Your suspicion of proxy/firewall issues is reasonable.

Be aware that MacPorts can get proxy settings from the environment, from System Preferences, or from macports.conf - see proxy_override_env in the ​macports.conf man page.