[tor-relays] Debugging my small relay

[Markus Hitter]

Hello all,

for somewhat over a year now I run a Tor relay on my router. The router
in turn is running OpenWRT. It's this one:

https://globe.torproject.org/#/relay/A52C51551F3BD6A68E778720E02B53303F014EB2
https://atlas.torproject.org/#details/A52C51551F3BD6A68E778720E02B53303F014EB2

Not much, but let it be one of my small shares for improving humanity :-)

A few days ago I upgraded OpenWRT from 14.07 to 15.05, the latest
release. Reinstalled the package 'tor', kept the old config file and the
server started apparently smoothly. Previous Tor version was 0.2.4.22,
now it's 0.2.5.12. I'm aware that these aren't exactly the latest, but
that's what OpenWRT's package manager offers.

As you can see in the link above, the relay is no longer recognized as
'running'. They don't recognize the new Tor version, don't recognize the
restart.

To what I know, /var/log/tor/notices.log looks fine, a few excerpts:

Jan 02 14:34:36.000 [notice] Tor 0.2.5.12 (git-99d0579ff5e0349f) opening
new log file.
[... clock synchrionisation works :-) ...]
Jan 04 17:35:42.000 [warn] Your system clock just jumped 183652 seconds
forward; assuming established circuits no longer work.
[...]
Jan 04 17:38:09.000 [notice] Now checking whether ORPort x.x.x.x:9001 is
reachable... (this may take up to 20 minutes -- look for log messages
indicating success)
Jan 04 17:38:15.000 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
[...]
Jan 06 11:35:42.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00
hours, with 0 circuits open. I've sent 68.73 MB and received 85.15 MB.
Jan 06 11:35:42.000 [notice] Average packaged cell fullness: 76.757%
Jan 06 11:35:42.000 [notice] TLS write overhead: 9%
Jan 06 11:35:42.000 [notice] Circuit handshake stats since last time:
9/9 TAP, 0/0 NTor.


How could I find out about what's going wrong?


Thanks,
Markus

-- 
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
http://www.jump-ing.de/