On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
There are no errors in the logs, just notices that the relay is not in the cached consensus. Apart from upgrading to Tor v0.2.4.22 3 days earlier I haven't made any changes to the server.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
Thanks.
On 07/04/2014 04:06 PM, Steve Snyder wrote:
On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
You can view the directory authorities' consensus votes at https://consensus-health.torproject.org/. As you can see, gabelmoo, moria1, tor26, and urras don't consider your relay "Running".
Directory authorities determine if a relay is running by trying to open a TLS connection to the relay. As a first step in your investigation, maybe try to connect to these directory authorities from your relay (e.g. by downloading the consensus file from /tor/status-vote/current/consensus), and see if that gives any hints.
Benedikt
I'm getting 100% packet loss when pinging dizum and gabelmoo; no packet loss to the other authorities.
On 07/04/2014 10:42 AM, Benedikt Gollatz wrote:
On 07/04/2014 04:06 PM, Steve Snyder wrote:
On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
You can view the directory authorities' consensus votes at https://consensus-health.torproject.org/. As you can see, gabelmoo, moria1, tor26, and urras don't consider your relay "Running".
Directory authorities determine if a relay is running by trying to open a TLS connection to the relay. As a first step in your investigation, maybe try to connect to these directory authorities from your relay (e.g. by downloading the consensus file from /tor/status-vote/current/consensus), and see if that gives any hints.
I'm getting 100% packet loss when pinging dizum and gabelmoo; no packet loss to the other authorities.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 7/4/2014 7:06 AM, Steve Snyder wrote:
On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
There are no errors in the logs, just notices that the relay is not in the cached consensus. Apart from upgrading to Tor v0.2.4.22 3 days earlier I haven't made any changes to the server.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
Thanks. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Your OpenSSL is current?
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
On 07/04/2014 11:08 AM, Kurt Besig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 7/4/2014 7:06 AM, Steve Snyder wrote:
On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
There are no errors in the logs, just notices that the relay is not in the cached consensus. Apart from upgrading to Tor v0.2.4.22 3 days earlier I haven't made any changes to the server.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
Thanks. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Your OpenSSL is current?
Yes, v1.0.1h.
On Fri, Jul 04, 2014 at 10:06:51AM -0400, Steve Snyder wrote:
On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
There are no errors in the logs, just notices that the relay is not in the cached consensus. Apart from upgrading to Tor v0.2.4.22 3 days earlier I haven't made any changes to the server.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
Did you fix something? It seems to be running again:
https://atlas.torproject.org/#details/9BE67F8BE1B248994A30E4DEEB3EA00CCFBE9F... https://globe.torproject.org/#/relay/9BE67F8BE1B248994A30E4DEEB3EA00CCFBE9F0...
On 07/04/2014 11:59 AM, Matthew Finkel wrote:
On Fri, Jul 04, 2014 at 10:06:51AM -0400, Steve Snyder wrote:
On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
There are no errors in the logs, just notices that the relay is not in the cached consensus. Apart from upgrading to Tor v0.2.4.22 3 days earlier I haven't made any changes to the server.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
Did you fix something? It seems to be running again:
https://atlas.torproject.org/#details/9BE67F8BE1B248994A30E4DEEB3EA00CCFBE9F... https://globe.torproject.org/#/relay/9BE67F8BE1B248994A30E4DEEB3EA00CCFBE9F0...
Well, I rebooted the server. Apparently that counts as a fix.
On 07/04/2014 11:59 AM, Matthew Finkel wrote:
On Fri, Jul 04, 2014 at 10:06:51AM -0400, Steve Snyder wrote:
On June 9th my relay, which was established about 20 months ago, fell out of the cached consensus.
There are no errors in the logs, just notices that the relay is not in the cached consensus. Apart from upgrading to Tor v0.2.4.22 3 days earlier I haven't made any changes to the server.
Anyone know what's going on here?
https://exonerator.torproject.org/?targetaddr=&targetPort=&ip=5.9.19...
Did you fix something? It seems to be running again:
https://atlas.torproject.org/#details/9BE67F8BE1B248994A30E4DEEB3EA00CCFBE9F... https://globe.torproject.org/#/relay/9BE67F8BE1B248994A30E4DEEB3EA00CCFBE9F0...
No, you're looking at the wrong relay. Mine is Falcon, 874786AE2D973602041D4A1A145D2A8435C88B6F, not the one referenced above.
tor-relays@lists.torproject.org
-
Benedikt Gollatz -
Kurt Besig -
Matthew Finkel -
Steve Snyder