Opened 7 months ago

Last modified 5 months ago

#33757 assigned defect

Fix log message when multiple tors try the same data directory

Reported by: teor Owned by: asn
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version: Tor: 0.4.2.7
Severity: Normal Keywords: 044-should, 035-backport-maybe, 041-backport-maybe, 042-backport, 043-backport, postfreeze-ok
Cc: nickm Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description (last modified by teor)

When a user launches two tor processes in the same data directory, they get these confusing logs:

Mar 29 17:45:08.000 [warn] It looks like another Tor process is running with the same data directory.  Waiting 5 seconds to see if it goes away.
Mar 29 17:45:13.000 [err] No, it's still there.  Exiting.
Mar 29 17:45:13.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.4.2.7 )
Mar 29 17:45:13.000 [err] Reading config failed--see warnings above.
Mar 29 19:55:41.000 [notice] Catching signal TERM, exiting cleanly.

Full logs:
https://lists.torproject.org/pipermail/tor-relays/2020-March/018306.html

I don't think the bug log should be there.

Child Tickets

Change History (4)

comment:1 Changed 7 months ago by teor

Maybe nickm will have a better idea why this is happening.

Could it be due to our config refactor?

comment:2 Changed 7 months ago by teor

Description: modified (diff)

comment:3 Changed 5 months ago by nickm

Keywords: postfreeze-ok added

Mark tickets which are important or safe enough to look at post-freeze for 0.4.4.

comment:4 Changed 5 months ago by nickm

Owner: set to asn
Status: newassigned
Note: See TracTickets for help on using tickets.