Running a packet analyzer on the remote site might also be more revealing than on the local site. He may be able to see relevant infos in system logs. not more than, say, 1% of the packets get lost), you should contact the remote server administrator to figure out what's wrong. If network congestion is not a problem (i.e. To rule out network congestion as a problem you could use a tool like mtr or traceroute or even ping to see if packets get lost to the remote site (see below though). You won't see much however except the packets reflecting exactly what the error message says. Debugging thisĪs suggested in the another answer, using a packet analyzer can help to debug the issue. It could in turn be the case that some of these hosts are misconfigured or overloaded and thus cause the aforementioned problems. It could however be the case that the DNS is configured to return different IP addresses on each request, which would connect you (DNS caching left aside) to different addresses hosts on each connection attempt. It is also not a (direct) DNS problem, that would cause another error ( Name or service not known or something similar).
It is possible that the packets travel fine in the one direction but get dropped (or misrouted) in the other. If it's occuring occasionally, it indicates that the other site has load problems or the network path to the other site is unreliable.Īlso, as it is a problem with the network, you cannot tell what happened on the other side. That said, it is probably not a problem in your script, but on the remote site. This is sometimes also caused by firewalls, sometimes by network congestion or heavy load on the remote (or even local) site.
In the context of urllib this may also mean that the HTTP response did not arrive in time. This usually means that either a firewall is actively denying the connection or the respective service is not started on the other site or is overloaded.Ĭonnection timed out: During the attempt to establish the TCP connection, no response came from the other side within a given time limit. Here are the status codes explained:Ĭonnection refused: The peer is not listening on the respective network port you're trying to connect to. Trying XXX.YY.ZZZ.telnet: Unable to connect to remote host: Connection timed out Trying XXX.YY.ZZZ.telnet: Unable to connect to remote host: Connection refused
I just tested with telnet, sometimes it succeeds, sometimes it doesn't, just like my Python. What should I do to debug and figure out where the issue is coming from? How can I tell if the endpoint has consumed my request and returned a response but never reached me? With telnet The above errors happen randomly, the script can run successfully the first time but then fails on the second run and vice versa. Return self.do_open(httplib.HTTPSConnection, req)įile "/usr/lib/python2.7/urllib2.py", line 1177, in do_open The trace of the failure is: Traceback (most recent call last):įile "/usr/lib/python2.7/urllib2.py", line 126, in urlopenįile "/usr/lib/python2.7/urllib2.py", line 400, in openįile "/usr/lib/python2.7/urllib2.py", line 418, in _openįile "/usr/lib/python2.7/urllib2.py", line 378, in _call_chainįile "/usr/lib/python2.7/urllib2.py", line 1215, in https_open Lately, there have been some random errors:
PYTHON ERROR ERRNO 110 CONNECTION TIMED OUT CODE
I have the following code that has worked for about a year: import urllib2
0 kommentar(er)
