Hello all, I recently set up the relay zelltor. I just got a notification that it went down about 10 hours ago. From what I can tell it looks like it decided to hibernate and that it will be hibernating for the rest of the month. I think I may have configured something wrong because this was rather unexpected. I want it to hibernate at a certain point, but I do not think its reached that threshold yet. Arm tells me: Accounting (hard) 15 MB / 250 GB 598 KB / 250 GB Time to reset: 31:02:20:23 I have the following configured in torrc: AccountingMax: 250 GB AccountingStart: month 3 15:00 Tor's log files: [notice] Configured hibernation. This interval began 2014-10-03 15:00:00; the scheduled wake-up time is 2014-10-03 15:00:00; we expect to exhaust our quota for this interval around 2014-11-03 15:00:00 (all times local) [notice] Commencing hibernation. We will wake up at 2014-10-03 15:00:00 local time. [notice] Heartbeat: Tor's uptime is 3 days 12:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.08 GB. We are currently hibernating. [notice] TLS write overhead: 6% [notice] Circuit handshake stats since last time: 2039/2039 TAP, 753/753 NTor. [warn] eventdns: Address mismatch on received DNS packet. Apparent source was 216.69.185.43:53 [notice] Heartbeat: Tor's uptime is 3 days 18:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.08 GB. We are currently hibernating. [notice] TLS write overhead: 6% [notice] New control connection opened. Note: I stripped the timestamps out because I am viewing these on a different computer and had to retype them. My ISP caps me at 500 GB up+down data per month, which is why I've capped it at 250 GB. I was planning to adjust that down a little bit as needed when my next month's bill came in and I got to see how much overhead Tor produces above the 500 GB cpa. Clearly I've come nowhere close to that though, so I don't think my node should be hibernating yet... Any ideas? Thank you, Derric Atzrott
On 2014-10-03 07:51, Derric Atzrott wrote:
Hello all,
I recently set up the relay zelltor. I just got a notification that it went down about 10 hours ago. From what I can tell it looks like it decided to hibernate and that it will be hibernating for the rest of the month. I think I may have configured something wrong because this was rather unexpected. I want it to hibernate at a certain point, but I do not think its reached that threshold yet.
Arm tells me: Accounting (hard) 15 MB / 250 GB 598 KB / 250 GB Time to reset: 31:02:20:23
I have the following configured in torrc: AccountingMax: 250 GB AccountingStart: month 3 15:00
Tor's log files: [notice] Configured hibernation. This interval began 2014-10-03 15:00:00; the scheduled wake-up time is 2014-10-03 15:00:00; we expect to exhaust our quota for this interval around 2014-11-03 15:00:00 (all times local) [notice] Commencing hibernation. We will wake up at 2014-10-03 15:00:00 local time. [notice] Heartbeat: Tor's uptime is 3 days 12:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.08 GB. We are currently hibernating. [notice] TLS write overhead: 6% [notice] Circuit handshake stats since last time: 2039/2039 TAP, 753/753 NTor. [warn] eventdns: Address mismatch on received DNS packet. Apparent source was 216.69.185.43:53 [notice] Heartbeat: Tor's uptime is 3 days 18:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.08 GB. We are currently hibernating. [notice] TLS write overhead: 6% [notice] New control connection opened.
Note: I stripped the timestamps out because I am viewing these on a different computer and had to retype them.
My ISP caps me at 500 GB up+down data per month, which is why I've capped it at 250 GB. I was planning to adjust that down a little bit as needed when my next month's bill came in and I got to see how much overhead Tor produces above the 500 GB cpa. Clearly I've come nowhere close to that though, so I don't think my node should be hibernating yet...
Any ideas?
Thank you, Derric Atzrott
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [1]
I don't understand why it started hibernation just because it began a new interval, but I think it will start back up at a random time.
From the manual for AccountingMax: "To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up."
-- Gabriel Links: ------ [1] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Fri, Oct 03, 2014 at 08:51:46AM -0400, Derric Atzrott wrote:
[notice] Configured hibernation. This interval began 2014-10-03 15:00:00; the scheduled wake-up time is 2014-10-03 15:00:00; we expect to exhaust our quota for this interval around 2014-11-03 15:00:00 (all times local)
It looks like Tor thinks it is in the interval that started at 2014-10-03 15:00:00. But then:
[notice] Commencing hibernation. We will wake up at 2014-10-03 15:00:00 local time.
It looks like Tor thinks it is not yet 2014-10-03 15:00:00.
Note: I stripped the timestamps out because I am viewing these on a different computer and had to retype them.
I think the timestamps here might be really useful, to sort out what time Tor actually said these things. --Roger
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It looks like Tor thinks it is not yet 2014-10-03 15:00:00.
Note: I stripped the timestamps out because I am viewing these on a different computer and had to retype them.
I think the timestamps here might be really useful, to sort out what time Tor actually said these things.
Sure, here is the same section of the log file, but with timestamps: Oct 03 04:17:02.000 [notice] Configured hibernation. This interval began at 2014-10-03 15:00:00; the scheduled wake-up time is 2014-10-03 15:00:00; we expect to exhaust our quota for this interval around 2014-11-03 15:00:00; the next interval begins at 2014-11-03 15:00:00 (all times local) Oct 03 04:17:02.000 [notice] Commencing hibernation. We will wake up at 2014-10-03 15:00:00 local time. Oct 03 04:17:02.000 [notice] Going dormant. Blowing away remaining connections. Oct 03 07:12:29.000 [notice] Heartbeat: Tor's uptime is 3 days 12:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.08 GB. We are currently hibernating. Oct 03 07:12:29.000 [notice] TLS write overhead: 6% Oct 03 07:12:29.000 [notice] Circuit handshake stats since last time: 2039/2039 TAP, 753/753 NTor. Oct 03 09:46:01.000 [warn] eventdns: Address mismatch on received DNS packet. Apparent source was 216.69.185.43:53 Oct 03 13:12:29.000 [notice] Heartbeat: Tor's uptime is 3 days 18:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.09 GB. We are currently hibernating. Oct 03 13:12:29.000 [notice] TLS write overhead: 6% Oct 03 13:12:29.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor. Oct 03 14:25:21.000 [notice] New control connection opened. Interestingly about a half hour after I sent that email, everything started to work again. (Note: there is nothing in between these two sections of the log file.) Oct 03 15:00:00.000 [notice] Hibernation period ended. Resuming normal activity. Oct 03 15:00:00.000 [notice] Opening Directory listener on 0.0.0.0:9030 Oct 03 15:00:00.000 [notice] Opening OR listener on 0.0.0.0:9001 Oct 03 15:00:47.000 [notice] Not advertising DirPort (Reason: AccountingMax enabled) Oct 03 17:48:12.000 [warn] Unexpected sendme cell from client. Closing circ (window 1000). Oct 03 19:12:28.000 [notice] Caching new entry debian-tor for debian-tor Oct 03 19:12:29.000 [notice] Heartbeat: Tor's uptime is 4:12 hours, with 20 circuits open. I've sent 6.19 GB and received 6.21 GB. Oct 03 19:12:29.000 [notice] Heartbeat: Accounting enabled. Sent: 107.37 MB / 250.00 GB, Received: 128.01 MB / 250.00 GB. The current accounting interval ends on 2014-11-03 15:00:00, in 30 days 20:47 hours. Oct 03 19:12:29.000 [notice] Average packaged cell fullness: 84.664% Oct 03 19:12:29.000 [notice] TLS write overhead: 6% Everything seems to be working fine now. Any idea what might have happened though? Thank you, Derric Atzrott -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) iD8DBQFUMrBBRHoDdZBwKDgRAho2AJ9psSg/1Dlto28C0pPAVenHTXOVFgCfQCNT o5kWFxFckR3JQ0fm+g0cXac= =Ji3B -----END PGP SIGNATURE-----
On Fri, Oct 03, 2014 at 08:51:46AM -0400, Derric Atzrott wrote:
Hello all,
I recently set up the relay zelltor. I just got a notification that it went down about 10 hours ago. From what I can tell it looks like it decided to hibernate and that it will be hibernating for the rest of the month. I think I may have configured something wrong because this was rather unexpected. I want it to hibernate at a certain point, but I do not think its reached that threshold yet.
Arm tells me: Accounting (hard) 15 MB / 250 GB 598 KB / 250 GB Time to reset: 31:02:20:23
I have the following configured in torrc: AccountingMax: 250 GB AccountingStart: month 3 15:00 AFAIK this ^^^^ means ^^^^^^^^^^^
Tor's log files: [notice] Configured hibernation. This interval began 2014-10-03 15:00:00; the scheduled wake-up time is 2014-10-03 15:00:00; we expect to exhaust ^^^^^^^^ Tor is running as you set it to? our quota for this interval around 2014-11-03 15:00:00 (all times local) [notice] Commencing hibernation. We will wake up at 2014-10-03 15:00:00 local time. [notice] Heartbeat: Tor's uptime is 3 days 12:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.08 GB. We are currently hibernating. [notice] TLS write overhead: 6% [notice] Circuit handshake stats since last time: 2039/2039 TAP, 753/753 NTor. [warn] eventdns: Address mismatch on received DNS packet. Apparent source was 216.69.185.43:53 [notice] Heartbeat: Tor's uptime is 3 days 18:00 hours, with 0 circuits open. I've sent 6.08 GB and received 6.08 GB. We are currently hibernating. [notice] TLS write overhead: 6% [notice] New control connection opened.
Note: I stripped the timestamps out because I am viewing these on a different computer and had to retype them.
My ISP caps me at 500 GB up+down data per month, which is why I've capped it at 250 GB. I was planning to adjust that down a little bit as needed when my next month's bill came in and I got to see how much overhead Tor produces above the 500 GB cpa. Clearly I've come nowhere close to that though, so I don't think my node should be hibernating yet...
Any ideas?
Thank you, Derric Atzrott
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (4)
-
014 -
Derric Atzrott -
L. Blissett -
Roger Dingledine