Re: Tor Service

["Raghav Gururajan" <rvgn@disroot.org>]

>> Does /var/log/messages contain additional hints?
> 
> Will look into it and get back to you. :-)

Apr 23 19:55:57 localhost Tor[1]: Tor 0.3.4.11 (git-4fd31340f3355342) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.0.2p, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8. 
Apr 23 19:55:57 localhost Tor[1]: Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning 
Apr 23 19:55:57 localhost Tor[1]: Read configuration file "/gnu/store/a3gvm19f541951x0b84d3a71v5sxk9h2-torrc". 
Apr 23 19:55:57 localhost Tor[1]: Scheduler type KIST has been enabled. 
Apr 23 19:55:57 localhost Tor[1]: Opening Socks listener on 127.0.0.1:9050 
Apr 23 19:55:57 localhost Tor[1]: Parsing GEOIP IPv4 file /gnu/store/0mnwmb670xxzqanqbamjmli7nm0dlpyn-tor-0.3.4.11/share/tor/geoip. 
Apr 23 19:55:57 localhost Tor[1]: Parsing GEOIP IPv6 file /gnu/store/0mnwmb670xxzqanqbamjmli7nm0dlpyn-tor-0.3.4.11/share/tor/geoip6. 
Apr 23 19:55:57 localhost Tor[1]: Bootstrapped 0%: Starting 
Apr 23 19:55:57 localhost Tor[1]: Starting with guard context "default" 
Apr 23 15:55:58 localhost shepherd[1]: Service tor has been started. 
Apr 23 15:55:58 localhost shepherd[1]: Service iptables has been started. 
Apr 23 19:55:58 localhost Tor[1]: Bootstrapped 5%: Connecting to directory server 
Apr 23 19:55:58 localhost Tor[1]: Bootstrapped 10%: Finishing handshake with directory server 
Apr 23 19:55:59 localhost Tor[1]: Bootstrapped 15%: Establishing an encrypted directory connection 
Apr 23 19:55:59 localhost Tor[1]: Bootstrapped 20%: Asking for networkstatus consensus 
Apr 23 19:55:59 localhost Tor[1]: Bootstrapped 25%: Loading networkstatus consensus 
Apr 23 19:56:05 localhost Tor[1]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus. 
Apr 23 19:56:06 localhost Tor[1]: Bootstrapped 40%: Loading authority key certs 
Apr 23 19:56:06 localhost Tor[1]: The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services. 
Apr 23 19:56:06 localhost Tor[1]: Bootstrapped 45%: Asking for relay descriptors for internal paths 
Apr 23 19:56:06 localhost Tor[1]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6712, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 100% of end bw (no exits in consensus) = 0% of path bw.) 
Apr 23 19:56:07 localhost Tor[1]: Bootstrapped 50%: Loading relay descriptors for internal paths 
Apr 23 19:56:08 localhost Tor[1]: The current consensus contains exit nodes. Tor can build exit and internal paths. 
Apr 23 19:56:09 localhost Tor[1]: Bootstrapped 56%: Loading relay descriptors 
Apr 23 19:56:09 localhost Tor[1]: Bootstrapped 64%: Loading relay descriptors 
Apr 23 19:56:09 localhost Tor[1]: Bootstrapped 70%: Loading relay descriptors 
Apr 23 19:56:09 localhost Tor[1]: Bootstrapped 80%: Connecting to the Tor network 
Apr 23 19:56:10 localhost Tor[1]: Bootstrapped 85%: Finishing handshake with first hop 
Apr 23 19:56:10 localhost Tor[1]: Bootstrapped 90%: Establishing a Tor circuit 
Apr 23 19:56:11 localhost Tor[1]: Tor has successfully opened a circuit. Looks like client functionality is working. 
Apr 23 19:56:11 localhost Tor[1]: Bootstrapped 100%: Done
[...]
Apr 23 20:06:25 localhost Tor[1]: Catching signal TERM, exiting cleanly.

The above repeats on every boot.

Regards,
RG.