TCP non-blocking connect() error
Donahue, Gregory
Hello,
Recently, our IT group reconfigured the network hosting the server with our track files, changing the IP address. This has created a problem where Genome Browser can no longer recognize the name of the server, dodongo.pmacs.upenn.edu. See for example the custom tracks here:
https://genome.ucsc.edu/s/Gdonahue/Pourshafie%20CUT%2DN%2DRUN%20OE%20and%20Tau
If you look at the custom tracks for this session, you will see a list of errors. Clicking on “Show” for any of them produces an error pop-up dialog:
“TCP non-blocking connect() to dodongo.pmacs.upenn.edu IP 130.91.193.206 timed-out in select() after 10000 milliseconds - Cancelling! Couldn't open http://dodongo.pmacs.upenn.edu/legacy/Pourshafie/08172022_H3K9ac-IgG.PBS.OE.bw”
The IP it mentions is the previous IP. The new IP is 165.123.69.116. If I add tracks using that IP rather than the domain name, it works. Is this some kind of DNS caching error?
On second thought, it sounds similar to the problem described here: https://groups.google.com/a/soe.ucsc.edu/g/genome/c/hTubkt757Xc/m/sJhk8NTsVWwJ, and in many other issues searchable under “TCP non-blocking.” Could it be a port issue? Or do I simply have to ask our admins to allow connections from 128.114.119.*? But if that hasn’t been set correctly, how can Genome Browser load tracks using the IP and not the domain name?
Thanks for any help you can give,
Greg
Greg Donahue
The Berger and Zaret Labs
The Perelman School of Medicine
The University of Pennsylvania
Galt Barber
--
---
You received this message because you are subscribed to the Google Groups "UCSC Genome Browser Public Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genome+un...@soe.ucsc.edu.
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/CH0PR04MB8114C9E2088B9294439C13E2E4529%40CH0PR04MB8114.namprd04.prod.outlook.com.
Donahue, Gregory
Hi Galt, thanks much for the reply. It seems the problem has resolved itself, though I’m not sure how. I don’t think anyone on our end altered anything in the network config. Best, -G