Hi All,
I initially went to the nyx website to find the right forum to ask questions. I understood this is the one :-), if not apologies.
So I'm running two relays, one is running on CentOS7, the other Debian Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is missing the CPU, Exit policy etc info. It's not tor version specific, as I recently upgraded the tor software on the nodes regularly.
So on the CentOS node I see this on the top at the right; cpu: 61.3% tor, 5.0% nyx mem: 371 MB (12.4%) pid: 1279 uptime: 02:59:09 fingerprint: 328E54981C6DDD7D89B89E418724A4A7881E3192 exit policy: reject *:*
On the Debian node it's simply not printing any of these three lines. I can't find in the (debug) logging whether an utility or library is missing. It's nothing major, but annoying. Especially with the new alpha releases it's nice to keep an eye out on mem/cpu.
Does anyone have an idea what the trick is to get it to work on debian?
-- CentOS info: [user@tornode ~]$ tor --version Tor version 0.3.3.1-alpha (git-de8bc9eed6eaadfc).
[user@tornode ~]$ nyx --version nyx version 2.0.4 (released November 5, 2017)
[user@tornode ~]$ uname -a Linux tornode.sjc.nl 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
-- Debian info: [maint@tornode2 ~]$ tor --version Tor version 0.3.3.1-alpha-dev (git-9e48338a12fd1fef+0f23e7e96).
[user@tornode2 ~]$ nyx --version nyx version 2.0.4 (released November 5, 2017)
[user@tornode2 ~]$ uname -a Linux tornode2 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux
[user@tornode2 ~]$ lsb_release -c Codename: stretch
Thx, Stijn
Hi Stijn, my first thought is that this might be tor's DisableDebuggerAttachment feature. It causes proc contents to only be readable by root. Usually this breaks Nyx's connection resolution but it can prevent resource usage lookups too. Does setting 'DisableDebuggerAttachment 0' in your torrc cause the data to appear?
If not then the next step is to take a peek at the debug logs. If you send me the logs on both platforms with any data you feel is sensitive redacted I'd be happy to take a peek. I only need the first five seconds or so of logs (just need to see the first resource resolution attempt).
Cheers! -Damian
On Sat, Feb 3, 2018 at 2:10 PM, Stijn Jonker sjcjonker@sjc.nl wrote:
Hi All,
I initially went to the nyx website to find the right forum to ask questions. I understood this is the one :-), if not apologies.
So I'm running two relays, one is running on CentOS7, the other Debian Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is missing the CPU, Exit policy etc info. It's not tor version specific, as I recently upgraded the tor software on the nodes regularly.
So on the CentOS node I see this on the top at the right; cpu: 61.3% tor, 5.0% nyx mem: 371 MB (12.4%) pid: 1279 uptime: 02:59:09 fingerprint: 328E54981C6DDD7D89B89E418724A4A7881E3192 exit policy: reject *:*
On the Debian node it's simply not printing any of these three lines. I can't find in the (debug) logging whether an utility or library is missing. It's nothing major, but annoying. Especially with the new alpha releases it's nice to keep an eye out on mem/cpu.
Does anyone have an idea what the trick is to get it to work on debian?
-- CentOS info: [user@tornode ~]$ tor --version Tor version 0.3.3.1-alpha (git-de8bc9eed6eaadfc).
[user@tornode ~]$ nyx --version nyx version 2.0.4 (released November 5, 2017)
[user@tornode ~]$ uname -a Linux tornode.sjc.nl 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
-- Debian info: [maint@tornode2 ~]$ tor --version Tor version 0.3.3.1-alpha-dev (git-9e48338a12fd1fef+0f23e7e96).
[user@tornode2 ~]$ nyx --version nyx version 2.0.4 (released November 5, 2017)
[user@tornode2 ~]$ uname -a Linux tornode2 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux
[user@tornode2 ~]$ lsb_release -c Codename: stretch
Thx, Stijn
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi Damian,
On Sat, Feb 3, 2018 at 2:10 PM, Stijn Jonker sjcjonker@sjc.nl wrote:
Hi All,
<SNIP>
So I'm running two relays, one is running on CentOS7, the other Debian Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is missing the CPU, Exit policy etc info. It's not tor version specific, as I recently upgraded the tor software on the nodes regularly.
On 3 Feb 2018, at 23:58, Damian Johnson wrote:
Hi Stijn, my first thought is that this might be tor's DisableDebuggerAttachment feature. It causes proc contents to only be readable by root. Usually this breaks Nyx's connection resolution but it can prevent resource usage lookups too. Does setting 'DisableDebuggerAttachment 0' in your torrc cause the data to appear?
For both nodes I have DisableDebuggerAttachment set to 0
If not then the next step is to take a peek at the debug logs. If you send me the logs on both platforms with any data you feel is sensitive redacted I'd be happy to take a peek. I only need the first five seconds or so of logs (just need to see the first resource resolution attempt).
There is a lot to remove in those logs :-), but one thing catched my eye whilst comparing both side-2-side (I only looked at the debian one so far). The debian one was running nyx via python3, whereby the centos one ran it with python2.
I did an pip3 uninstall nyx and then a pip2 install nyx on the debian server. Then I had the output on the top right:
cpu: 88.7% tor, 54.8% nyx mem: 866 MB (21.9%) pid: 1344 uptime: 19:02:04 fingerprint: 366BC592BC0154C0CD1D35C0E77D8F2C7F0B843E exit policy: reject *:*
So it seems to be something python2/python3 related. I'm not sure why I used python3 to be honest.
P.S. If you want the logs, do you mind if I send them directly? Then I don't have to remove all the other tor node details, which is quite a lot that flies by (so this doesn't end up in the public archives - even-though it's public info anyway).
Thanks! Stijn
Cheers! -Damian
So it seems to be something python2/python3 related. I'm not sure why I used python3 to be honest.
Interesting. Can't say there's anything that comes straight to mind that would cause that. I'd expect python2 and python3 to behave the same on this front.
P.S. If you want the logs, do you mind if I send them directly? Then I don't have to remove all the other tor node details, which is quite a lot that flies by (so this doesn't end up in the public archives - even-though it's public info anyway).
Of course. I didn't mean to encourage you to send the logs to the list. :)
Considering your find above the most useful logs would be the working Debian python2 verses the broken Debian python3.
Hi Stijn,
So I'm running two relays, one is running on CentOS7, the other Debian Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is missing the CPU, Exit policy etc info. It's not tor version specific, as I recently upgraded the tor software on the nodes regularly.
So on the CentOS node I see this on the top at the right; cpu: 61.3% tor, 5.0% nyx mem: 371 MB (12.4%) pid: 1279 uptime: 02:59:09 fingerprint: 328E54981C6DDD7D89B89E418724A4A7881E3192 exit policy: reject *:*
On the Debian node it's simply not printing any of these three lines. I can't find in the (debug) logging whether an utility or library is missing. It's nothing major, but annoying. Especially with the new alpha releases it's nice to keep an eye out on mem/cpu.
I have a similar problem with nyx on FreeBSD 11.1. The CPU, mem, pid, uptime, fingerprint and exit policy is only visible when using a terminal width of 141-153 characters. You could try this.
~ Stian Fauskanger
Hi Stain,
On 4 Feb 2018, at 14:56, Stian Fauskanger wrote:
Hi Stijn,
So I'm running two relays, one is running on CentOS7, the other Debian Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is missing the CPU, Exit policy etc info. It's not tor version specific, as I recently upgraded the tor software on the nodes regularly.
So on the CentOS node I see this on the top at the right; cpu: 61.3% tor, 5.0% nyx mem: 371 MB (12.4%) pid: 1279 uptime: 02:59:09 fingerprint: 328E54981C6DDD7D89B89E418724A4A7881E3192 exit policy: reject *:*
On the Debian node it's simply not printing any of these three lines. I can't find in the (debug) logging whether an utility or library is missing. It's nothing major, but annoying. Especially with the new alpha releases it's nice to keep an eye out on mem/cpu.
I have a similar problem with nyx on FreeBSD 11.1. The CPU, mem, pid, uptime, fingerprint and exit policy is only visible when using a terminal width of 141-153 characters. You could try this.
I think I found the non-printing at all, python2 vs python3. But when I have a smaller terminal (actually most of the time I run then side by side in a 55 char width terminal, the lines are printed in one column (for me at least - now on both nodes :-)):
nyx - tornode.sjc.nl (Linux 3.10.0-6...) Tor 0.3.3.1-alpha (recommended) sjc01 - <<RMEOVED>>:443, Dir Port: 80, Control Port (cookie): 9051 cpu: 73.7% tor, 1.1% nyx mem: 691 MB (23.1%) pid: 1279 uptime: 19:09:43 fingerprint: 328E54981C6DDD7D89B89E418724A4A7881E3192 flags: Fast, Guard, Running, Stable, V2Dir, Valid
Stian Fauskanger
Thx, Stijn
tor-relays@lists.torproject.org
-
Damian Johnson -
Stian Fauskanger -
Stijn Jonker