Upgrade your 'droideka' Tor relay?
Hi Damien, You are running a Tor exit relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/7B1807281CC74E54CC2144B87A78F5... But 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! 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
Hi, Thanks for letting me know, this should be fixed now (I'm now using the Tor package from Debian Buster). Is there a way to get automated warnings when that happens? I had unattended-upgrades set up on this machine, but due to an old /etc/apt/sources.list, I was stuck on an older Tor version. Best, Damien On Sat, Aug 31, 2019 at 08:32:32PM -0400, Roger Dingledine wrote:
Hi Damien,
You are running a Tor exit relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/7B1807281CC74E54CC2144B87A78F5...
But 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!
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
Hi Damien,
On 3 Sep 2019, at 07:12, Damien Desfontaines <tor-droideka@desfontain.es> wrote:
Thanks for letting me know, this should be fixed now (I'm now using the Tor package from Debian Buster). Is there a way to get automated warnings when that happens? I had unattended-upgrades set up on this machine, but due to an old /etc/apt/sources.list, I was stuck on an older Tor version.
That's a really good question. There used to be a service called Tor Weather, but we didn't have enough people to maintain it. It would email you when your relay was down or outdated. I think someone else runs a copy now. I don't know if we know them. Tor will also warn in its logs when your relay is out of date. T
On Mon, Sep 02, 2019 at 11:12:04PM +0200, Damien Desfontaines wrote:
Thanks for letting me know, this should be fixed now (I'm now using the Tor package from Debian Buster).
Great! But, it looks like the relay isn't running currently? Did something go wrong after the upgrade?
Is there a way to get automated warnings when that happens? I had unattended-upgrades set up on this machine, but due to an old /etc/apt/sources.list, I was stuck on an older Tor version.
Hm. I think there are a variety of monitoring approaches that folks use. I would suggest looking at the wiki relay guide: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Maintainingarela... But those are mostly aimed toward "did the process go away", not more subtle issues. I guess another answer would be to encourage you to actually look at the warning-level and err-level logs that Tor produces. :) In theory they should be pretty light, and can warn you about a variety of things that need fixing. Thanks! --Roger
On Mon, Sep 02, 2019 at 11:12:04PM +0200, Damien Desfontaines wrote:
Thanks for letting me know, this should be fixed now (I'm now using the Tor package from Debian Buster).
Great! But, it looks like the relay isn't running currently? Did something go wrong after the upgrade? Your tor-droideka@desfontain.es address also seems to be bouncing now -- hopefully that doesn't mean you have deleted all of your Tor things. :)
Is there a way to get automated warnings when that happens? I had unattended-upgrades set up on this machine, but due to an old /etc/apt/sources.list, I was stuck on an older Tor version.
Hm. I think there are a variety of monitoring approaches that folks use. I would suggest looking at the wiki relay guide: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Maintainingarela... But those are mostly aimed toward "did the process go away", not more subtle issues. I guess another answer would be to encourage you to actually look at the warning-level and err-level logs that Tor produces. :) In theory they should be pretty light, and can warn you about a variety of things that need fixing. Thanks! --Roger
Arg, I don't know what happened, it looked good after the update, but apparently it got stuck at some point, and rebooting my machine made me lose my previous config =( Are Tor relay configs stored somewhere? I'd just like to reuse whatever I was doing before… Otherwise I'll manually rewrite a config (and backup it this time ><) some time in the near future. Damien On Mon, Oct 14, 2019 at 06:34:24AM -0400, Roger Dingledine wrote:
On Mon, Sep 02, 2019 at 11:12:04PM +0200, Damien Desfontaines wrote:
Thanks for letting me know, this should be fixed now (I'm now using the Tor package from Debian Buster).
Great! But, it looks like the relay isn't running currently? Did something go wrong after the upgrade?
Your tor-droideka@desfontain.es address also seems to be bouncing now -- hopefully that doesn't mean you have deleted all of your Tor things. :)
Is there a way to get automated warnings when that happens? I had unattended-upgrades set up on this machine, but due to an old /etc/apt/sources.list, I was stuck on an older Tor version.
Hm. I think there are a variety of monitoring approaches that folks use. I would suggest looking at the wiki relay guide: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Maintainingarela... But those are mostly aimed toward "did the process go away", not more subtle issues.
I guess another answer would be to encourage you to actually look at the warning-level and err-level logs that Tor produces. :) In theory they should be pretty light, and can warn you about a variety of things that need fixing.
Thanks! --Roger
On Fri, Oct 18, 2019 at 02:25:51PM +0200, Damien Desfontaines wrote:
Arg, I don't know what happened, it looked good after the update, but apparently it got stuck at some point, and rebooting my machine made me lose my previous config =( Are Tor relay configs stored somewhere? I'd just like to reuse whatever I was doing before???
Yes, your relay identity info should be stored in the "keys" directory in your DataDirectory: https://2019.www.torproject.org/docs/faq#UpgradeOrMove So, either it's still there, and when you started the new Tor you somehow were pointing it to a different DataDirectory. Or something else weird happened.
Otherwise I'll manually rewrite a config (and backup it this time ><) some time in the near future.
That sounds like a solid option too. --Roger
participants (4)
-
Damien Desfontaines -
Damien Desfontaines -
Roger Dingledine -
teor