Opened 7 years ago

Closed 7 years ago

#7285 closed defect (fixed)

wrong low port hibernation warning

Reported by: weasel Owned by:
Priority: Medium Milestone: Tor: 0.2.4.x-final
Component: Core Tor/Tor Version: Tor: 0.2.4.5-alpha
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I have two orports in my torrc (one for v4, one for v6).

I get the low-port warning twice:

[....] Starting tor daemon...Nov 02 16:40:21.707 [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.
Nov 02 16:40:21.707 [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.

That it's shown twice is one bug.

The other bug is that I should not get this message at all, since these orports are nolisten (and I have noadvertise ports at > 1024).

Cheers,

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by nickm

See #7343 (closed as a duplicate) : this also happens if you do "ORPort 80; ORListenAddress 9090" or whatever.

comment:2 Changed 7 years ago by nickm

Keywords: tor-relay added
Milestone: Tor: 0.2.4.x-final

comment:3 Changed 7 years ago by nickm

Status: newneeds_review

Branch bug7285 in my public repository should fix this; needs review. I'm calling this merely annoying and therefore not worth backporting to 0.2.3, but a second opinion could override me.

comment:4 Changed 7 years ago by nickm

Resolution: fixed
Status: needs_reviewclosed

arma and asn like it; merging.

Note: See TracTickets for help on using tickets.