[tor-bugs] #8458 [Tor]: Received http status code 504 ("Gateway Time-out") from server '154.35.32.5:80' while fetching consensus directory.

[Tor Bug Tracker & Wiki]

#8458: Received http status code 504 ("Gateway Time-out") from server
'154.35.32.5:80' while fetching consensus directory.
-------------------------+--------------------------------------------------
 Reporter:  cypherpunks  |          Owner:               
     Type:  defect       |         Status:  new          
 Priority:  normal       |      Milestone:               
Component:  Tor          |        Version:  Tor: 0.2.3.25
 Keywords:               |         Parent:               
   Points:               |   Actualpoints:               
-------------------------+--------------------------------------------------
 Howdy,

 After restarting the server that hosts my Tor relay, I noticed that it's
 no longer publishing relay descriptors (i.e. entries on
 https://metrics.torproject.org/relay-search.html aren't being updated as
 they used to). I checked my tor logs and saw the following (with bits
 redacted):

 Mar 12 06:44:26.000 [notice] Tor 0.2.3.25 (git-3fed5eb096d2d187) opening
 log file.
 Mar 12 06:44:26.000 [notice] Parsing GEOIP file /usr/share/tor/geoip.
 Mar 12 06:44:26.000 [notice] Configured to measure statistics. Look for
 the *-stats files that will first be written to the data directory in 24
 hours from now.
 Mar 12 06:44:26.000 [notice] This version of OpenSSL has a known-good EVP
 counter-mode implementation. Using it.
 Mar 12 06:44:26.000 [notice] OpenSSL OpenSSL 1.0.1e 11 Feb 2013 looks like
 version 0.9.8m or later; I will try SSL_OP to enable renegotiation
 Mar 12 06:44:26.000 [notice] Your Tor server's identity key fingerprint is
 '[redacted]'
 Mar 12 06:44:27.000 [notice] Reloaded microdescriptor cache.  Found 7802
 descriptors.
 Mar 12 06:44:32.000 [notice] We now have enough directory information to
 build circuits.
 Mar 12 06:44:32.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network.
 Mar 12 06:41:06.000 [notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent. Publishing server descriptor.
 Mar 12 06:41:07.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop.
 Mar 12 06:41:07.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, with
 15 circuits open. I've sent 57 kB and received 49 kB.
 Mar 12 06:41:08.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
 Mar 12 06:41:09.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Mar 12 06:41:09.000 [notice] Bootstrapped 100%: Done.
 Mar 12 06:42:09.000 [notice] Self-testing indicates your DirPort is
 reachable from the outside. Excellent.
 Mar 12 06:42:18.000 [notice] Performing bandwidth self-test...done.
 Mar 12 08:06:33.000 [warn] Received http status code 504 ("Gateway Time-
 out") from server '154.35.32.5:80' while fetching "/tor/server/d/[several
 lines of hexadecimal redacted].z". I'll try again soon.
 Mar 12 12:41:07.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with
 488 circuits open. I've sent 13.72 GB and received 13.17 GB.
 Mar 12 16:14:30.000 [warn] Received http status code 504 ("Gateway Time-
 out") from server '154.35.32.5:80' while fetching consensus directory.
 Mar 12 16:14:30.000 [warn] Received http status code 504 ("Gateway Time-
 out") from server '154.35.32.5:80' while fetching consensus directory.
 Mar 12 18:09:23.000 [warn] Received http status code 504 ("Gateway Time-
 out") from server '154.35.32.5:80' while fetching
 "/tor/server/authority.z". I'll try again soon.
 Mar 12 18:41:07.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with
 613 circuits open. I've sent 31.99 GB and received 30.72 GB.

 The folks on oftc/#tor said to file a bug report here, even though it
 might be a transient network issue with one of the directory servers,
 because nobody's come up with an exact idea yet.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8458>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online