We have an application that's trying to connect to Tor, and when Tor starts, it blocks for about 15 seconds before responding on the control port.
This is the behaviour we are observing:
Nov 16 13:21:17.969 [notice] Opening Control listener on 127.0.0.1:39069 Nov 16 13:21:17.969 [notice] Opened Control listener connection (ready) on 127.0.0.1:39069 Nov 16 12:21:18 starting application Nov 16 13:21:33.000 [notice] Starting with guard context "default" Nov 16 12:21:33 tor connected Nov 16 13:21:33.000 [notice] New control connection opened from 127.0.0.1. Nov 16 13:21:33.000 [notice] New control connection opened from 127.0.0.1. Nov 16 13:21:33.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
As soon as Tor has opened its control port, we send the auth cookie to the port but we wait for the ok back from Tor. But this only happens after tor prints
Starting with guard context "default"
The question is, what is Tor doing between opening the control port and printing that out? It looks like something is blocking Tor. It's not doing the same behaviour on PC.
Is there something we can enable to see better logs and see what Tor is doing and how we can remove that blocker?
After that startup, if Tor is kept open, it will always respond fairly quickly. It's just on the initial startup where something is blocking.