My question evolves around tor arm the controller used with tor. I hope I'm posting in the correct area as I'm not at all sure where the fault lies; either with Ubuntu or arm. If I'm in the wrong place apologies!
My relay has been in operation for little better than two weeks. I am new to tor relay. I've experienced the same problem several times. For the most part the relay takes care of itself with me checking it's operation periodically throughout the day. Until it happens.. I lose all Administrative functions with arm. Meanwhile, the relay seemingly continues to function as normal. The only solution I've found so far is to stop tor, and arm and do a hard restart. It's then good again for who knows how long until it happens again.
I've intentionally left out computer specifics as the computer itself is not the issue. It's software related either arm or Ubuntu OR both. How to sort it out, I am at a loss.
Thanks for any help everyone :-)
Upon further exploration!
Oct 29 04:31:51.000 [notice] Circuit handshake stats since last time: 90/90 TAP, 1/1 NTor. Oct 29 04:31:51.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 1820 v4 connections; and received 746 v1 connections, 315 v2 connections, 380 v3 connections, and 5426 v4 connections. Oct 29 07:35:02.000 [notice] *Received reload signal (hup)*. Reloading config and resetting internal state. Oct 29 07:35:02.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Oct 29 07:35:02.000 [notice] Read configuration file "/etc/tor/torrc".
So why am I getting a "reload signal??"