tor 0.1.2.17 server died after only a few hours

[Scott Bennett]

>     I wrote:
>>     I switched from 0.1.2.16 to 0.1.2.17 this morning.  About 5 hrs. 20-odd
>>minutes later, tor wrote the following message to the notice log and exited:
>>
>>Sep 04 14:06:29.140 [err] connection.c:2387: assert_connection_ok: Assertion connection_is_writing(conn) || conn->wants_to_write || (conn->type == CONN_TYPE_DIR && TO_DIR_CONN(conn)->is_blocked_on_or_conn) failed; aborting.
>>
>>Does anyone know what caused this?  I can still switch back to 0.1.2.16 if
>>need be.
>
>     It just did it again after being up only a few minutes.  I've now reverted
>to 0.1.2.16 and will stay with that until the next release comes out.  Sigh.

     I can't believe this!  My 0.1.2.16 server just did the same thing!  And
that is after it ran fine for quite some time before trying 0.1.2.17 (this is
the first time 0.1.2.16 has acted up).  Here's the message:

Sep 05 02:09:33.960 [err] connection.c:2391: assert_connection_ok: Assertion connection_is_writing(conn) || conn->wants_to_write || (conn->type == CONN_TYPE_DIR && TO_DIR_CONN(conn)->is_blocked_on_or_conn) failed; aborting.

I really wish I knew what is going on and how to get it to stop.  I've never
looked into the tor source.  Can someone tell me what the message means?  Maybe
it will spur my recognition of some detail previously ignored as insignificant.


                                  Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet:       bennett at cs.niu.edu                              *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *
**********************************************************************