Hi - I am having an issue where the Tor Metrics page for my [bridge](https://metrics.torproject.org/rs.html#details/FE31AD644BA16316A06B905F8403F...) will always eventually be showing between 1-2hr downtimes, despite the server showing no notable logs, being reachable, and displaying running circuit/data activity using Nyx.
I have tried rebooting the machine and the service, which at best fixes it for a week before the displayed downtimes begin.
I am pretty confident in the operation of the bridge and am worried that traffic may be steered away due to incorrect descriptors going around.
Best, Hakeem
Hakeem M Salem via network-health:
Hi - I am having an issue where the Tor Metrics page for my [bridge](https://metrics.torproject.org/rs.html#details/FE31AD644BA16316A06B905F8403F...) will always eventually be showing between 1-2hr downtimes, despite the server showing no notable logs, being reachable, and displaying running circuit/data activity using Nyx.
I have tried rebooting the machine and the service, which at best fixes it for a week before the displayed downtimes begin.
Okay, so right now things look fine, right? I think the downtime part is a bug which is on our radar[1].
The interesting part is why this is working for a bit but then stopping, though. Are there any changes on your side that could cause this?
We can look at your bridge and maybe investigate a bit next time when this happens. My guess is that the bridge authority is not able to reach your bridge at some point and then things start to go south...
Georg
[1] https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issu...
I am pretty confident in the operation of the bridge and am worried that traffic may be steered away due to incorrect descriptors going around.
Best, Hakeem
network-health mailing list network-health@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/network-health
network-health@lists.torproject.org