Re: [tor-relays] [Relay] Hibernation Reset

Subject: Re: [tor-relays] [Relay] Hibernation Reset

Date: Wed, 22 Jul 2015 01:09:34 +1000

Delivery-date: Tue, 21 Jul 2015 11:09:54 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:message-id :references:to; bh=PfP0WA71bgw/c5MrbMBPHotumG08asMV8w8pomlHyrM=; b=TsqP3F+BfF/CaoRTvKEIhezn70rppAlsRORL10uybHyZxJzEr2J+20NxdZmt9qhdkz PWvPb59qw1oFPnwsf5NIDVHhxJ0TzGENcZE34C2RW1Q4LPyx0j6/Mv7fgzgKQ/QUyRoH TIdIUZINbmo2nvRF/pEuwzfvyWGQnNN2IZ68uZ1nM2Eg/AaL2RNb77CG1nyksErlGqhk Z6rP06RU1RU0rCuLp2v0y2mvMiMlcPHubh4SVNLb0ndFxnXkxWt7s/tIN5TBWKoAuOYy 21DU7h8+yYmeo35kllzdEWe6cMNFs0ONoRTEPNfu014h7bBMB99OJzlgjVJ8Nx0+lsFE 5chA==

In-reply-to: <55AD2BEA.7090208@xxxxxxxxxxxxxxxxxx>

List-archive: <http://lists.torproject.org/pipermail/tor-relays/>

List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>

List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>

List-post: <mailto:tor-relays@lists.torproject.org>

List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>

List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>

References: <55AD2BEA.7090208@xxxxxxxxxxxxxxxxxx>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

On 21 Jul 2015, at 03:12 , Tor Operator <tor@xxxxxxxxxxxxxxxxxx> wrote:

Hi gents,

I rencetly had one of my relay fall into hibernation. It seems that simply restarting the service doesn't change the hibernation status since Tor is still thinking that the BW limits have been overrun. Is the proper method to reset the status of the node is simply to delete the "state" file in "/var/lib/tor/". For now, I just set back to 0 the "AccountingBytesReadInInterval" and "AccountingBytesWrittenInInterval" counters and the node was able to wake up but that doesn't seem like a very elegant way to do it.

Why not edit or remove the accounting limits in the torrc?

We might need a little more context: why are the accounting limits set lower than you want?

What exactly are you trying to achieve?

Tim

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
pgp ABFED1AC
https://gist.github.com/teor2345/d033b8ce0a99adbc89c5

teor at blah dot im
OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays