[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #2933 [Tor Client]: Error from libevent: evdns.c:1360: Assertion req != port->pending_replies failed in server_port_flush



#2933: Error from libevent: evdns.c:1360: Assertion req != port->pending_replies
failed in server_port_flush
------------------------+---------------------------------------------------
 Reporter:  mr-4        |          Owner:                     
     Type:  defect      |         Status:  new                
 Priority:  normal      |      Milestone:                     
Component:  Tor Client  |        Version:  Tor: 0.2.2.24-alpha
 Keywords:              |         Parent:                     
   Points:              |   Actualpoints:                     
------------------------+---------------------------------------------------

Comment(by mr-4):

 Replying to [comment:1 Sebastian]:
 > On the libevent list you reported the error, but slightly differently.
 Where is the error triggered? eventdns.c shouldn't be used with libevent2
 at all iirc, so I'm confused about this report.

 The error is triggered in one of the following two scenarios: when my
 openvpn connection is closed - about a minute after openvpn manages to
 reconnect me again I get the following in my syslog, after which tor bails
 out:

 Apr 17 00:58:20 test1 openvpn[4773]: Initialization Sequence Completed
 Apr 17 00:59:24 test1 Tor[6268]: Error from libevent: evdns.c:1360:
 Assertion req != port->pending_replies failed in server_port_flush

 The second case is when my openvpn connection is pretty congested (i.e. it
 has a lot of traffic - mainly from my bittorent client - to deal with)
 this is what I get in my syslog (this is after I have restarted tor after
 it bailed out above and when there is initially heavy trafiic on my newly
 established openvpn connection):

 Apr 17 01:01:23 test1 Tor[6635]: Error from libevent: evdns.c:1360:
 Assertion req != port->pending_replies failed in server_port_flush

 After which tor bails out again.

 Please note that when the traffic is fairly light-ish or openvpn does not
 disconnect me tor is happily running without any problems.

 It is also true that I reported this on the libevent mailing list (I think
 it was yesterday) as I was not 100% sure whether this is a tor error or a
 libevent error (apologies, but I am not an expert in either of these
 packages!), though I am not aware what have I reported to be "different"
 from my original submission here.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2933#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs