Opened 6 years ago

Last modified 22 months ago

#9105 new defect

make heartbeat messages describe hibernation consistently

Reported by: hsn Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.4.13-alpha
Severity: Normal Keywords: tor-relay accounting heartbeat easy
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If user have configured hibernation it looks like this:

03:02:02.000 [notice] Bandwidth soft limit reached; commencing hibernation. No new connections will be accepted
06:19:04.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 1 circuits open. I've sent 1.43 GB and received 1.45 GB. We are currently hibernating.
08:00:00.000 [notice] Configured hibernation.  This interval began at 2013-06-20 08:00:00; the scheduled wake-up time was 2013-06-20 08:00:00; we expect to exhaust our quota for this interval around 2013-06-21 08:00:00; the next interval begins at 2013-06-21 08:00:00 (all times local)
08:00:00.000 [notice] Hibernation period ended. Resuming normal activity.
12:19:04.000 [notice] Heartbeat: Tor's uptime is 4:19 hours, with 45 circuits open. I've sent 1.58 GB and received 1.60 GB.

This is inconsistent. Upon hibernating Tor uptime is reset, but transferred GB are not. This does not make these messages useful.

It would be best to reset bw info on uptime reset after hibernation ended or report totals and current periods.

For example Running for XX hours (not reset on hibernation), total sent/received. Uptime is YY hours, sent/received data since last start.

If user have configured hibernation, i presume that he wants to know data sent/received in last hibernation interval.

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by nickm

Keywords: tor-relay added
Milestone: Tor: 0.2.5.x-final
Priority: normalminor

comment:2 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:3 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:4 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:5 Changed 22 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 22 months ago by nickm

Keywords: accounting heartbeat easy added
Severity: Normal
Summary: make heartbeat messages consistentmake heartbeat messages describe hibernation consistently

Upon hibernating Tor uptime is reset, but transferred GB are not.

So, this is in one sense correct behavior. Hibernating makes the relay go down (as far as anybody else is concerned), which ought to reset its uptime.

That said, it would be good to log both the amount of time that the tor process has been running, and the uptime for the current session.

Note: See TracTickets for help on using tickets.