<html><head></head><body><div class="ydpe4a53c53yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div>The log you provided shows 0 circuits open. Something is not right with that instance. I know 124 days of uptime is a great achievement, but it might be time to restart that instance.</div><div><br></div><div>Did a medium-term key not update properly or the like?</div><div><br></div><div>Respectfully,</div><div><br></div><div><br></div><div>Gary</div><div class="ydpe4a53c53signature">—<br>This Message Originated by the Sun.<br>iBigBlue 63W Solar Array (~12 Hour Charge)<br>+ 2 x Charmast 26800mAh Power Banks<br>= iPhone XS Max 512GB (~2 Weeks Charged)</div></div>
        <div><br></div><div><br></div>
        
        <div id="ydpe4a53c53yahoo_quoted_4304685538" class="ydpe4a53c53yahoo_quoted">
            <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
                
                <div>
                    On Thursday, October 14, 2021, 5:10:53 AM PDT, Bleedangel Tor Admin <tor@bleedangel.com> wrote:
                </div>
                <div><br></div>
                <div><br></div>
                <div><div id="ydpe4a53c53yiv1463508461"><div>   You are running 0.4.5.8, maybe updating to a newer version of tor will help?<br clear="none"><div><br clear="none"></div><div id="ydpe4a53c53yiv1463508461protonmail_mobile_signature_block"><div>Sent from ProtonMail for iOS</div></div> <div><br clear="none"></div><div><div class="ydpe4a53c53yiv1463508461yqt2426682402" id="ydpe4a53c53yiv1463508461yqtfd80233"><br clear="none"></div></div><div class="ydpe4a53c53yiv1463508461yqt2426682402" id="ydpe4a53c53yiv1463508461yqtfd94475">On Thu, Oct 14, 2021 at 03:02, Georg Koppen <<a shape="rect" class="ydpe4a53c53yiv1463508461" href="mailto:gk@torproject.org" rel="nofollow" target="_blank">gk@torproject.org</a>> wrote:<blockquote class="ydpe4a53c53yiv1463508461protonmail_quote" type="cite">  Eddie:<br clear="none">> Looking at tor metrics, one of my bridges is showing as off-line:<br clear="none">> B080140DC1BAB5B86D1CE5A4CA2EF64F20282440<br clear="none">><br clear="none">> However, the log isn't showing any issues:<br clear="none">><br clear="none">> Oct 14 00:00:28.000 [notice] Tor 0.4.5.8 opening new log file.<br clear="none">> Oct 14 00:00:28.000 [notice] Configured hibernation.  This interval<br clear="none">> began at 2021-10-14 00:00:00; the scheduled wake-up time was 2021-10-14<br clear="none">> 00:00:00; we expect to exhaust our quota for this interval around<br clear="none">> 2021-10-15 00:00:00; the next interval begins at 2021-10-15 00:00:00<br clear="none">> (all times local)<br clear="none">> Oct 14 01:49:40.000 [notice] Heartbeat: Tor's uptime is 124 days 6:00<br clear="none">> hours, with 0 circuits open. I've sent 907.23 GB and received 922.28 GB.<br clear="none">> I've received 63052 connections on IPv4 and 8375 on IPv6. I've made<br clear="none">> 512684 connections with IPv4 and 100974 with IPv6.<br clear="none">> Oct 14 01:49:40.000 [notice] While not bootstrapping, fetched this many<br clear="none">> bytes: 1801791624 (server descriptor fetch); 175792 (server descriptor<br clear="none">> upload); 221750347 (consensus network-status fetch); 10974 (authority<br clear="none">> cert fetch); 19905655 (microdescriptor fetch)<br clear="none">> Oct 14 01:49:40.000 [notice] Heartbeat: Accounting enabled. Sent: 140.52<br clear="none">> MB, Received: 140.69 MB, Used: 281.21 MB / 200.00 GB, Rule: sum. The<br clear="none">> current accounting interval ends on 2021-10-15 00:00:00, in 22:10 hours.<br clear="none">> Oct 14 01:49:40.000 [notice] Heartbeat: In the last 6 hours, I have seen<br clear="none">> 14 unique clients.<br clear="none">><br clear="none">> Initially I thought of a previous issue I had with IPv6 connectivity,<br clear="none">> but don't think this is the problem here as the 2nd bridge on the same<br clear="none">> server is showing on-line.  Also an IPv6 port scan shows the ports for<br clear="none">> both bridges as accessible.<br clear="none">><br clear="none">> Ideas ??<br clear="none"><br clear="none">I wonder whether that is another instance<br clear="none">https://gitlab.torproject.org/tpo/core/tor/-/issues/40424. Hard to tell,<br clear="none">though. Does that issue happen regularly?<br clear="none"><br clear="none">Georg<br clear="none"><br clear="none">_______________________________________________<br clear="none">tor-relays mailing list<br clear="none">tor-relays@lists.torproject.org<br clear="none">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br clear="none"></blockquote><div><br clear="none"></div><div><br clear="none"></div></div></div></div><div class="ydpe4a53c53yqt2426682402" id="ydpe4a53c53yqtfd26242">_______________________________________________<br clear="none">tor-relays mailing list<br clear="none"><a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a><br clear="none"><a shape="rect" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="nofollow" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br clear="none"></div></div>
            </div>
        </div></div></body></html>