On 15 Aug 2017, at 05:26, Dirk tor-relay.dirk@o.banes.ch wrote:
Hello Roger,
your lucky - I got an example now: DigiGesTor2e1 Mon Aug 14 21:20:26 CEST 2017 => according to atlas offline.
Prozess is running PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+ BEFEHL
38629 debian-+ 20 0 502848 271376 52056 S 15.0 7.0 389:15.45 /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc1 --hush
Notices log shows: ....... Aug 14 21:01:58.000 [warn] assign_to_cpuworker failed. Ignoring. ......
These are not very useful, please provide distinct log messages next time.
Missing here [1], Available here [2]
Next time it happens, check the relay flags here: https://consensus-health.torproject.org/consensus-health.html
It will tell you how many authorities could connect to your relay in the past hour or so.
...
[1] https://collector.torproject.org/recent/relay-descriptors/consensuses/2017-0... [2] https://collector.torproject.org/recent/relay-descriptors/votes/2017-08-14-1...
The problem here is. Since the process is running neiter my scripts nor systemd will try to restart it.
This is probably a network failure on your relay or provider, or your relay is running out of some resource (like file descriptors).
T -- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------