Hi,
You are running a Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/72657B96BF99B28FBD9F2B036A590A...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Ideally you will switch to keeping up with our stable releases, but if you need a stable that is especially stable, the Tor 0.3.5 branch will be maintained until Feb 2022: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... and you can see the lifetimes of other Tor versions on that table too.
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
G'day Roger,
That was a fun morning! Managed to get that old VM up to Ubuntu 16.04, which you still have a repo for, and got tor upgraded on it :)
Though looks like the node may have been blacklisted due to the old tor version?
Oct 12 12:02:10 minbar Tor[12066]: http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '204.13.164.118:80'. Please correct. Oct 12 12:02:10 minbar Tor[12066]: http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '154.35.175.225:80'. Please correct. Oct 12 12:02:10 minbar Tor[12066]: http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '199.58.81.140:80'. Please correct. Oct 12 12:02:10 minbar Tor[12066]: http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '131.188.40.189:80'. Please correct. Oct 12 12:02:10 minbar Tor[12066]: http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '86.59.21.38:80'. Please correct. Oct 12 12:02:11 minbar Tor[12066]: http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '171.25.193.9:443'. Please correct.
Is that what these errors mean? If that's all it is, are you able to un-blacklist it please (Or should I email bad-relays? I was't sure if I should use this current thread or start a new one)? It's now running:
Tor 0.4.1.6 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g, Zlib 1.2.8, Liblzma 5.1.0alpha, and Libzstd N/A.
Hoping this is new enough? If not, I can try taking it up to ubuntu 18.04, but that may be problematic as it's living on a VERY old xen host :D
Regarding bandwidth, I don't have any of the RelayBandwidth* setting configured in torrc - so had always just assumed it would be open slather. Do I need to specifically set these to 0? As long as it doesn't go nuts (aka saturate the gig ethernet into the host or affect paying customers on the segment), I don't really mind too much now much traffic it uses.
How often does the node status page update? ( https://metrics.torproject.org/rs.html#details/72657B96BF99B28FBD9F2B036A590...) It's been a few hours now since the timestamp at the bottom was updated, when I convert from UTC to local :)
Regards,
Damien
On Mon, 2 Sep 2019 at 18:15, Roger Dingledine arma@torproject.org wrote:
Hi,
You are running a Tor relay, which is great:
http://rougmnvswfsmd4dq.onion/rs.html#details/72657B96BF99B28FBD9F2B036A590A...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for your distro / OS here:
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Ideally you will switch to keeping up with our stable releases, but if you need a stable that is especially stable, the Tor 0.3.5 branch will be maintained until Feb 2022:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... and you can see the lifetimes of other Tor versions on that table too.
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
On Sat, Oct 12, 2019 at 12:08:02PM +1100, Damien Gardner wrote:
That was a fun morning! Managed to get that old VM up to Ubuntu 16.04, which you still have a repo for, and got tor upgraded on it :)
Awesome! Looks good, thanks.
Though looks like the node may have been blacklisted due to the old tor version?
Oct 12 12:02:10 minbar Tor[12066]: http status 400 ("Fingerprint is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver '204.13.164.118:80'. Please correct.
Yes, this is exactly what happened. We moved forward with the plan to remove the old relays: https://blog.torproject.org/removing-end-life-relays-network
Is that what these errors mean? If that's all it is, are you able to un-blacklist it please
Yes, I've started the process of unblacklisting the fingerprint. It will need a threshold of the directory authorities to pull the update, so it could be a couple of days until it takes effect, but hopefully it will be relatively soon.
You can go to the bottom of https://consensus-health.torproject.org/#relayinfo and paste in your fingerprint or nickname to see progress.
Hoping this is new enough? If not, I can try taking it up to ubuntu 18.04, but that may be problematic as it's living on a VERY old xen host :D
Hm. It looks based on https://ubuntu.com/about/release-cycle that you have another year and a bit until Ubuntu 16.04 goes dead.
So, that's plenty of time to plan ahead, especially if you start soon. :)
Regarding bandwidth, I don't have any of the RelayBandwidth* setting configured in torrc - so had always just assumed it would be open slather. Do I need to specifically set these to 0? As long as it doesn't go nuts (aka saturate the gig ethernet into the host or affect paying customers on the segment), I don't really mind too much now much traffic it uses.
Ok, sounds good, we'll see where it goes from here.
(It looks like the relay is located in Australia? That would explain why it isn't growing in usage as much as relays closer to the middle of the internet -- Tor tries to shift load toward relays that can handle it better than their peers, and the huge latencies to and from Australia make it harder to look good compared to the other relays.)
How often does the node status page update? ( https://metrics.torproject.org/rs.html#details/72657B96BF99B28FBD9F2B036A590...) It's been a few hours now since the timestamp at the bottom was updated, when I convert from UTC to local :)
I'm not sure how often exactly, but pretty often. Usually often enough that it is not the bottleneck at least. Once some directory authorities update things should start looking better.
Thanks! --Roger
network-health@lists.torproject.org
-
Damien Gardner -
Roger Dingledine