Re: [tor-dev] Consensus network status fetch

2021-05-16 Thread sysmanager7
crotab -l root returns 0 crontab -l user returns 0 I am running a tor relay on Ubuntu 20.4 on a digital Ocean Droplet. NTX is used to monitor 00:00:05 [NOTICE] Read configuration file "/etc/tor/torrc". x 00:00:05 [NOTICE] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".

Re: [tor-dev] Consensus network status fetch

2021-05-16 Thread Roger Dingledine
On Sun, May 16, 2021 at 06:05:59PM +, sysmanager7 wrote: > crotab -l root returns 0 > crontab -l user returns 0 Modern cron jobs don't just live in the crontab. See also your /etc/cron* directories, which is where various packages might put cron things. For example, in my case I have an /etc/

Re: [tor-dev] Consensus network status fetch

2021-05-14 Thread Roger Dingledine
On Fri, May 14, 2021 at 06:02:50PM +, sysmanager7 wrote: > Why does a network status fetch cause a signal hup and my system to reset? > > x 00:00:07 [NOTICE] Received reload signal (hup). Reloading config and > resetting internal state. It probably isn't the networkstatus fetch that did it.