Opened 4 years ago

Last modified 2 years ago

#15380 new defect

log messages are doubled and unclear

Reported by: toralf Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.6.5-rc
Severity: Normal Keywords: tor-relay accounting log-message usability
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Played today with accounting and read in notice log :

Mar 19 18:49:51.000 [warn] You have set AccountingMax to use hibernation. You have also chosen a low DirPort or OrPort. This combination can make Tor stop working when it tries to re-attach the port after a period of hibernation. Please choose a different port or turn off hibernation unless you know this combination will work on your platform.
Mar 19 18:49:51.000 [warn] You have set AccountingMax to use hibernation. You have also chosen a low DirPort or OrPort. This combination can make Tor stop working when it tries to re-attach the port after a period of hibernation. Please choose a different port or turn off hibernation unless you know this combination will work on your platform.
Mar 19 18:49:51.000 [notice] Tor 0.2.6.5-rc (git-e0b77cd3194d705f) opening log file.
Mar 19 18:49:51.000 [warn] Failed to unlink /var/lib/tor/data/bw_accounting: No such file or directory
Mar 19 18:49:51.000 [notice] Configured hibernation. This interval begins at 2015-03-01 05:00:00 and ends at 2015-04-01 05:00:00. We have no prior estimate for bandwidth, so we will start out awake and hibernate when we exhaust our quota.
Mar 19 18:49:51.000 [notice] Not advertising DirPort (Reason: AccountingMax enabled)

Beside the doubling /me wonders why tor *warns* about DirPort (or ORPort) - but then *noticed* that it will ignore DirPort (anyway).

Child Tickets

Change History (12)

comment:1 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-final

comment:2 Changed 4 years ago by nickm

Keywords: 028-triaged added

comment:3 Changed 4 years ago by nickm

Status: newneeds_information

comment:4 Changed 4 years ago by toralf

IIRC as a non-native english speaker I stumbled over "a low DirPort or OrPort" versus "Not advertising DirPort"

I belief that made me thinking that if DirPort is not advertised (== ignored) why do I get then the warning above (and even more 2x in a row)?

comment:5 Changed 4 years ago by nickm

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

Move a bunch of (but not all) low-priority items to 0.2.???. If you write a patch, it can still get into 0.2.8

comment:6 Changed 4 years ago by teor

Severity: Normal
Status: needs_informationnew

Tor will advertise the DirPort when AccountingMax is enabled and the usage was significantly under the previous period's quota. In the case quoted above, I am assuming it was the first period, so the DirPort is disabled because there was no way of knowing whether the usage is under quota.

So it's possible that a low DirPort will be disabled, and then re-enabled at the start of the second period, which would then fail unless the tor process has the capability to bind to low ports.

We could clarify the final message to make this clearer.

comment:7 Changed 4 years ago by teor

This could be related to #15661.

comment:8 Changed 3 years ago by teor

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

Milestone renamed

comment:9 Changed 3 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:10 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:11 Changed 2 years ago by nickm

Keywords: 028-triaged removed

comment:12 Changed 2 years ago by nickm

Keywords: tor-relay accounting log-message usability added
Note: See TracTickets for help on using tickets.