<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Hi,<br>
      <br>
      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.<br>
      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.<br>
      <br>
      Cord<br>
      <br>
      On 06.01.2022 19:52, Eddie wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:cdafe95c-db58-a3c1-156c-46261ca0f821@attglobal.net">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      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.<br>
      <br>
      Guess I'll keep an eye on the metrics to see if it pops back to
      available.<br>
      <br>
      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.<br>
      <br>
      Cheers.<br>
      <br>
      <br>
      <br>
      <br>
      <div class="moz-cite-prefix">On 10/14/2021 12:11 PM, Eddie wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:c441a73e-2a27-6ccd-0c18-d00e2a423868@attglobal.net">
        <meta http-equiv="Content-Type" content="text/html;
          charset=UTF-8">
        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-txt-link-freetext" 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"
              moz-do-not-send="true">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 moz-txt-link-freetext"
              href="mailto:tor-relays@lists.torproject.org"
              moz-do-not-send="true">tor-relays@lists.torproject.org</a><br>
            <a class="moz-txt-link-freetext"
              href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays"
              moz-do-not-send="true">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>
        <br>
        <fieldset class="moz-mime-attachment-header"></fieldset>
        <pre class="moz-quote-pre" wrap="">_______________________________________________
tor-relays mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:tor-relays@lists.torproject.org" moz-do-not-send="true">tor-relays@lists.torproject.org</a>
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" moz-do-not-send="true">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a>
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
tor-relays mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a>
<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>
</pre>
    </blockquote>
    <br>
  </body>
</html>