[solved]WDR3600 won't run Tor server on Gargoyle 1.10.0

[ysy]

Hi all,

Pls help. My hardware set runs Tor server ok on 1.8.1 but won't work on 1.9.2 or 1.10.0

Attach error log and Tor setup: -
-----error log-----
Sun Oct 29 07:10:00 2017 user.notice root: Tor seems to have died unexpectedly, restarting
Sun Oct 29 07:10:05 2017 daemon.notice Tor[989]: Tor 0.3.1.7 (git-6babd3d9ba9318b3) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2l, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A.
Sun Oct 29 07:10:05 2017 daemon.notice Tor[989]: Tor can't help you if you use it wrong! Learn how to be safe at h**ps://***.torproject.o*g/download/download#warning
Sun Oct 29 07:10:05 2017 daemon.notice Tor[989]: Read configuration file "/etc/tor/torrc".
Sun Oct 29 07:10:05 2017 daemon.notice Tor[989]: Based on detected system memory, MaxMemInQueues is set to 256 MB. You can override this by setting MaxMemInQueues by hand.
Sun Oct 29 07:10:05 2017 daemon.warn Tor[989]: Being a directory cache (default) with less than DIRCACHE_MIN_MEM_MB MB of memory is not recommended and may consume most of the available resources, consider disabling this functionality by setting the DirCache option to 0.
Sun Oct 29 07:10:05 2017 daemon.warn Tor[989]: ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible.
Sun Oct 29 07:10:05 2017 daemon.notice Tor[989]: Opening Control listener on 127.0.0.1:9051
Sun Oct 29 07:10:05 2017 daemon.notice Tor[989]: Opening OR listener on 0.0.0.0:9090
Sun Oct 29 07:10:05 2017 daemon.notice Tor[989]: Configured to measure directory request statistics, but no GeoIP database found. Please specify a GeoIP database using the GeoIPFile option.
Sun Oct 29 07:10:05 2017 daemon.warn Tor[989]: Directory /usr/lib/tor/keys cannot be read: Too many levels of symbolic links
Sun Oct 29 07:10:05 2017 daemon.err Tor[989]: Error initializing keys; exiting
Sun Oct 29 07:11:00 2017 user.notice root: Tor seems to have died unexpectedly, restarting

-----tor setup-----
Bridge/Relay Port: 9090
Max Relay Bandwidth: 500 kBytes/s
Node Nickname (optional): damies
Contact email / PGP PubKey (optional): power.t@the.people
Tor Data Directory: /usr/lib/tor

[Lantis]

What router, and is tor installed by default or as a plugin?
Are you using external plugin root?
Did you preserve settings or set it up from scratch?

[ispyisail]

I never tested the TOR server, only the TOR client

client seams to work fine

[ispyisail]

Looks like there is something wrong with the TOR server?

Code: Select all

Sun Oct 29 16:32:00 2017 user.notice root: Tor seems to have died unexpectedly, restarting
Sun Oct 29 16:32:01 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:02 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:03 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:04 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:06 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:07 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:08 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:09 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:11 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:13 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:15 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:17 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:19 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:21 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:23 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:25 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused
Sun Oct 29 16:32:27 2017 daemon.err uhttpd[1642]: nc: can't connect to remote host (127.0.0.1): Connection refused

[ysy]

Thanks for asking. It's TPLink WDR3600 v1.4
1) Firmware update from 1.8.1, no attempt to preserve settings.
2) Format 1GB USB stick, 75% external root. 25% swap. External root on /dev/sdb1.
3) Install Tor as plugin.
4) yes Tor client works great. Tor relay works on 1.8.1 only, relay won't work on 1.9.2 or 1.10.0

[Lantis]

I suspect that the reason is exactly as it says.
“Too many symlink levels”

So you’ve installed Tor as a plugin. This gets symlinked from plugin_root.
You also have an overlay which is also a symlink I believe.

I’m not saying this is acceptable behaviour, but I think it is explainable.
I’d like to hear from someone running it as a default plugin to see if it works fine

[ispyisail]

Just tried TOR server on my C7 not as a plug in and it also fails

[Lantis]

With the same error?

[Lantis]

I believe i've chased this through to cause and effect. Just running it by Eric to get his view on the potential solutions

[ysy]

Wow! Thanks a lot! Cheers