Why does my relay often appears offline in Metrics and should I be worry?
Hello, I often check my relay trough Metrics, but it often appears as offline after some time, from couple of hours to few days. I think it has this behavior since December 20. However, my relay seems to run normally. I have the usual number of connections when I check in Nyx. I don't see anything in the log. But, in Nyx, I don't see the flags that I see when it appears as online in Metrics. What I do is to restart the service, but I'm not sure if it's what I'm suppose to do. Is there an explanation or can you help me to investigate this issue? FYI, the tor, version 0.4.2.7, is running on a Ubuntu server 18.04 within a LXD container. My relay fingerprint is 33D88F331408141F2A2CC563239E54E48F7A211B https://metrics.torproject.org/rs.html#details/33D88F331408141F2A2CC563239E5... Thanks, Clèm
Am Do., 9. Apr. 2020 um 15:39 Uhr schrieb Clément Février < clement@forumanalogue.fr>:
I had the same problem some days ago but only once. The relay was shown as offline on Metrics and all flags in nyx were gone. I did not saw anything strange in the logfile and a reboot did not solved the problem. The next morning everything was back to normal. I switched it from a non-exit to an exit the day before and was still messing around with the Exit policy so i thought it was related to this. Fingerprint: DAA806E9529D77EF94685FC0E513386EF65B83F8
On Sat, Apr 18, 2020 at 10:16:34AM +0200, Clément Février wrote:
The issue is back. After more than 3 days, the relay appears offline. All flags are gone in nyx. There is a bug.
I believe there is something wrong with your ipv6 port. I see that your relay is advertising [2001:41d0:fecf:8900:216:3eff:fe8a:e4a6]:9001 and when I go to https://bridges.torproject.org/scan/ and put in "[2001:41d0:fecf:8900:216:3eff:fe8a:e4a6]" and "9001", it tells me "i/o timeout". So I would suggest removing the ipv6 stuff for a while and see if things get better for you. And then also exploring why your ipv6 address is not consistently routable, or not consistently reachable, or whatever else is going wrong with it. Thanks, --Roger
Hi there,
indeed there is something wrong. I am voting against you because I cannot reach you via IPv6. A traceroute to you seems to die somewhere inside OVH: 11 th2-dsl1-a1.fr.eu (2001:41d0::b76) 12.944 ms be45.th2-dsl1a-n93.fr.eu (2001:41d0::b72) 13.035 ms 13.103 ms 12 2001:41d0:fde0:80::30 (2001:41d0:fde0:80::30) 12.637 ms 12.595 ms 12.549 ms 13 2001:41d0:fecf:8900:5ee2:8cff:fe99:f106 (2001:41d0:fecf:8900:5ee2:8cff:fe99:f106) 22.724 ms 22.759 ms 21.971 ms 14 2001:41d0:fecf:8900:5ee2:8cff:fe99:f106 (2001:41d0:fecf:8900:5ee2:8cff:fe99:f106) 3029.525 ms !H 3022.011 ms !H 3022.124 ms !H
That seems quite worthwhile to figure out. Basically, your computer isn't really online right now ;) Cheers Sebastian
On 19/04/2020 02:37, Sebastian Hahn wrote:
It seems indeed there is something wrong with OVH support of IPv6. I tried few times to test IPv6 on https://bridges.torproject.org/scan/ and just by the time of writing this email, I got both positive and negative results. It is very random because I'm seeing IPv6 connections in nyx. The IP 2001:41d0:fecf:8900:5ee2:8cff:fe99:f106 corresponds to the router provided by OVH (it is a very crappy one a Zyxel VMG8823-B50B where the interface is so buggy). I'll contact them to solve this issue. In the mean time, I'll remove IPv6 from torrc. Thank you all for your answers! Cheers, Clèm
participants (4)
-
[REDACTED] -
Clément Février -
Roger Dingledine -
Sebastian Hahn