Relay has Low Consensus and No Exit Flag Following Upgrade
Hello, I recently upgraded my tor exit relay's tor version to 0.2.8.12. The uptime is 51 days and it has valid, running and stable flags. However, it no longer has the exit node flag and the consensus is very low (20). It also is not listed as a directory. I suspect something else during the upgrade has broken it as I had some SELinux issues binding to the ports before - which I resolved. There are no errors in ARM although the log is non existent? - permissions error? The fingerprint is 575F2C60045805ABFDB2B7D7A78982F9571BC277 Where should I start to fix this? Best Wishes, Chris -- Protect your privacy: encrypt your communications GPG: CF7F98B2
I recently upgraded my tor exit relay's tor version to 0.2.8.12.
The uptime is 51 days and it has valid, running and stable flags.
However, it no longer has the exit node flag and the consensus is very low (20). It also is not listed as a directory.
I suspect something else during the upgrade has broken it as I had some SELinux issues binding to the ports before - which I resolved.
There are no errors in ARM although the log is non existent? - permissions error?
The fingerprint is 575F2C60045805ABFDB2B7D7A78982F9571BC277
Where should I start to fix this?
Your relay is not measured by tor's bandwidth authorities (this is unusual for a relay with such an uptime). Unmeasured relays have a very low consensus weight. https://raw.githubusercontent.com/ornetstats/stats/master/o/unmeasured_relay... https://onionoo.torproject.org/details?fingerprint=575F2C60045805ABFDB2B7D7A... -- https://mastodon.social/@nusenu https://twitter.com/nusenu_
Why is that? Perhaps they tried to measure and it failed? On 7 May 2017 2:39 p.m., "nusenu" <nusenu-lists@riseup.net> wrote:
I recently upgraded my tor exit relay's tor version to 0.2.8.12.
The uptime is 51 days and it has valid, running and stable flags.
However, it no longer has the exit node flag and the consensus is very low (20). It also is not listed as a directory.
I suspect something else during the upgrade has broken it as I had some SELinux issues binding to the ports before - which I resolved.
There are no errors in ARM although the log is non existent? - permissions error?
The fingerprint is 575F2C60045805ABFDB2B7D7A78982F9571BC277
Where should I start to fix this?
Your relay is not measured by tor's bandwidth authorities (this is unusual for a relay with such an uptime). Unmeasured relays have a very low consensus weight.
https://raw.githubusercontent.com/ornetstats/stats/master/o/ unmeasured_relays.txt
https://onionoo.torproject.org/details?fingerprint= 575F2C60045805ABFDB2B7D7A78982F9571BC277&fields=measured
-- https://mastodon.social/@nusenu https://twitter.com/nusenu_
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Sun, May 07, 2017 at 02:20:42PM +0100, Chris wrote:
However, it no longer has the exit node flag and the consensus is very low (20). It also is not listed as a directory.
I suspect something else during the upgrade has broken it as I had some SELinux issues binding to the ports before - which I resolved.
There are no errors in ARM although the log is non existent? - permissions error?
My first thought is that you somehow changed your identity key during the upgrade, meaning you're now a new relay (waiting to be measured). --Roger
The update was over 30 days ago. How long should I wait? C On 7 May 2017 4:59 p.m., "Roger Dingledine" <arma@mit.edu> wrote:
On Sun, May 07, 2017 at 02:20:42PM +0100, Chris wrote:
However, it no longer has the exit node flag and the consensus is very low (20). It also is not listed as a directory.
I suspect something else during the upgrade has broken it as I had some SELinux issues binding to the ports before - which I resolved.
There are no errors in ARM although the log is non existent? - permissions error?
My first thought is that you somehow changed your identity key during the upgrade, meaning you're now a new relay (waiting to be measured).
--Roger
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 8 May 2017, at 02:07, Chris Adams <chris@chrisada.co.uk> wrote:
The update was over 30 days ago. How long should I wait?
Your relay appears to be online at its IP address and ORPort. But it looks like you might have changed your torrc during the upgrade. (You said it used to have a DirPort, and it doesn't now.) Please check your logs for warnings: they are typically in /var/log/tor/log for Linux, but this does vary. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
participants (5)
-
Chris -
Chris Adams
-
nusenu -
Roger Dingledine -
teor