> 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.
As Damian Johnson has said, it is hard to guess the cause without more
clues. But keep in mind that 2MB/s with 7k c
Hey Torix,
This is something that seems to come up with offline generated keys, I've
no idea what's happening here though.
I suppose keeping an original key for a bridge doesn't matter in the
slightest, because the bridges don't generate any consensus. I'm presuming
this is one of your bridges th
Dear LIst,
My bridge, tor version 0.4.2.7 stopped this morning with a bunch of lines like
this:
"It looks like I should try to generate and sign a new medium-term signing key,
because
the one I have is going to expire soon. To do that, I'm going to have to try to
load the permanent master ident
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.
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 troubles
