Last 'log' entry was from a few days ago when I started it. Just shows
bootstrapping 0-100% without errors.
'notices.log' entries happen fairly regularly. Mostly heartbeat uptime
notifications and lifetime sent/received. Also bugging me to add my
ContactInfo. No errors relating to tor-arm's odd be
What does the
cat /var/log/tor/log
says?
On Tuesday, June 17, 2014 6:56 PM, Adam Griffin wrote:
Running top in a separate SSH session shows ~50% load average. I imagine
spikes would cause the CLI interruptions and maybe relay unresponsive/resumed
notices. Did you have the same blank upt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Yes, especially when hitting Enter after "sudo -u debian-tor arm"
Then it took a few seconds and the relay resumed.
It never seemed to have these problems when running on it's own, so I think
this is just due to the limited resources of the pi
Running top in a separate SSH session shows ~50% load average. I imagine
spikes would cause the CLI interruptions and maybe relay
unresponsive/resumed notices. Did you have the same blank uptime issue?
On Tue, Jun 17, 2014 at 2:08 PM, Elrippo wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Had the same issues on my pi when running over ssh.
It simply is the fact, that your pi is running almost on max load. Type top in
your console, and watch the pi working :)
On 17. Juni 2014 19:28:23 MESZ, Adam Griffin wrote:
>Hi,
>
>Just started a
Hi,
Just started a new tor relay on my raspberry pi yesterday and I'm
monitoring with tor-arm over ssh. I'm currently listed on
atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid'
with > 17hrs uptime.
However, tor-arm is showing a blank for uptime and about once a minute, the
