On 10-05-18 11:34, Udo van den Heuvel wrote: > 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?
TimeoutStartSec=60 in tor.service helps; starting tor works again. But is that the correct solution? Can't tor signal readiness sooner? Kind regards, Udo -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk