[tor-bugs] #6979 [Tor]: TBB Bug: router.c:164
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Jul 19 20:02:08 UTC 2013
#6979: TBB Bug: router.c:164
-----------------------+----------------------------------------------------
Reporter: eli | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor | Version: Tor: 0.2.3.25
Resolution: | Keywords: tor-bridge tor-relay
Parent: | Points:
Actualpoints: |
-----------------------+----------------------------------------------------
Comment(by thefliegendeeep):
I misconfigured things. /etc/tor/torrc was owned by root with 0600. Still
a bug, but that seems to be why it occurs. Logs contained more important
info too:
Jul 17 04:20:55.000 [notice] Heartbeat: Tor's uptime is 1 day 6:00 hours,
with 2053 circuits open. I've sent 1.59 GB and received 1.50 GB.
Jul 17 06:25:02.000 [notice] Received reload signal (hup). Reloading
config and resetting internal state.
Jul 17 06:25:02.000 [notice] Read configuration file "/usr/share/tor/tor-
service-defaults-torrc".
Jul 17 06:25:02.000 [warn] Couldn't find $HOME environment variable while
expanding "~/.torrc"; defaulting to "".
Jul 17 06:25:02.000 [notice] Configuration file "/etc/tor/torrc" not
present, using reasonable defaults.
Jul 17 06:25:02.000 [notice] Opening Socks listener on 127.0.0.1:9050
Jul 17 06:25:02.000 [notice] Closing no-longer-configured Control listener
on 127.0.0.1:9051
Jul 17 06:25:02.000 [notice] Closing no-longer-configured Directory
listener on 0.0.0.0:80
Jul 17 06:25:02.000 [notice] Closing no-longer-configured OR listener on
0.0.0.0:443
Jul 17 06:25:02.000 [notice] Tor 0.2.3.25 (git-3fed5eb096d2d187) opening
new log file.
Jul 17 06:25:02.000 [notice] Closing old Control listener on
127.0.0.1:9051
Jul 17 06:25:02.000 [notice] Closing old Directory listener on 0.0.0.0:80
Jul 17 06:25:02.000 [notice] Closing old OR listener on 0.0.0.0:443
Jul 17 06:25:03.000 [err] get_server_identity_key(): Bug: router.c:171:
get_server_identity_key: Assertion server_mode(get_options()) failed;
aborting.
Jul 19 05:07:55.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with
53 circuits open. I've sent 1.34 GB and received 1.28 GB.
Jul 19 06:25:02.000 [notice] Received reload signal (hup). Reloading
config and resetting internal state.
Jul 19 06:25:02.000 [notice] Read configuration file "/usr/share/tor/tor-
service-defaults-torrc".
Jul 19 06:25:02.000 [warn] Couldn't find $HOME environment variable while
expanding "~/.torrc"; defaulting to "".
Jul 19 06:25:02.000 [notice] Configuration file "/etc/tor/torrc" not
present, using reasonable defaults.
Jul 19 06:25:02.000 [notice] Opening Socks listener on 127.0.0.1:9050
Jul 19 06:25:02.000 [notice] Closing no-longer-configured Control listener
on 127.0.0.1:9051
Jul 19 06:25:02.000 [notice] Closing no-longer-configured Directory
listener on 0.0.0.0:80
Jul 19 06:25:02.000 [notice] Closing no-longer-configured OR listener on
0.0.0.0:443
Jul 19 06:25:02.000 [notice] Tor 0.2.3.25 (git-3fed5eb096d2d187) opening
new log file.
Jul 19 06:25:02.000 [notice] Closing old Control listener on
127.0.0.1:9051
Jul 19 06:25:02.000 [notice] Closing old Directory listener on 0.0.0.0:80
Jul 19 06:25:02.000 [notice] Closing old OR listener on 0.0.0.0:443
Jul 19 11:07:55.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with
1 circuits open. I've sent 2.01 GB and received 1.93 GB.
Jul 19 17:07:55.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with
2 circuits open. I've sent 2.02 GB and received 1.94 GB.
So, im assuming that it starts with enough privileges to read the config,
runs as a server, then receives the reload signal, doesnt have enough
privileges anymore, thus defaults to not being a server, but some code can
still be running thinking it is, hence the assertion error once.
Still try and get a stacktrace? Maybe send some sighups as well. I could
also just fix the permission problem...
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6979#comment:17>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list