once again: all technology can be used for good (activist wants to know more without beeing tracked down bit Exxon Mobile’s arm of Booz Allen Hamilton) or evil. (hacker asking for ransom bitcoins via tor hidden service)

booz-allan-hamilton-is-making-billions-every-year-by-spying-nsa-and-cia

„Privacy for the Weak – Transparency for the Powerful“ that would be it.

That’s why tor exists and hopefully continues to work.

if you wonder why your tor relay can not be found here: https://atlas.torproject.org/

it’s time to check the log-files.

less /var/log/tor/log
# you could press shift+f to "follow" any changes that occur to the logfile in realtime

Sep 23 09:55:05.000 [notice] SIGINT received while hibernating; exiting now.
Sep 23 09:55:06.000 [notice] Tor 0.2.8.7 (git-cc2f02ef17899f86) opening log file.
Sep 23 09:55:06.719 [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000106f: OpenSSL 1.0.1f 6 Jan 2014; running with 1000114f: OpenSSL 1.0.1t  3 May 2016).
Sep 23 09:55:06.000 [warn] Failed to unlink /var/lib/tor/bw_accounting: No such file or directory
Sep 23 09:55:06.000 [notice] Not advertising Directory Service support (Reason: AccountingMax enabled)
Sep 23 09:55:06.000 [notice] Your Tor server'
s identity key fingerprint is 'nickname CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC'
Sep 23 09:55:06.000 [notice] Configured hibernation.  This interval began at 2016-09-01 00:00:00; the scheduled wake-up time was 2016-09-03 04:51:47; we expect to exhaust our quota for this interval around 2016-09-27 07:53:47; the next interval begins at 2016-10-01 00:00:00 (all
 times local)
Sep 23 09:55:06.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 23 09:55:07.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 23 09:55:07.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.
Sep 23 09:55:07.000 [notice] Bootstrapped 0%: Starting
Sep 23 09:55:24.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Sep 23 09:55:24.000 [notice] Opening Socks listener on /var/run/tor/socks
Sep 23 09:55:24.000 [notice] Opening Control listener on /var/run/tor/control
Sep 23 09:55:25.000 [notice] Bandwidth soft limit reached; commencing hibernation. No new connections will be accepted

so the keywords here are „limit reached“ and „hibernation“.

if the limits of the tor accounting (traffic per day/month) are reached you can find this in your log file.

when checking config file i realized:

vim /etc/tor/torrc

RelayRelayBandwidthRate 100 KBytes  # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)

## Set a maximum of 40 gigabytes each way per period.
AccountingMax 4 GBytes

## Each period starts daily at midnight (AccountingMax is per day)
# AccountingStart day 00:00 <- I FORGOT TO COMMENT OUT THIS THING :-D

# restart tor, and recheck logs
service tor restart

less /var/log/tor/log
# you could press shift+f to "follow" any changes that occur to the logfile in realtime

Sep 23 09:58:21.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Sep 23 09:58:21.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Sep 23 09:58:21.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.
Sep 23 09:58:21.000 [notice] Bootstrapped 0%: Starting
Sep 23 09:58:31.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Sep 23 09:58:31.000 [notice] Opening Socks listener on /var/run/tor/socks
Sep 23 09:58:31.000 [notice] Opening Control listener on /var/run/tor/control
Sep 23 09:58:32.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Sep 23 09:58:32.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Sep 23 09:58:32.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Sep 23 09:58:32.000 [notice] Bootstrapped 100%: Done
Sep 23 09:58:32.000 [notice] Now checking whether ORPort XXX.XXX.XXX.XXX:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Sep 23 09:58:33.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Sep 23 09:58:34.000 [notice] Performing bandwidth self-test...done.

that looks way better know. wait a little then recheck at: https://atlas.torproject.org/

Links:

https://www.torproject.org/docs/faq.html.en#Hibernation

admin