[tor-relays] Bridge showing offline

Fri Jan 7 08:08:26 UTC 2022

Hi,

I experience a similar problem and ended up restarting the service once 
a week. With this hack, metrics shows it online all the time and I get 
connections. There were no traces in the logs either.
BTW: I am running 0.4.6.8 on FreeBSD. I someone want's to guide me how 
to analyze this further I am happy to help.

Cord

On 06.01.2022 19:52, Eddie wrote:
> This has now happened again, on the same bridge, showing off-line to 
> the metrics, but the logs showing it running with activity taking place.
>
> Guess I'll keep an eye on the metrics to see if it pops back to available.
>
> I'm wondering how often this might be happening, because I don't check 
> the metrics that often and the instance documented below didn't change 
> the Uptime or Last Restart to indicate anything had happened.  So 
> unless I notice while it's in this state, like now, I have no way of 
> knowing if it happens regularly or not.
>
> Cheers.
>
>
>
>
> On 10/14/2021 12:11 PM, Eddie wrote:
>> 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> 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.
>>
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20220107/78dd185b/attachment-0001.htm>