Bug: Emptied a dirserv buffer, but it's still spooling!
On moria1, running valgrind so things are slower than usual, I got these two Bug: lines (client IP address replaced with "[ip]"):
Jun 20 18:11:24.982 [info] connection_handle_write_impl(): tls error ([ip]:65063). breaking. Jun 20 18:11:24.982 [info] connection_or_notify_error(): called for [ip]:65063 Jun 20 18:11:24.982 [info] connection_close_immediate(): fd 571, type OR, state open, 1024 bytes on outbuf. Jun 20 18:11:25.000 [warn] connection_dir_finished_flushing(): Bug: Emptied a dirserv buffer, but it's still spooling! (on Tor 0.3.5.0-alpha-dev e4e949e901400c85) Jun 20 18:11:25.000 [warn] connection_mark_for_close_internal_(): Bug: Duplicate call to connection_mark_for_close at src/or/directory.c:5229 (first at src/or/main.c:1218) (on Tor 0.3.5.0-alpha-dev e4e949e901400c85) Jun 20 18:11:25.000 [info] connection_edge_reached_eof(): conn (fd -1) reached eof. Closing. Jun 20 18:11:25.001 [info] connection_free_minimal(): Freeing linked Exit connection [open] with 0 bytes on inbuf, 0 on outbuf.
I'm putting this in the 0.3.5 milestone since that's the version I was running, but I bet it's a bug in earlier releases too.