Greetings All, I have three relays that are in need of an upgrade and reboot. What is the best way to restart these relays without loosing flags or time? Secondly how long can a relay be down before flags are dropped? Thank you for any help! Sysop
Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Hello,
I cant comment on how long a relay needs to be down before you loose flags could be a day or longer. As for needing to upgrade and reboot just go ahead and do it. The network will keep your current flags through the reboot and upgrade. Being down for both a reboot and or a upgrade is expected and encouraged.
Thanks, John Csuti +1 (216) 633-1279
On 2021-10-09 11:07 PM, sysmanager7 via tor-relays wrote:
Greetings All, I have three relays that are in need of an upgrade and reboot. What is the best way to restart these relays without loosing flags or time? Secondly how long can a relay be down before flags are dropped? Thank you for any help! Sysop
Sent with ProtonMail [1] Secure Email.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Links: ------ [1] https://protonmail.com/
On Sunday, October 10, 2021 5:07:54 AM CEST sysmanager7 via tor-relays wrote:
Greetings All, I have three relays that are in need of an upgrade and reboot. What is the best way to restart these relays without loosing flags or time?
That depends on your OS and the init daemon. Example for sshd: https://www.cyberciti.biz/faq/howto-restart-ssh/ On Debian derivatives with systemd:
Reload will tell the service to reload its configuration files, but keep the same process running. Restart tells it to shut down entirely, then restart. Generally speaking, restart will terminate the service in question and restart it; reload will only reload the configuration file. After an upgrade you must use restart.
Use 'su -' or sudo
~$ sudo systemctl restart tor ~$ sudo systemctl reload tor
The above applies to all instances. For individual instances use: ~$ sudo systemctl reload tor@00 ~$ sudo systemctl reload tor@01 ...
On init.d systems (Unix/Linux/*BSD) use: ('su -', doas or sudo) ~$ service restart tor
Secondly how long can a relay be down before flags are dropped?
After a reload, the flags are retained. After a restart they are gone straight away. How quickly they come back depends on the length and frequency of the downtime.
Greetings! Thanks for running your relays!
On Sunday, October 10, 2021 at 4:49:16 AM UTC-4 sysmanager7 via tor-relays wrote:
Greetings All, I have three relays that are in need of an upgrade and reboot. What is the best way to restart these relays without loosing flags or time?
We routinely reboot our nodes for kernel updates and retain the stable flag. High uptime is not something to brag about for a tor node, so don't worry about that.
If you're running a debian-based linux distro, you can have unattended-upgrades[0] do the work for you and warn you via email. There are tools that will allow for similar workflows for other OSes, eg. with dnf on rpm-based distros[1].
Secondly how long can a relay be down before flags are dropped?
I don't know the upper bound, but twice I've migrated keys from an old piece of hardware to a new piece of hardware when the support warranty expired, and that node still has the stable flag. I took my time and did the migration carefully. It's far more important that you follow the advice[2] on how to keep your relay in good shape once it's up and running than that you find the limits of certain flags.
Cheers! -- ibiblio Tor Manager
[0] https://wiki.debian.org/UnattendedUpgrades [1] https://dnf.readthedocs.io/en/latest/automatic.html [2] https://community.torproject.org/relay/setup/post-install/
tor-relays@lists.torproject.org