<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 10/14/2021 2:44 AM, Bleedangel Tor Admin wrote:<br>
<blockquote type="cite"
cite="mid:dTEO07i1qokpel6X2KtCG7dxCHMkxDR16f03fSwRFXlYWRMmPL2rvQ7ueJCK4hYDJ7bRj7tzY0VJAAGJ-CLhcQbE1dj28AcXtnDGAjzohtU=@bleedangel.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
You are running 0.4.5.8, maybe updating to a newer version of tor
will help?<caret></caret><br>
<div><br>
</div>
<div id="protonmail_mobile_signature_block">
<div>Sent from ProtonMail for iOS</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Thu, Oct 14, 2021 at 03:02, Georg Koppen <<a
href="mailto:gk@torproject.org" class="" moz-do-not-send="true">gk@torproject.org</a>>
wrote:
<blockquote class="protonmail_quote" type="cite"> Eddie:<br>
> Looking at tor metrics, one of my bridges is showing as
off-line:<br>
> B080140DC1BAB5B86D1CE5A4CA2EF64F20282440<br>
><br>
> However, the log isn't showing any issues:<br>
><br>
> Oct 14 00:00:28.000 [notice] Tor 0.4.5.8 opening new log
file.<br>
> Oct 14 00:00:28.000 [notice] Configured hibernation. This
interval<br>
> began at 2021-10-14 00:00:00; the scheduled wake-up time
was 2021-10-14<br>
> 00:00:00; we expect to exhaust our quota for this interval
around<br>
> 2021-10-15 00:00:00; the next interval begins at 2021-10-15
00:00:00<br>
> (all times local)<br>
> Oct 14 01:49:40.000 [notice] Heartbeat: Tor's uptime is 124
days 6:00<br>
> hours, with 0 circuits open. I've sent 907.23 GB and
received 922.28 GB.<br>
> I've received 63052 connections on IPv4 and 8375 on IPv6.
I've made<br>
> 512684 connections with IPv4 and 100974 with IPv6.<br>
> Oct 14 01:49:40.000 [notice] While not bootstrapping,
fetched this many<br>
> bytes: 1801791624 (server descriptor fetch); 175792 (server
descriptor<br>
> upload); 221750347 (consensus network-status fetch); 10974
(authority<br>
> cert fetch); 19905655 (microdescriptor fetch)<br>
> Oct 14 01:49:40.000 [notice] Heartbeat: Accounting enabled.
Sent: 140.52<br>
> MB, Received: 140.69 MB, Used: 281.21 MB / 200.00 GB, Rule:
sum. The<br>
> current accounting interval ends on 2021-10-15 00:00:00, in
22:10 hours.<br>
> Oct 14 01:49:40.000 [notice] Heartbeat: In the last 6
hours, I have seen<br>
> 14 unique clients.<br>
><br>
> Initially I thought of a previous issue I had with IPv6
connectivity,<br>
> but don't think this is the problem here as the 2nd bridge
on the same<br>
> server is showing on-line. Also an IPv6 port scan shows
the ports for<br>
> both bridges as accessible.<br>
><br>
> Ideas ??<br>
<br>
I wonder whether that is another instance<br>
<a class="moz-txt-link-freetext" href="https://gitlab.torproject.org/tpo/core/tor/-/issues/40424">https://gitlab.torproject.org/tpo/core/tor/-/issues/40424</a>. Hard
to tell,<br>
though. Does that issue happen regularly?<br>
<br>
Georg<br>
<br>
_______________________________________________<br>
tor-relays mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</blockquote>
</blockquote>
<br>
I didn't touch anything, and this morning the metrics say the bridge
is running normally, with an uptime of over 125 days.<br>
<br>
Looks like it might have been a metrics issue, not the bridge
itself.<br>
<br>
Cheers.<br>
<br>
</body>
</html>