[tor-relays] OrPort self-testing sometimes fails

[Julien ROBIN]

Hi everybody,

Second time it happen to me so I would like to know if you have ideas about it.
Sometimes after a reboot, I haven't the following message into the log :

"Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor."

And after a while (fortunately), I receive a warning (Tor Weather) because my server is shown as offline.

So I just type /etc/init.d/tor stop and /etc/init.d/tor start, and it works fine.

I would like to know how does the test works, in order to check what can fail during the test.
If my server's IP (95.130.9.190) is not reachable by a part of the Internet for example, in order to open a support ticket with my ISP (do you know how I can easily check it ?).

Also, since few month now, the bandwith usage seems to keeps far below what I had before (even with a good consensus weight, fresh OS install with new keys and name a month ago) so I now realize that may be there is a problem somewhere with this machine.

Thank you in advance for your help and ideas !

Best Regards,
Julien ROBIN


----
Please find below the logs of the "failed" start, followed by the "working" start


Nov 21 11:56:53.000 [notice] Tor 0.2.5.10 (git-43a5f3d91e726291) opening log file.
Nov 21 11:56:53.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Nov 21 11:56:53.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Nov 21 11:56:53.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Nov 21 11:56:53.000 [notice] Caching new entry debian-tor for debian-tor
Nov 21 11:56:53.000 [notice] Caching new entry debian-tor for debian-tor
Nov 21 11:56:53.000 [notice] Your Tor server's identity key fingerprint is 'MagnetronFR1 145AEE9359A8943189500C5451722CAA7EEEC6C3'
Nov 21 11:56:53.000 [notice] Bootstrapped 0%: Starting
Nov 21 11:56:57.000 [notice] We now have enough directory information to build circuits.
Nov 21 11:56:57.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Nov 21 11:56:57.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Nov 21 11:56:58.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Nov 21 11:57:00.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Nov 21 11:57:00.000 [notice] Bootstrapped 100%: Done
Nov 21 13:56:58.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now.
Nov 21 13:57:28.000 [notice] Clean shutdown finished. Exiting.


Nov 21 13:57:39.000 [notice] Tor 0.2.5.10 (git-43a5f3d91e726291) opening log file.
Nov 21 13:57:39.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Nov 21 13:57:39.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Nov 21 13:57:39.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
Nov 21 13:57:39.000 [notice] Caching new entry debian-tor for debian-tor
Nov 21 13:57:39.000 [notice] Caching new entry debian-tor for debian-tor
Nov 21 13:57:39.000 [notice] Your Tor server's identity key fingerprint is 'MagnetronFR1 145AEE9359A8943189500C5451722CAA7EEEC6C3'
Nov 21 13:57:39.000 [notice] Bootstrapped 0%: Starting
Nov 21 13:57:39.000 [notice] Bootstrapped 5%: Connecting to directory server
Nov 21 13:57:41.000 [notice] We now have enough directory information to build circuits.
Nov 21 13:57:41.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Nov 21 13:57:41.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Nov 21 13:57:41.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 21 13:57:43.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Nov 21 13:57:44.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Nov 21 13:57:44.000 [notice] Bootstrapped 100%: Done