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
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 sho
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
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
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
grap
