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 SS
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.
On May 30, 2016 4:32 PM, "Green Dream" wrote:
Hi. Thanks for running a relay. These notice messages are from the
monitoring tool Arm, and should
Hi. Thanks for running a relay. These notice messages are from the
monitoring tool Arm, and should not affect the Tor process.
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
Hi, i have installed a non-exit relay in my home server and for many
days i have had this warnings:
20:42:57 [ARM_NOTICE] Unable to prepopulate bandwidth information
(unable to read the state file)
20:42:56 [ARM_WARN] Unable to read tor's log file: /var/log/tor/log [1
duplicate hidden]
20:42:56
