-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2013 02:18 PM, Stephan wrote:
> On 11.09.2013 13:33, Random Tor Node Operator wrote:
>> Could you post the corresponding line(s) in your monitrc?
>
> Of course. I use the default of "set daemon 120", so tor is checked
> once every 120 seconds
On 11.09.2013 13:33, Random Tor Node Operator wrote:
Could you post the corresponding line(s) in your monitrc?
Of course. I use the default of "set daemon 120", so tor is checked once
every 120 seconds ('one cycle'). The tor specific part of the
configuration is this:
if failed host 127.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2013 12:34 PM, Stephan wrote:
> I'm just taking a wild guess here, because I had similar symptoms:
> that log message doesn't seem to be a crash but a regular shutdown.
> In my case I use 'monit' to monitor my server and the running
> services
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2013 12:37 PM, Roger Dingledine wrote:
>> In my case I use 'monit' to monitor my server and the running
>> services - including tor. Once in a while the automated TCP check
>> on either the OR-Port or the DIR-Port failed which resulted in
>>
On 11.09.2013 10:05, Random Tor Node Operator wrote:
Sep 10 08:59:40.000 [notice] Interrupt: we have stopped accepting new
connections, and will shut down in 30 seconds. Interrupt again to exit
now.
I'm just taking a wild guess here, because I had similar symptoms: that
log message doesn't see
On Wed, Sep 11, 2013 at 12:34:12PM +0200, Stephan wrote:
> On 11.09.2013 10:05, Random Tor Node Operator wrote:
> >Sep 10 08:59:40.000 [notice] Interrupt: we have stopped accepting new
> >connections, and will shut down in 30 seconds. Interrupt again to exit
> >now.
>
> I'm just taking a wild gues
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody,
since this botnet started flooding Tor, my Tor relay Bazinga
($196832C61F30E9D6D179393C9AED4E47FD29796B) has been experiencing some
issues.
Previously, it was relaying 100 Mbit/s for a few months without problem.
When the botnet came
