Hi Davin. Unfortunately I can't tell you offhand what's up, but as Nyx's author I can tell you what that message means.
Nyx constantly communicates with the tor process. At the very minimum tor emits a bandwidth event each second, which means that Nyx should constantly hear from the tor process.
Nyx reports that message when it hasn't heard from tor in ten seconds. This means that the tor process is struggling, usually due to resource contention (for instance pegged CPU usage). You'll need to use tor's other logs and check 'top' when tor becomes unresponsive to learn more.
Cheers! -Damian
On Mon, Jun 8, 2020 at 12:47 PM Davin Mertens davinmertens@gmail.com wrote:
I keep getting NYX_NOTICEs about "Relay unresponsive". They happen every few hours, and last for minutes or sometimes a couple of hours before I get a "relay resumed" message.
But, I don't see anything in the actual Tor logs to indicate that anything is wrong. Does anyone know how best to troubleshoot this? I think it's impacting my consensus weight and making it drop, and is keeping me from getting the Guard flag.
This is the relay: https://metrics.torproject.org/rs.html#details/94626BD21119568EB301D1E7677B2...
Thanks for any tips! _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays