Hello all, a couple of quick questions. Tor exited with this error: Dec 09 06:35:34.000 [err] descriptor at 0x62ee080 begins with unexpected string "". Is another process running in our data directory? Exiting. I've a vague feeling it's happened once before - anything to worry about? Also, on restarting Tor with Obfsproxy already running, I got Dec 09 14:14:43.000 [warn] Server managed proxy encountered a method error. (obfs3 Could not set up listener (0.0.0.0:xx) for 'obfs3' (Address already in use).) Dec 09 14:14:43.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed the configuration protocol and will be destroyed. does this mean that Tor is running without obfsproxy now, and I need to stop both and restart? It's quite annoying that Tor doesn't remember its auto-picked port, and I have to change the port-forwarding rule every time. Thanks, GD
On Thu, 10 Dec 2015 01:26:41 +0000 Geoff Down geoffdown@fastmail.net wrote:
[snip[
Also, on restarting Tor with Obfsproxy already running, I got Dec 09 14:14:43.000 [warn] Server managed proxy encountered a method error. (obfs3 Could not set up listener (0.0.0.0:xx) for 'obfs3' (Address already in use).) Dec 09 14:14:43.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed the configuration protocol and will be destroyed. does this mean that Tor is running without obfsproxy now, and I need to stop both and restart?
Yes. For what it's worth, newer versions of tor (0.2.7.x) has code to prevent this from happening on Linux systems by using prctl to force the kernel into cleaning up children with SIGTERM.
obfs4proxy also has the same prctl() trickery and additional code for non-Linux systems so it can self-terminate on parent exit.
It's quite annoying that Tor doesn't remember its auto-picked port, and I have to change the port-forwarding rule every time.
This should get persisted in the state file.
Regards,
On 10 Dec 2015, at 15:52, Yawning Angel yawning@schwanenlied.me wrote:
On Thu, 10 Dec 2015 01:26:41 +0000 Geoff Down geoffdown@fastmail.net wrote:
...
It's quite annoying that Tor doesn't remember its auto-picked port, and I have to change the port-forwarding rule every time.
This should get persisted in the state file.
It seems a few people are encountering this issue. https://trac.torproject.org/projects/tor/ticket/3511 https://trac.torproject.org/projects/tor/ticket/3511 (We'd love a patch to fix this!)
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP 968F094B
teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
On Thu, Dec 10, 2015, at 04:52 AM, Yawning Angel wrote:
On Thu, 10 Dec 2015 01:26:41 +0000 Geoff Down geoffdown@fastmail.net wrote:
[snip[
It's quite annoying that Tor doesn't remember its auto-picked port, and I have to change the port-forwarding rule every time.
This should get persisted in the state file.
Thanks Yawning The obfs port has been remembered, but not the Tor port. This is Tor 0.2.6.10 built from source on OSX10.4. Bug? GD
tor-relays@lists.torproject.org
-
Geoff Down -
Tim Wilson-Brown - teor -
Yawning Angel