I am not, but I fail the "make test" on 0.1.2.17 as follows: ================================ v3_networkstatus ........... File test.c: line 2548 (test_v3_networkstatus): Assertion failed: (v1->published==vote->published) 1188938513!=1188938536
Because of this I have not yet done a "make install". What other info would be useful in tracking down this failure? . . . Wesley -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Mathewson Sent: September 4, 2007 4:27 PM To: [email protected] Subject: Re: tor 0.1.2.17 server died after only a few hours On Tue, Sep 04, 2007 at 03:23:56PM -0500, Scott Bennett wrote: > 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. Is anybody else seeing this? Can you get a stack trace? -- Nick Mathewson
