<html><head></head><body>Ok thanks both of you, i'll look into it. The control port is blocked from outside. I'm using openWRT router as firewall which it is the best i can do for the moment, but it gives decent control features so far. The relay itself is running on an encrypted LVM debian virtual machine and it has SSH key only login, its pretty secure. Hist system is also debian, both frecuently updated, and monitored for tootkits with rkhunter and brute force attacks mitogation with fail2ban, any other suggestion is welcome.<br>
<br>
Best regards,<br><br><div class="gmail_quote">El 30 de mayo de 2016 6:44:23 PM GMT-03:00, Tristan <supersluether@gmail.com> escribió:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<p dir="ltr">Not sure where I found this, but I remember reading that Tor changed how it stored bandwidth information. Arm wasn't updated yet, so it throws an error.</p>
<div class="gmail_quote">On May 30, 2016 4:32 PM, "Green Dream" <<a href="mailto:greendream848@gmail.com">greendream848@gmail.com</a>> wrote:<br type="attribution" /><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi. Thanks for running a relay. These notice messages are from the monitoring tool Arm, and should not affect the Tor process. </div><div><br /></div><div>If you don't care about Arm and Tor seems to be working okay otherwise, you could safely ignore these messages. In case you want to look into them further, I'll share some thoughts below. It looks like you're running on a Unix or Linux system, I'll assume Debian or Ubuntu for the moment.</div><div class="quoted-text"><div><br /></div><div>> 20:42:57 [ARM_NOTICE] Unable to prepopulate bandwidth information</div><div>> (unable to read the state file)</div><div><br /></div><div><br /></div></div><div><div>This is
normal in my experience. Arm is trying to read your node's bandwidth history to populate the graphs with data collected before you started Arm. I don't know why it fails, but you could squelch it by adding the following config line to ~/.arm/armrc:</div><div><br /></div><div> features.graph.bw.prepopulate false</div></div><div class="quoted-text"><div><br /></div><div><br /></div><div>> 20:42:56 [ARM_WARN] Unable to read tor's log file: </div><div>> /var/log/tor/log [1duplicate hidden]</div><div><br /></div><div><br /></div></div><div>It looks like Arm doesn't have permission to read /var/log/tor/log. I normally start Arm with something like this, so it has the same permissions as the Tor daemon:</div><div><br /></div><div> sudo -u debian-tor arm</div><div class="quoted-text"><div><br /></div><div><br /></div><div>> 20:42:56 [ARM_NOTICE] Tor is preventing system utilities like netstat<br /></div><div>> and lsof from working. This means that arm
can't provide you with</div><div>> connection information. You can change this by adding </div><div>> 'DisableDebuggerAttachment 0' to your torrc and restarting tor. For </div><div>> more information see... <a href="https://trac.torproject.org/3313" rel="noreferrer" target="_blank">https://trac.torproject.org/3313</a></div><div><br /></div><div><br /></div></div><div><div>You need to add the following to /etc/tor/torrc if you want to utilize all the features of Arm:</div><div><br /></div><div> DisableDebuggerAttachment 0</div><div><br /></div><div>It's disabled by default for security (with a value of '1'), so think carefully before doing this. It "reduces security by enabling debugger attachment to the Tor process. This can be used by an adversary to extract keys." (Quoting from <a href="https://trac.torproject.org/projects/tor/ticket/13880" target="_blank">https://trac.torproject.org/projects/tor/ticket/13880</a>). If you do enable
the deubgger attachment for Arm, make sure your control port is locked down (not reachable from the Internet or from other hosts you don't control, etc.)</div></div><div><br /></div><div><br /></div></div>
<br />_______________________________________________<br />
tor-relays mailing list<br />
<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.org</a><br />
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br />
<br /></blockquote></div>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />tor-relays mailing list<br />tor-relays@lists.torproject.org<br /><a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br /></pre></blockquote></div><br>
Santiago Roland.-<br>
------------------------------------------------------------------<br>
Jabber: santiago@jabber.undernet.uy<br>
Diaspora*: <a href="http://bit.ly/diasr">http://bit.ly/diasr</a><br>
GNU Social: <a href="http://bit.ly/gnusr">http://bit.ly/gnusr</a><br>
openPGP ID: 7BE512C5<br>
openPGP key: <a href="http://bit.ly/pgpsr">http://bit.ly/pgpsr</a><br>
CX1DR - Grid Locator: GF25bf<br>
------------------------------------------------------------------</body></html>