You are running 0.4.5.8, maybe updating to a newer version of tor will help?
Sent from ProtonMail for iOS
> Looking at tor metrics, one of my bridges is showing as off-line:
> However, the log isn't showing any issues:
> Oct 14 00:00:28.000 [notice] Tor 0.4.5.8 opening new log file.
> Oct 14 00:00:28.000 [notice] Configured hibernation. This interval
> began at 2021-10-14 00:00:00; the scheduled wake-up time was 2021-10-14
> 00:00:00; we expect to exhaust our quota for this interval around
> 2021-10-15 00:00:00; the next interval begins at 2021-10-15 00:00:00
> (all times local)
> Oct 14 01:49:40.000 [notice] Heartbeat: Tor's uptime is 124 days 6:00
> hours, with 0 circuits open. I've sent 907.23 GB and received 922.28 GB.
> I've received 63052 connections on IPv4 and 8375 on IPv6. I've made
> 512684 connections with IPv4 and 100974 with IPv6.
> Oct 14 01:49:40.000 [notice] While not bootstrapping, fetched this many
> bytes: 1801791624 (server descriptor fetch); 175792 (server descriptor
> upload); 221750347 (consensus network-status fetch); 10974 (authority
> cert fetch); 19905655 (microdescriptor fetch)
> Oct 14 01:49:40.000 [notice] Heartbeat: Accounting enabled. Sent: 140.52
> MB, Received: 140.69 MB, Used: 281.21 MB / 200.00 GB, Rule: sum. The
> current accounting interval ends on 2021-10-15 00:00:00, in 22:10 hours.
> Oct 14 01:49:40.000 [notice] Heartbeat: In the last 6 hours, I have seen
> 14 unique clients.
> Initially I thought of a previous issue I had with IPv6 connectivity,
> but don't think this is the problem here as the 2nd bridge on the same
> server is showing on-line. Also an IPv6 port scan shows the ports for
> both bridges as accessible.
> Ideas ??
I wonder whether that is another instance
Relay ORPort is not reachable in Tor 0.4.5 (worked in Tor 0.4.4) (#40424) · Issues · The Tor Project / Core / Tor · GitLab. Hard to tell,
though. Does that issue happen regularly?
I didn't touch anything, and this morning the metrics say the bridge is running normally, with an uptime of over 125 days.
Looks like it might have been a metrics issue, not the bridge itself.
Actually, I don't think this has been a Metrics issue. Rather, Serge (the bridge authority) did not assign your bridge the Running flag between 0330 and 0500 UTC presumably because it was not able to reach your bridge during that time for whatever reason. As a result relays-search showed your bridge as offline.
There might be a bug somewhere, though, for showing the bridge as running again because, anecdotally, it takes quite some time to get the Running indicator to green again. I am not sure.
However, your bridge at least should have been doing fine since then according to data we have.