[network-health] Bridge status

[Georg Koppen]

Bruno Grossmann:
> Hello,
> 
> I have installed a bridge in December 2021. It has been running 
> seamlessly - until recently. For the last week or so, when I check the 
> status page, it says it is down. Yet, when I check on the server, it 
> seems to be running fine (see output below). Is it an issue with the 
> bridge checking mechanism or is there a real issue with my bridge? In 
> other words, what information would I be looking for to ensure my bridge 
> is up?

You could check with bridgestrap to test the bridge by visiting 
https://bridges.torproject.org/status?id=[fingerprint]

There might be other options, I am not sure. I am not sure either how 
many anti-censorship folks are on this list. So, maybe asking on our 
forum[1] or the tor-relays@ mailing list[2] might give you even better 
answers.

Thanks,
Georg

[1] https://forum.torproject.net/c/support/relay-operator/17
[2] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

> [root at li1228-97 ~]# systemctl status tor-master.service
> ● tor-master.service - Anonymizing overlay network for TCP 
> (multi-instance master)
>     Loaded: loaded (/usr/lib/systemd/system/tor-master.service; 
> disabled; vendor preset: disabled)
>     Active: active (exited) since Wed 2022-03-16 12:20:43 UTC; 22h ago
>    Process: 19224 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
>   Main PID: 19224 (code=exited, status=0/SUCCESS)
>      Tasks: 0
>     CGroup: /system.slice/tor-master.service
> 
> Mar 16 12:20:43 li1228-97 systemd[1]: Stopped Anonymizing overlay 
> network for TCP (multi-instance master).
> Mar 16 12:20:43 li1228-97 systemd[1]: Stopping Anonymizing overlay 
> network for TCP (multi-instance master)...
> Mar 16 12:20:43 li1228-97 systemd[1]: Starting Anonymizing overlay 
> network for TCP (multi-instance master)...
> Mar 16 12:20:43 li1228-97 systemd[1]: Started Anonymizing overlay 
> network for TCP (multi-instance master).
> [root at li1228-97 ~]# systemctl status -l tor
> ● tor.service - Anonymizing overlay network for TCP
>     Loaded: loaded (/usr/lib/systemd/system/tor.service; enabled; vendor 
> preset: disabled)
>     Active: active (running) since Wed 2022-03-16 12:21:13 UTC; 22h ago
>    Process: 19238 ExecStartPre=/usr/bin/tor --runasdaemon 0 
> --defaults-torrc /usr/share/tor/defaults-torrc -f /etc/tor/torrc 
> --verify-config (code=exited, status=0/SUCCESS)
>   Main PID: 19240 (tor)
>      Tasks: 9
>     CGroup: /system.slice/tor.service
>             ├─19240 /usr/bin/tor --runasdaemon 0 --defaults-torrc 
> /usr/share/tor/defaults-torrc -f /etc/tor/torrc
>             └─19242 /usr/local/bin/obfs4proxy
> 
> Mar 17 06:21:43 li1228-97 Tor[19240]: Heartbeat: In the last 6 hours, I 
> have seen 0 unique clients.
> Mar 17 06:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address 
> [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. 
> However, IPv4 address is reachable. Publishing server descriptor without 
> IPv6 address. [2 similar message(s) suppressed in last 2400 seconds]
> Mar 17 07:34:47 li1228-97 Tor[19240]: No circuits are opened. Relaxed 
> timeout for circuit 673 (a Measuring circuit timeout 3-hop circuit in 
> state doing handshakes with channel state open) to 60000ms. However, it 
> appears the circuit has timed out anyway. [7 similar message(s) 
> suppressed in last 10020 seconds]
> Mar 17 07:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address 
> [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. 
> However, IPv4 address is reachable. Publishing server descriptor without 
> IPv6 address. [2 similar message(s) suppressed in last 2400 seconds]
> Mar 17 08:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address 
> [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. 
> However, IPv4 address is reachable. Publishing server descriptor without 
> IPv6 address. [2 similar message(s) suppressed in last 2400 seconds]
> Mar 17 09:24:48 li1228-97 Tor[19240]: No circuits are opened. Relaxed 
> timeout for circuit 718 (a Testing circuit 3-hop circuit in state doing 
> handshakes with channel state open) to 60000ms. However, it appears the 
> circuit has timed out anyway. [2 similar message(s) suppressed in last 
> 6600 seconds]
> Mar 17 09:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address 
> [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. 
> However, IPv4 address is reachable. Publishing server descriptor without 
> IPv6 address. [2 similar message(s) suppressed in last 2400 seconds]
> Mar 17 09:51:50 li1228-97 Tor[19240]: Your network connection speed 
> appears to have changed. Resetting timeout to 60000ms after 18 timeouts 
> and 462 buildtimes.
> Mar 17 10:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address 
> [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. 
> However, IPv4 address is reachable. Publishing server descriptor without 
> IPv6 address. [2 similar message(s) suppressed in last 2400 seconds]
> Mar 17 10:45:46 li1228-97 Tor[19240]: No circuits are opened. Relaxed 
> timeout for circuit 850 (a Testing circuit 3-hop circuit in state doing 
> handshakes with channel state open) to 60000ms. However, it appears the 
> circuit has timed out anyway. [1 similar message(s) suppressed in last 
> 4860 seconds]
> 
> 
> _______________________________________________
> network-health mailing list
> network-health at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/network-health

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/network-health/attachments/20220321/5baeb5a0/attachment.sig>