Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#5136 closed defect (fixed)

“Registered server transport ...” should not be a warning

Reported by: rransom Owned by: asn
Priority: High Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-bridge
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


From register_server_proxy in src/or/transports.c:

    /* LOG_WARN so that the bridge operator can easily find the
       transport's port in the log file and send it to the users. */
    log_warn(LD_GENERAL, "Registered server transport '%s' at '%s:%d'",
             t->name, fmt_addr(&t->addr), (int)t->port);

Child Tickets

Change History (6)

comment:1 Changed 9 years ago by rransom

Component: Pluggable transportTor Bridge

comment:2 Changed 9 years ago by asn

I agree. What should it be? LOG_INFO is probably the right answer, but it won't be easily found by bridge operators (they will also have to enable 'info' logging which is messy).

Maybe, in the future, we will send this information to the control port andLOG_WARN won't be necessary, but at the moment I can't see a better solution.

comment:3 Changed 9 years ago by nickm

INFO or NOTICE. It is definitely not a warning.

comment:4 Changed 9 years ago by nickm

Resolution: fixed
Status: newclosed

Downgraded to NOTICE in 936b7b7

comment:5 Changed 8 years ago by nickm

Keywords: tor-bridge added

comment:6 Changed 8 years ago by nickm

Component: Tor BridgeTor
Note: See TracTickets for help on using tickets.