I restarted my tor server a couple of hours ago, and since then, it has
been acting very peculiarly. Here are the notice-level log file entries since
startup. Note that I deleted cached-descriptors and cached-descriptors.new
after shutting down tor and before shutting down the system several hours prior
to this startup.
Nov 20 06:29:05.896 [notice] Tor 0.2.0.12-alpha (r12518) opening log file.
Nov 20 06:29:05.903 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
Nov 20 06:29:10.660 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 0232 2050 5A55 0D6F DF0C 20FF 7C48 E66B A06A 49A6'
Nov 20 06:29:17.629 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1314 usable descriptors.
Nov 20 06:29:20.027 [notice] I learned some more directory information, but not enough to build a circuit: We have only 2/1314 usable descriptors.
Nov 20 06:29:21.525 [notice] I learned some more directory information, but not enough to build a circuit: We have only 49/1314 usable descriptors.
Nov 20 06:29:22.491 [notice] I learned some more directory information, but not enough to build a circuit: We have only 98/1314 usable descriptors.
Nov 20 06:29:23.550 [notice] I learned some more directory information, but not enough to build a circuit: We have only 149/1314 usable descriptors.
Nov 20 06:29:24.726 [notice] I learned some more directory information, but not enough to build a circuit: We have only 198/1314 usable descriptors.
Nov 20 06:29:25.751 [notice] I learned some more directory information, but not enough to build a circuit: We have only 252/1314 usable descriptors.
Nov 20 06:29:26.006 [notice] I learned some more directory information, but not enough to build a circuit: We have only 252/1314 usable descriptors.
Nov 20 06:29:26.909 [notice] I learned some more directory information, but not enough to build a circuit: We have only 302/1314 usable descriptors.
Nov 20 06:29:27.859 [notice] We now have enough directory information to build circuits.
Nov 20 06:29:27.981 [warn] Nickname list includes 'yourd0f670b45a' which isn't a known router.
Nov 20 06:29:37.281 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Nov 20 06:29:37.282 [notice] Now checking whether ORPort 66.225.36.5:995 and DirPort 66.225.36.5:443 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Note that the above address was incorrect. The correct address was, and
still is, 66.225.42.30. It has not changed since before the system was
rebooted.
Nov 20 06:30:33.280 [notice] Your IP address seems to have changed. Updating.
Nov 20 06:30:51.123 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 20 06:30:56.775 [notice] Performing bandwidth self-test...done.
Nov 20 06:30:59.538 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Nov 20 06:31:39.584 [warn] We just marked ourself as down. Are your external addresses reachable?
Nov 20 06:55:32.625 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Nov 20 06:55:47.924 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Nov 20 06:56:06.538 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'fissefjaes'. Retrying on a new circuit.
Nov 20 06:56:54.155 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TFTor'. Retrying on a new circuit.
Nov 20 06:56:54.157 [notice] Tried for 121 seconds to get a connection to [scrubbed]:80. Giving up.
Nov 20 06:57:04.521 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Nov 20 06:57:04.525 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Nov 20 06:58:39.288 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TorNetwork'. Retrying on a new circuit.
Nov 20 06:58:44.334 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TorNetwork'. Retrying on a new circuit.
Nov 20 07:15:04.708 [notice] Your IP address seems to have changed. Updating.
Nov 20 07:15:28.734 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 20 07:30:19.742 [notice] Your IP address seems to have changed. Updating.
Nov 20 07:30:38.206 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 20 07:30:49.831 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Nov 20 08:00:49.710 [notice] Your IP address seems to have changed. Updating.
Nov 20 08:01:06.195 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 20 08:20:49.474 [warn] Your server (66.225.36.5:443) has not managed to confirm that its DirPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
Note that it has reported using the wrong address again. The address
shown is the one that was in use before the system was shut down several hours
earlier. (I use the free service of dyndns.org to yield the current IP address
for the host+domain name coded in the torrc file.)
I'm going to shut tor down and restart it, but it would be really nice to
know what went wrong and how to avoid it in the future.
Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet: bennett at cs.niu.edu *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good *
* objection to the introduction of that bane of all free governments *
* -- a standing army." *
* -- Gov. John Hancock, New York Journal, 28 January 1790 *
**********************************************************************