[tor-relays] Bridge showing offline

Eddie stunnel at attglobal.net
Thu Oct 14 19:11:17 UTC 2021


On 10/14/2021 2:44 AM, Bleedangel Tor Admin wrote:
> You are running 0.4.5.8, maybe updating to a newer version of tor will 
> help?
>
> Sent from ProtonMail for iOS
>
>
> On Thu, Oct 14, 2021 at 03:02, Georg Koppen <gk at torproject.org 
> <mailto:gk at torproject.org>> wrote:
>> Eddie:
>> > Looking at tor metrics, one of my bridges is showing as off-line:
>> > B080140DC1BAB5B86D1CE5A4CA2EF64F20282440
>> >
>> > 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
>> https://gitlab.torproject.org/tpo/core/tor/-/issues/40424. Hard to tell,
>> though. Does that issue happen regularly?
>>
>> Georg
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

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.

Cheers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20211014/40cf8f38/attachment.htm>


More information about the tor-relays mailing list