Re: [tor-relays] Overloaded state indicator on relay-search
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Agreed, can the thresholds be published publicly for easy reference? Sometimes i get the overloaded flag but i have nothing in my logs, and my cpu/memory is abundant. It would be much easier to ascertain the cause of this if we knew what we were looking for! Thank you ‐‐‐ Original Message ‐‐‐ On Monday, September 27th, 2021 at 10:23 AM, Gary C. New via tor-relays wrote: > George, > > The referenced support article provides recommendations as to what might be > causing the overloaded state, but it doesn't provide the metric(s) for how > Tor decides whether a relay is overloaded. I'm trying to ascertain the later. > > I would assume the overloaded state metric(S) is/are a maximum timeout value > and/or reoccurrence value, etc. > > By knowing what the overloaded state metric is, I can tune my Tor relay just > short of it. > > Thank you for your reply. > > Respectfully, > > Gary > > On Monday, September 27, 2021, 2:44:35 AM PDT, Georg Koppen > wrote: > > Gary C. New via tor-relays: > > > Hiro, > > > Presently, I'm seeing a similar issue. On my laptop, I'm observing an > > overloaded status for my relay. However, the same relay shows a green > > status on my phone. > > > Do you do any user-agent detection? > > > I'm still interested in those magic numbers, which determine whether a > > relay has reached an overloaded state. > > Which numbers do you mean? Is there anything missing from the support > > article[1] you feel should be there? > > Georg > > [1] https://support.torproject.org/relay-operators/relay-bridge-overloaded/ > > > Thank You. > > > Respectfully, > > > > > > Gary > > > > > > On Saturday, September 25, 2021, 7:11:31 AM PDT, Silvia/Hiro > > wrote: > > > > > > Hi, > > > I went back in history and tried to find out whenever your node > > > FriendlyExit1 was overloaded. I couldn't find the exact descriptor. > > > > > > One thing I can think of is that on the 22nd when I deployed this I > > > noticed a few typos in the code and had to make a second release. Maybe > > > something was cached for a while and you what you were accessing from > > > mobile was the buggy page. > > > > > > If it happens again there are two buttons at the end of the page where > > > you can see the latest server and extra-info descriptors. If you > > > download the server one you would be able to verify that there is a > > > "overload-general" field in there. If there isn't we have a bug :). > > > > > > Please let me know if this happens again. > > > > > > Cheers, > > > -hiro > > > > > > On 9/24/21 2:39 PM, friendlyexitnode via tor-relays wrote: > > >> Hey hiro, thanks! > > >> > > >> I've also attached some screenshots too if it helps (sorry, I should have > >> done that before). I had first noticed this around 3:45 PM CST on > >> September 23. > > >> > > >> - The Friendly Exit Node Family > > >> > > >> Sent with ProtonMail Secure Email. > > >> > > >> ‐‐‐ Original Message ‐‐‐ > > >> > > >> On Friday, September 24th, 2021 at 4:47 AM, Silvia/Hiro > >> wrote: > > >> > > >>> On 9/23/21 10:54 PM, friendlyexitnode via tor-relays wrote: > > >>> > > This looks like an awesome feature! I super appreciate it. > > > > Random question though (and I'm the first to admit I may be doing > something wrong), I notice that on Mobile it says my relays are > overloaded however when I view it on a normal computer I don't get the > overloaded indicator. I've tried refreshing multiple times but getting > the same results. Is anyone seeing the same thing? > > >>> > > >>> Hi, > > >>> > > >>> could you let me know when you accessed the page via mobile approximately? > > >>> > > >>> I'll try to check if any of your relays were overloaded in the past. > > >>> > > >>> When a node is overloaded the state is kept for 72 hours. > > >>> > > >>> Cheers, > > >>> > > >>> -hiro > > >>> > > Family Members: > > > > F01E382DA524A57F2BFB3C4FF270A23D5CD3311D > > > > 6231A1370700DD03046A85D953D35CAB5C21 > > > > F9A28AB71D7E4E446308641A556EA53BA55FCB50 > > > > 23F74D581DE92AC59D3527DE4D448E036139D81E > > > > A00E900534DFF76371064C03714753EAF8B88820 > > > > C232D8EE677E6BDF5CFFDDCAC4E2B1682DCE7AE5 > > > > - The Friendly Exit Node Family > > > > Sent with ProtonMail Secure Email. > > > > ‐‐‐ Original Message ‐‐‐ > > > > On Thursday, September 23rd, 2021 at 8:39 AM, Silvia/Hiro > h...@torproject.org wrote: > > > > > Hello all, > > > > > > One of our goals with our current performance work is to reduce the > > > > > > overload of relays in the network. The implementation of proposal 328[1] > > > > > > a while back made different overload indicators available to relay > > > > > > operators and since a couple of weeks ago those can be tracked via > > > > > > Onionoo[2] as
Re: [tor-relays] Overloaded state indicator on relay-search
George, The referenced support article provides recommendations as to what might be causing the overloaded state, but it doesn't provide the metric(s) for how Tor decides whether a relay is overloaded. I'm trying to ascertain the later. I would assume the overloaded state metric(S) is/are a maximum timeout value and/or reoccurrence value, etc. By knowing what the overloaded state metric is, I can tune my Tor relay just short of it. Thank you for your reply. Respectfully, Gary On Monday, September 27, 2021, 2:44:35 AM PDT, Georg Koppen wrote: Gary C. New via tor-relays: > Hiro, > Presently, I'm seeing a similar issue. On my laptop, I'm observing an > overloaded status for my relay. However, the same relay shows a green status > on my phone. > Do you do any user-agent detection? > I'm still interested in those magic numbers, which determine whether a relay > has reached an overloaded state. Which numbers do you mean? Is there anything missing from the support article[1] you feel should be there? Georg [1] https://support.torproject.org/relay-operators/relay-bridge-overloaded/ > Thank You. > Respectfully, > > Gary > > On Saturday, September 25, 2021, 7:11:31 AM PDT, Silvia/Hiro > wrote: > > Hi, > I went back in history and tried to find out whenever your node > FriendlyExit1 was overloaded. I couldn't find the exact descriptor. > > One thing I can think of is that on the 22nd when I deployed this I > noticed a few typos in the code and had to make a second release. Maybe > something was cached for a while and you what you were accessing from > mobile was the buggy page. > > If it happens again there are two buttons at the end of the page where > you can see the latest server and extra-info descriptors. If you > download the server one you would be able to verify that there is a > "overload-general" field in there. If there isn't we have a bug :). > > Please let me know if this happens again. > > Cheers, > -hiro > > On 9/24/21 2:39 PM, friendlyexitnode via tor-relays wrote: >> Hey hiro, thanks! >> >> I've also attached some screenshots too if it helps (sorry, I should have >> done that before). I had first noticed this around 3:45 PM CST on September >> 23. >> >> - The Friendly Exit Node Family >> >> Sent with ProtonMail Secure Email. >> >> ‐‐‐ Original Message ‐‐‐ >> >> On Friday, September 24th, 2021 at 4:47 AM, Silvia/Hiro >> wrote: >> >>> On 9/23/21 10:54 PM, friendlyexitnode via tor-relays wrote: >>> This looks like an awesome feature! I super appreciate it. Random question though (and I'm the first to admit I may be doing something wrong), I notice that on Mobile it says my relays are overloaded however when I view it on a normal computer I don't get the overloaded indicator. I've tried refreshing multiple times but getting the same results. Is anyone seeing the same thing? >>> >>> Hi, >>> >>> could you let me know when you accessed the page via mobile approximately? >>> >>> I'll try to check if any of your relays were overloaded in the past. >>> >>> When a node is overloaded the state is kept for 72 hours. >>> >>> Cheers, >>> >>> -hiro >>> Family Members: F01E382DA524A57F2BFB3C4FF270A23D5CD3311D 6231A1370700DD03046A85D953D35CAB5C21 F9A28AB71D7E4E446308641A556EA53BA55FCB50 23F74D581DE92AC59D3527DE4D448E036139D81E A00E900534DFF76371064C03714753EAF8B88820 C232D8EE677E6BDF5CFFDDCAC4E2B1682DCE7AE5 - The Friendly Exit Node Family Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, September 23rd, 2021 at 8:39 AM, Silvia/Hiro h...@torproject.org wrote: > Hello all, > > One of our goals with our current performance work is to reduce the > > overload of relays in the network. The implementation of proposal 328[1] > > a while back made different overload indicators available to relay > > operators and since a couple of weeks ago those can be tracked via > > Onionoo[2] as well. > > As we know that a lot of our relay operators use relay search to check > > for the health of their relays, we have launched a new feature there, > > too, to help them know when their relays are overloaded. > > When a relay is in the overloaded state we show an amber dot next to the > > relay nickname. > > Currently we are counting between 50 and 80 overloaded relays and > > between 10 and 20 overloaded bridges. > > The overloaded state is reached when one or many of the possible load > > metrics have been triggered. When this happens we show it for 72 hours > > after the relay has recovered [3]. Note, though, that not all of the > > exposed overload metrics are triggering the overload indicator on relay > > search yet. > > If you noticed your relay is
Re: [tor-relays] Overloaded state indicator on relay-search
On 24 Sep (12:36:17), li...@for-privacy.net wrote: > On Thursday, September 23, 2021 3:39:08 PM CEST Silvia/Hiro wrote: > > > When a relay is in the overloaded state we show an amber dot next to the > > relay nickname. > Nice thing. This flag has noticed me a few days ago. > > > If you noticed your relay is overloaded, please check the following > > support article to find out how you can recover to a "normal" state: > > > > https://support.torproject.org/relay-operators/relay-bridge-overloaded/ > > A question about Enabling Metricsport. Is definitely Prometheus necessary? > Or can the Metrics Port write into a LogFile / TextFile? The output format is Prometheus but you don't need a prometheus server to get it. Once opened, you can simply fetch it like this: wget http://:/metrics -O /tmp/output.txt or curl http://:/metrics -o /tmp/output.txt Cheers! David -- 7GLrazDic7AYE2euK7PjuTqUtCfU+/3JH4ZWkM1HP/g= signature.asc Description: PGP signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Overloaded state indicator on relay-search
Toralf Förster: > On 9/25/21 4:11 PM, Silvia/Hiro wrote: >> If it happens again there are two buttons at the end of the page where >> you can see the latest server and extra-info descriptors. > Only, if the DirPort is (still) opened, or ? Yes, I think so. (Good catch) Georg OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Overloaded state indicator on relay-search
Gary C. New via tor-relays: > Hiro, > Presently, I'm seeing a similar issue. On my laptop, I'm observing an > overloaded status for my relay. However, the same relay shows a green status > on my phone. > Do you do any user-agent detection? > I'm still interested in those magic numbers, which determine whether a relay > has reached an overloaded state. Which numbers do you mean? Is there anything missing from the support article[1] you feel should be there? Georg [1] https://support.torproject.org/relay-operators/relay-bridge-overloaded/ > Thank You. > Respectfully, > > Gary > > On Saturday, September 25, 2021, 7:11:31 AM PDT, Silvia/Hiro > wrote: > > Hi, > I went back in history and tried to find out whenever your node > FriendlyExit1 was overloaded. I couldn't find the exact descriptor. > > One thing I can think of is that on the 22nd when I deployed this I > noticed a few typos in the code and had to make a second release. Maybe > something was cached for a while and you what you were accessing from > mobile was the buggy page. > > If it happens again there are two buttons at the end of the page where > you can see the latest server and extra-info descriptors. If you > download the server one you would be able to verify that there is a > "overload-general" field in there. If there isn't we have a bug :). > > Please let me know if this happens again. > > Cheers, > -hiro > > On 9/24/21 2:39 PM, friendlyexitnode via tor-relays wrote: >> Hey hiro, thanks! >> >> I've also attached some screenshots too if it helps (sorry, I should have >> done that before). I had first noticed this around 3:45 PM CST on September >> 23. >> >> - The Friendly Exit Node Family >> >> Sent with ProtonMail Secure Email. >> >> ‐‐‐ Original Message ‐‐‐ >> >> On Friday, September 24th, 2021 at 4:47 AM, Silvia/Hiro >> wrote: >> >>> On 9/23/21 10:54 PM, friendlyexitnode via tor-relays wrote: >>> This looks like an awesome feature! I super appreciate it. Random question though (and I'm the first to admit I may be doing something wrong), I notice that on Mobile it says my relays are overloaded however when I view it on a normal computer I don't get the overloaded indicator. I've tried refreshing multiple times but getting the same results. Is anyone seeing the same thing? >>> >>> Hi, >>> >>> could you let me know when you accessed the page via mobile approximately? >>> >>> I'll try to check if any of your relays were overloaded in the past. >>> >>> When a node is overloaded the state is kept for 72 hours. >>> >>> Cheers, >>> >>> -hiro >>> Family Members: F01E382DA524A57F2BFB3C4FF270A23D5CD3311D 6231A1370700DD03046A85D953D35CAB5C21 F9A28AB71D7E4E446308641A556EA53BA55FCB50 23F74D581DE92AC59D3527DE4D448E036139D81E A00E900534DFF76371064C03714753EAF8B88820 C232D8EE677E6BDF5CFFDDCAC4E2B1682DCE7AE5 - The Friendly Exit Node Family Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, September 23rd, 2021 at 8:39 AM, Silvia/Hiro h...@torproject.org wrote: > Hello all, > > One of our goals with our current performance work is to reduce the > > overload of relays in the network. The implementation of proposal 328[1] > > a while back made different overload indicators available to relay > > operators and since a couple of weeks ago those can be tracked via > > Onionoo[2] as well. > > As we know that a lot of our relay operators use relay search to check > > for the health of their relays, we have launched a new feature there, > > too, to help them know when their relays are overloaded. > > When a relay is in the overloaded state we show an amber dot next to the > > relay nickname. > > Currently we are counting between 50 and 80 overloaded relays and > > between 10 and 20 overloaded bridges. > > The overloaded state is reached when one or many of the possible load > > metrics have been triggered. When this happens we show it for 72 hours > > after the relay has recovered [3]. Note, though, that not all of the > > exposed overload metrics are triggering the overload indicator on relay > > search yet. > > If you noticed your relay is overloaded, please check the following > > support article to find out how you can recover to a "normal" state: > > https://support.torproject.org/relay-operators/relay-bridge-overloaded/ > > Let us known how you find this new feature. > > Cheers, > > -hiro > > [1] > > https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload-report.md > > [2] > > https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html > > [3]
Re: [tor-relays] Overloaded state indicator on relay-search
Ofc I meant you can reply off list. On 9/27/21 11:16 AM, Silvia/Hiro wrote: > Gary, > > Replying off list. > Can I know which one is your relay? > We don't do user-agent detection. > > Cheers, > -hiro > > On 9/26/21 4:27 AM, Gary C. New via tor-relays wrote: >> Hiro, >> Presently, I'm seeing a similar issue. On my laptop, I'm observing an >> overloaded status for my relay. However, the same relay shows a green status >> on my phone. >> Do you do any user-agent detection? >> I'm still interested in those magic numbers, which determine whether a relay >> has reached an overloaded state. >> Thank You. >> Respectfully, >> >> Gary >> >> On Saturday, September 25, 2021, 7:11:31 AM PDT, Silvia/Hiro >> wrote: >> >> Hi, >> I went back in history and tried to find out whenever your node >> FriendlyExit1 was overloaded. I couldn't find the exact descriptor. >> >> One thing I can think of is that on the 22nd when I deployed this I >> noticed a few typos in the code and had to make a second release. Maybe >> something was cached for a while and you what you were accessing from >> mobile was the buggy page. >> >> If it happens again there are two buttons at the end of the page where >> you can see the latest server and extra-info descriptors. If you >> download the server one you would be able to verify that there is a >> "overload-general" field in there. If there isn't we have a bug :). >> >> Please let me know if this happens again. >> >> Cheers, >> -hiro >> >> On 9/24/21 2:39 PM, friendlyexitnode via tor-relays wrote: >>> Hey hiro, thanks! >>> >>> I've also attached some screenshots too if it helps (sorry, I should have >>> done that before). I had first noticed this around 3:45 PM CST on September >>> 23. >>> >>> - The Friendly Exit Node Family >>> >>> Sent with ProtonMail Secure Email. >>> >>> ‐‐‐ Original Message ‐‐‐ >>> >>> On Friday, September 24th, 2021 at 4:47 AM, Silvia/Hiro >>> wrote: >>> On 9/23/21 10:54 PM, friendlyexitnode via tor-relays wrote: > This looks like an awesome feature! I super appreciate it. > > Random question though (and I'm the first to admit I may be doing > something wrong), I notice that on Mobile it says my relays are > overloaded however when I view it on a normal computer I don't get the > overloaded indicator. I've tried refreshing multiple times but getting > the same results. Is anyone seeing the same thing? Hi, could you let me know when you accessed the page via mobile approximately? I'll try to check if any of your relays were overloaded in the past. When a node is overloaded the state is kept for 72 hours. Cheers, -hiro > Family Members: > > F01E382DA524A57F2BFB3C4FF270A23D5CD3311D > > 6231A1370700DD03046A85D953D35CAB5C21 > > F9A28AB71D7E4E446308641A556EA53BA55FCB50 > > 23F74D581DE92AC59D3527DE4D448E036139D81E > > A00E900534DFF76371064C03714753EAF8B88820 > > C232D8EE677E6BDF5CFFDDCAC4E2B1682DCE7AE5 > > - The Friendly Exit Node Family > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > > On Thursday, September 23rd, 2021 at 8:39 AM, Silvia/Hiro > h...@torproject.org wrote: > >> Hello all, >> >> One of our goals with our current performance work is to reduce the >> >> overload of relays in the network. The implementation of proposal 328[1] >> >> a while back made different overload indicators available to relay >> >> operators and since a couple of weeks ago those can be tracked via >> >> Onionoo[2] as well. >> >> As we know that a lot of our relay operators use relay search to check >> >> for the health of their relays, we have launched a new feature there, >> >> too, to help them know when their relays are overloaded. >> >> When a relay is in the overloaded state we show an amber dot next to the >> >> relay nickname. >> >> Currently we are counting between 50 and 80 overloaded relays and >> >> between 10 and 20 overloaded bridges. >> >> The overloaded state is reached when one or many of the possible load >> >> metrics have been triggered. When this happens we show it for 72 hours >> >> after the relay has recovered [3]. Note, though, that not all of the >> >> exposed overload metrics are triggering the overload indicator on relay >> >> search yet. >> >> If you noticed your relay is overloaded, please check the following >> >> support article to find out how you can recover to a "normal" state: >> >> https://support.torproject.org/relay-operators/relay-bridge-overloaded/ >> >> Let us known how you find this new feature. >> >> Cheers, >> >> -hiro >> >> [1] >> >>
Re: [tor-relays] Overloaded state indicator on relay-search
Gary, Replying off list. Can I know which one is your relay? We don't do user-agent detection. Cheers, -hiro On 9/26/21 4:27 AM, Gary C. New via tor-relays wrote: > Hiro, > Presently, I'm seeing a similar issue. On my laptop, I'm observing an > overloaded status for my relay. However, the same relay shows a green status > on my phone. > Do you do any user-agent detection? > I'm still interested in those magic numbers, which determine whether a relay > has reached an overloaded state. > Thank You. > Respectfully, > > Gary > > On Saturday, September 25, 2021, 7:11:31 AM PDT, Silvia/Hiro > wrote: > > Hi, > I went back in history and tried to find out whenever your node > FriendlyExit1 was overloaded. I couldn't find the exact descriptor. > > One thing I can think of is that on the 22nd when I deployed this I > noticed a few typos in the code and had to make a second release. Maybe > something was cached for a while and you what you were accessing from > mobile was the buggy page. > > If it happens again there are two buttons at the end of the page where > you can see the latest server and extra-info descriptors. If you > download the server one you would be able to verify that there is a > "overload-general" field in there. If there isn't we have a bug :). > > Please let me know if this happens again. > > Cheers, > -hiro > > On 9/24/21 2:39 PM, friendlyexitnode via tor-relays wrote: >> Hey hiro, thanks! >> >> I've also attached some screenshots too if it helps (sorry, I should have >> done that before). I had first noticed this around 3:45 PM CST on September >> 23. >> >> - The Friendly Exit Node Family >> >> Sent with ProtonMail Secure Email. >> >> ‐‐‐ Original Message ‐‐‐ >> >> On Friday, September 24th, 2021 at 4:47 AM, Silvia/Hiro >> wrote: >> >>> On 9/23/21 10:54 PM, friendlyexitnode via tor-relays wrote: >>> This looks like an awesome feature! I super appreciate it. Random question though (and I'm the first to admit I may be doing something wrong), I notice that on Mobile it says my relays are overloaded however when I view it on a normal computer I don't get the overloaded indicator. I've tried refreshing multiple times but getting the same results. Is anyone seeing the same thing? >>> >>> Hi, >>> >>> could you let me know when you accessed the page via mobile approximately? >>> >>> I'll try to check if any of your relays were overloaded in the past. >>> >>> When a node is overloaded the state is kept for 72 hours. >>> >>> Cheers, >>> >>> -hiro >>> Family Members: F01E382DA524A57F2BFB3C4FF270A23D5CD3311D 6231A1370700DD03046A85D953D35CAB5C21 F9A28AB71D7E4E446308641A556EA53BA55FCB50 23F74D581DE92AC59D3527DE4D448E036139D81E A00E900534DFF76371064C03714753EAF8B88820 C232D8EE677E6BDF5CFFDDCAC4E2B1682DCE7AE5 - The Friendly Exit Node Family Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, September 23rd, 2021 at 8:39 AM, Silvia/Hiro h...@torproject.org wrote: > Hello all, > > One of our goals with our current performance work is to reduce the > > overload of relays in the network. The implementation of proposal 328[1] > > a while back made different overload indicators available to relay > > operators and since a couple of weeks ago those can be tracked via > > Onionoo[2] as well. > > As we know that a lot of our relay operators use relay search to check > > for the health of their relays, we have launched a new feature there, > > too, to help them know when their relays are overloaded. > > When a relay is in the overloaded state we show an amber dot next to the > > relay nickname. > > Currently we are counting between 50 and 80 overloaded relays and > > between 10 and 20 overloaded bridges. > > The overloaded state is reached when one or many of the possible load > > metrics have been triggered. When this happens we show it for 72 hours > > after the relay has recovered [3]. Note, though, that not all of the > > exposed overload metrics are triggering the overload indicator on relay > > search yet. > > If you noticed your relay is overloaded, please check the following > > support article to find out how you can recover to a "normal" state: > > https://support.torproject.org/relay-operators/relay-bridge-overloaded/ > > Let us known how you find this new feature. > > Cheers, > > -hiro > > [1] > > https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload-report.md > > [2] > > https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html > > [3] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n637 > > tor-relays
