Hello,
since updating my nodes to Tor 0.2.8.8, the "connections" page of Arm is not showing connections anymore for one exit node running on Gentoo Linux. On a Debian based exit node and on Gentoo based non-exit nodes things work as expected. The affected exit seems to work fine and bandwidth graphs look OK, only the connection list is unexpectedly shown as empty.
I tried all listed "resolving utility" options, but that did not help. Any idea on how I might be able to debug/fix this?
-Ralph
I recently moved my relay, and I had the same problem. ARM suggested that I add DisableDebuggerAttachment 0 to my torrc. That fixed it. I hope it wasn't a bad idea.
Bryce
-------- Original Message -------- On Sep 25, 2016, 5:57 AM, Ralph Seichter wrote:
Hello,
since updating my nodes to Tor 0.2.8.8, the "connections" page of Arm is not showing connections anymore for one exit node running on Gentoo Linux. On a Debian based exit node and on Gentoo based non-exit nodes things work as expected. The affected exit seems to work fine and bandwidth graphs look OK, only the connection list is unexpectedly shown as empty.
I tried all listed "resolving utility" options, but that did not help. Any idea on how I might be able to debug/fix this?
-Ralph _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 25.09.16 17:40, Bryce Miller wrote:
ARM suggested that I add DisableDebuggerAttachment 0 to my torrc.
Thanks Bryce, but this configuration option was already present since before the latest update, for all my nodes. I still cannot figure out what makes this particular node behave differently from the others.
-Ralph
Hi Ralph, arm simply shells out to netstat, lsof, and other commands to get connection information. You can run these commands yourself to troubleshoot why they don't work...
https://gitweb.torproject.org/nyx.git/tree/src/util/connections.py?h=release
Also, if you log the ARM_DEBUG events arm should tell you what it's running along with a little information.
Cheers! -Damian (arm's author)
On Sun, Sep 25, 2016 at 2:57 AM, Ralph Seichter tor-relays-ml@horus-it.de wrote:
Hello,
since updating my nodes to Tor 0.2.8.8, the "connections" page of Arm is not showing connections anymore for one exit node running on Gentoo Linux. On a Debian based exit node and on Gentoo based non-exit nodes things work as expected. The affected exit seems to work fine and bandwidth graphs look OK, only the connection list is unexpectedly shown as empty.
I tried all listed "resolving utility" options, but that did not help. Any idea on how I might be able to debug/fix this?
-Ralph _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 25.09.16 19:09, Damian Johnson wrote:
arm simply shells out to netstat, lsof, and other commands to get connection information. You can run these commands yourself to troubleshoot why they don't work...
It looks like the commands run in the background to determine open connections do not return results when run as the 'tor' user, but only on this particular node.
For example, "lsof -wnPi" (as logged in ~/.arm/log) returns no results when manually run as 'tor'. Specifically, the "i" option causes the result set to be empty. Running "lsof -wnPi" as 'root' returns the expected results.
Seems like a permission problem, but how to fix it? I verified that /proc/{tor-process-id}/fdinfo and all files therein are readable by the 'tor' user.
-Ralph
tor-relays@lists.torproject.org
-
Bryce Miller -
Damian Johnson -
Ralph Seichter