[tor-relays] Relay no longer acting as a gaurd node?

Hi All,

A little while ago one of my relays switched from usually acting as a
guard node to never acting as a guard node:

https://metrics.torproject.org/rs.html#details/9715C81BA8C5B0C698882035F75C67D6D643DBE3

Doesn't matter to me if it's a guard or not jsut want to understand
what's changed and if it's a problem. Do I have a misconfiguration?

-Jon

I've thought the same, but then I checked relays running 0.4.8.7 version and many (most?) of them are guard nodes: Relay Search

I noticed that the author have updated their node to 0.4.8.8 version and still doesn't have the guard flag.

Best,
Bart

···

On 9.11.2023 16:47, Albert Larsan via tor-relays wrote:

On 11/9/23 16:03, Jonathan Proulx wrote:

A little while ago one of my relays switched from usually acting as a
guard node to never acting as a guard node:

Relay Search

Doesn't matter to me if it's a guard or not jsut want to understand
what's changed and if it's a problem. Do I have a misconfiguration?

I think this is because your relay is not up-to-date, you should update to the latest version available (0.4.8.8 at time of writing, though from what I can tell 0.4.8.9 was just released).

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
tor-relays Info Page

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Just wondering, you haven’t set a bandwidth limit on that node, have you? Setting an AccountingMax directive will cause you to lose your Guard flag since your server can’t be available at all times.

···

On 11/9/2023 10:03 AM, Jonathan Proulx wrote:

Hi All,

A little while ago one of my relays switched from usually acting as a
guard node to never acting as a guard node:

[https://metrics.torproject.org/rs.html#details/9715C81BA8C5B0C698882035F75C67D6D643DBE3](https://metrics.torproject.org/rs.html#details/9715C81BA8C5B0C698882035F75C67D6D643DBE3)

Doesn't matter to me if it's a guard or not jsut want to understand
what's changed and if it's a problem. Do I have a misconfiguration?

-Jon

_______________________________________________
tor-relays mailing list
[tor-relays@lists.torproject.org](mailto:tor-relays@lists.torproject.org)
[https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays)

Thanks Alex, I do have the node configured to automatically apply security updates and reboot as needed so at first I though that might be biting me, but I did have three reboots to the same kernel version so maybe there were some transient issues:

$ last reboot
reboot system boot 5.4.0-166-generi Tue Oct 31 19:43 still running
reboot system boot 5.4.0-165-generi Sat Oct 28 02:00 - 19:43 (3+17:42)
reboot system boot 5.4.0-165-generi Tue Oct 24 03:27 - 02:00 (3+22:33)
reboot system boot 5.4.0-165-generi Sat Oct 21 02:00 - 02:00 (6+23:59)
reboot system boot 5.4.0-164-generi Sat Oct 7 02:00 - 02:00 (13+23:59)

I did miss the missing stable flag and that definitely explains my state.

Thanks,
-Jon

···

On Friday, November 10th, 2023 at 9:19 AM, Alex Xu \(Hello71\) via tor-relays <tor-relays@lists.torproject.org> wrote:

I'm not sure what the MTBF criteria are now, but
restarting more than once a week will probably disqualify a relay from
being a Guard.