[tor-talk] starting tor using systemd, readiness issue

[Udo van den Heuvel <udovdh@xxxxxxxxx>]

Hello,

As I moved the firewall box to a UPS, upon startup I noticed an issue
with tor: it was being started over and over again by systemd.
The log has stuff like:

May 10 11:20:53.000 [notice] Tor 0.3.2.10 (git-31cc63deb69db819) opening
log file.
May 10 11:20:53.869 [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 1010007f: OpenSSL 1.1.0g-fips  2 Nov 2017; r
unning with 1010008f: OpenSSL 1.1.0h-fips  27 Mar 2018).
May 10 11:20:53.945 [notice] Tor 0.3.2.10 (git-31cc63deb69db819) running
on Linux with Libevent 2.0.22-stable, OpenSSL 1.1.0h-fips, Zlib 1.2.11,
Liblzma 5.2.3, and Libzstd 1.3.4.
May 10 11:20:53.945 [notice] Tor can't help you if you use it wrong!
Learn how to be safe at https://www.torproject.org/download/download#warning
May 10 11:20:53.945 [notice] Read configuration file
"/usr/share/tor/defaults-torrc".
May 10 11:20:53.945 [notice] Read configuration file "/etc/tor/torrc".
May 10 11:20:53.954 [warn] You have asked to exclude certain relays from
all positions in your circuits. Expect hidden services and other Tor
features to be broken in unpredictable ways.
May 10 11:20:53.955 [notice] Scheduler type KIST has been enabled.
May 10 11:20:53.955 [notice] Opening Socks listener on 127.0.0.1:9050
May 10 11:20:53.955 [notice] Opening Control listener on 127.0.0.1:9051
May 10 11:20:53.955 [notice] Opening OR listener on 0.0.0.0:9001
May 10 11:20:53.955 [notice] Opening Extended OR listener on 127.0.0.1:0
May 10 11:20:53.955 [notice] Extended OR listener listening on port 44271.
May 10 11:20:53.955 [notice] Opening Directory listener on 0.0.0.0:9030
May 10 11:20:55.000 [notice] Your Tor server's identity key fingerprint
is 'x'
May 10 11:20:55.000 [notice] Configured hibernation.  This interval
began at 2018-05-09 12:21:00; the scheduled wake-up time was 2018-05-09
12:21:00; we expect to exhaust our quota for this interval around 2
018-05-10 12:21:00; the next interval begins at 2018-05-10 12:21:00 (all
times local)
May 10 11:20:55.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
May 10 11:20:56.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
May 10 11:20:56.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.
May 10 11:20:56.000 [notice] Bootstrapped 0%: Starting
May 10 11:21:25.000 [notice] Starting with guard context "default"
May 10 11:21:25.000 [notice] Bootstrapped 80%: Connecting to the Tor network
May 10 11:21:25.000 [notice] Signaled readiness to systemd
May 10 11:21:25.000 [notice] Interrupt: we have stopped accepting new
connections, and will shut down in 30 seconds. Interrupt again to exit now.
May 10 11:21:59.000 [notice] Tor 0.3.2.10 (git-31cc63deb69db819) opening
log file.
(etc)

So tor communicates readines to systemd but still they think tor is not
starting OK.
How can I fix this?

Of course without systemd things work better: I can start tor from the
commandline without problems.


Udo
-- 
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk