<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal"><p dir="auto">Hi Damian,</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">On Sat, Feb 3, 2018 at 2:10 PM, Stijn Jonker <sjcjonker@sjc.nl> wrote:</p>
<blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><p dir="auto">Hi All,<br>
</p>
</blockquote></blockquote><p dir="auto"><SNIP></p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><p dir="auto">So I'm running two relays, one is running on CentOS7, the other Debian<br>
Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is missing<br>
the CPU, Exit policy etc info. It's not tor version specific, as I recently<br>
upgraded the tor software on the nodes regularly.</p>
</blockquote></blockquote><p dir="auto">On 3 Feb 2018, at 23:58, Damian Johnson wrote:</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">Hi Stijn, my first thought is that this might be tor's<br>
DisableDebuggerAttachment feature. It causes proc contents to only be<br>
readable by root. Usually this breaks Nyx's connection resolution but<br>
it can prevent resource usage lookups too. Does setting<br>
'DisableDebuggerAttachment 0' in your torrc cause the data to appear?</p>
</blockquote><p dir="auto">For both nodes I have DisableDebuggerAttachment set to 0</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">If not then the next step is to take a peek at the debug logs. If you<br>
send me the logs on both platforms with any data you feel is sensitive<br>
redacted I'd be happy to take a peek. I only need the first five<br>
seconds or so of logs (just need to see the first resource resolution<br>
attempt).</p>
</blockquote><p dir="auto">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.</p>
<p dir="auto">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:</p>
<p dir="auto">cpu: 88.7% tor, 54.8% nyx mem: 866 MB (21.9%) pid: 1344 uptime: 19:02:04<br>
fingerprint: 366BC592BC0154C0CD1D35C0E77D8F2C7F0B843E<br>
exit policy: reject *:*</p>
<p dir="auto">So it seems to be something python2/python3 related. I'm not sure why I used python3 to be honest.</p>
<p dir="auto">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).</p>
<p dir="auto">Thanks!<br>
Stijn</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">Cheers! -Damian<br>
</p>
</blockquote></div>
</div>
</body>
</html>