Opened 8 years ago

Last modified 2 years ago

#4373 new defect

When we close a conn due to bad CERTS cell, we complain about stuff in our outbuf

Reported by: arma Owned by: nickm
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.3.7-alpha
Severity: Trivial Keywords: tor-client warning outbuf
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

While looking at bug #4371, here's what my client said:

Nov 01 04:30:45.000 [warn] Certificate not yet valid: is your system clock set incorrectly?
Nov 01 04:30:45.000 [warn] (certificate lifetime runs from Nov  1 12:15:08 2011 GMT through Oct 31 12:15:08 2012 GMT. Your time is Nov 01 08:30:45 2011 GMT.)
Nov 01 04:30:45.000 [notice] We stalled too much while trying to write 512 bytes to address "120.50.40.184".  If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 14, type OR, state 7, marked at command.c:995).

Looks like we had already written our netinfo cell to the outbuf, but hadn't flushed it. Since I'm a client and this was an OR connection, it gets to be severity notice. Fun.

For the client side, I think this bug might be resolved by the proposed fix to #4361.

But my directory authority experiences something similar:
Nov 01 06:04:10.000 [info] conn_close_if_marked(): Conn (addr "120.50.40.184", fd 1609, type OR, state 7) marked, but wants to flush 916 bytes. (Marked at command.c:995) Nov 01 06:04:10.000 [info] conn_close_if_marked(): We stalled too much while trying to write 916 bytes to address "120.50.40.184". If this happens a lot, either something is wrong with your network connection, or something is wrong with theirs. (fd 1609, type OR, state 7, marked at command.c:995).
I wonder what's sitting in its outbuf.

Child Tickets

Change History (7)

comment:1 Changed 7 years ago by nickm

Owner: set to nickm
Status: newaccepted

comment:2 Changed 7 years ago by nickm

Priority: normalminor

Slightly annoying, but can slip.

comment:3 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

comment:4 Changed 7 years ago by nickm

Keywords: tor-client added

comment:5 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:6 Changed 6 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: unspecified

Info-level log message; not hurting anything; not a regression. It can wait.

comment:7 Changed 2 years ago by nickm

Keywords: warning outbuf added
Points: 1
Severity: Trivial
Status: acceptednew
Note: See TracTickets for help on using tickets.