Opened 11 years ago

Last modified 7 years ago

#775 closed defect (Works for me)

tor crash on libevent error

Reported by: amis Owned by:
Priority: Very High Milestone:
Component: Core Tor/Tor Version: 0.2.0.29-rc
Severity: Keywords:
Cc: amis, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Jul 15 03:44:56.239 [notice] Tor 0.2.0.28-rc (r15188) opening new log file.
...
Jul 15 18:53:24.691 [err] Error from libevent: event_queue_remove: 0x9c331c38(fd 0) not on queue 1
...
Jul 17 11:58:35.282 [notice] Tor 0.2.1.2-alpha (r15383) opening log file.
...
Jul 17 23:33:22.515 [err] Error from libevent: event_queue_remove: 0xb2797c38(fd 0) not on queue 1
Hello,
since the last two days i've the same error on mxr running on a debian hardy with all standard scripts.
I've no change in the config since some days.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Attachments (1)

log (8.9 KB) - added by mfr 11 years ago.
log as requested

Download all attachments as: .zip

Change History (11)

comment:1 Changed 11 years ago by mfr

[notice] Initialized libevent version 1.3e using method epoll. Good.

comment:2 Changed 11 years ago by nickm

If you can get a stack trace for this, that would be great.

Changed 11 years ago by mfr

Attachment: log added

log as requested

comment:3 Changed 11 years ago by mfr

I've attached a lob but it's a poor log.

comment:4 Changed 11 years ago by mfr

Here is a new log for the last same bug seems it's a dns bug:
Perhaps when there are too many request waiting and a dns problem ?
Jul 19 04:36:09.341 [info] launch_resolve(): Launching eventdns request for "www.le"
Jul 19 04:36:09.342 [info] eventdns: Resolve requested for www.le
Jul 19 04:36:09.342 [info] eventdns: Setting timeout for request b5744600
Jul 19 04:36:09.342 [info] launch_resolve(): Launching eventdns request for "www.mu"
Jul 19 04:36:09.342 [info] eventdns: Resolve requested for www.mu
Jul 19 04:36:09.343 [info] eventdns: Setting timeout for request b79eb400
Jul 19 04:36:09.343 [info] launch_resolve(): Launching eventdns request for "tw"
Jul 19 04:36:09.343 [info] eventdns: Resolve requested for tw
Jul 19 04:36:09.343 [info] eventdns: Setting timeout for request b79eb800
Jul 19 04:36:09.344 [info] launch_resolve(): Launching eventdns request for "te"
Jul 19 04:36:09.344 [info] eventdns: Resolve requested for te
Jul 19 04:36:09.344 [info] eventdns: Setting timeout for request b79ebc00
Jul 19 04:36:09.345 [info] eventdns: Removing timeout for request b797ce00
Jul 19 04:36:09.346 [info] launch_resolve(): Launching eventdns request for "www.pu"
Jul 19 04:36:09.346 [info] eventdns: Resolve requested for www.pu
Jul 19 04:36:09.347 [info] eventdns: Setting timeout for request b7a00200
Jul 19 04:36:09.347 [info] launch_resolve(): Launching eventdns request for "www.a"
Jul 19 04:36:09.347 [info] eventdns: Resolve requested for www.a
Jul 19 04:36:09.347 [info] eventdns: Setting timeout for request b7a03200
Jul 19 04:36:09.347 [info] launch_resolve(): Launching eventdns request for "www.t"
Jul 19 04:36:09.347 [info] eventdns: Resolve requested for www.t
Jul 19 04:36:09.347 [info] eventdns: Setting timeout for request b7c5e200
Jul 19 04:36:09.347 [info] launch_resolve(): Launching eventdns request for "www.c"
Jul 19 04:36:09.347 [info] eventdns: Resolve requested for www.c
Jul 19 04:36:09.347 [info] launch_resolve(): Launching eventdns request for "m"
Jul 19 04:36:09.347 [info] eventdns: Resolve requested for m
Jul 19 04:36:09.347 [info] launch_resolve(): Launching eventdns request for "f"
Jul 19 04:36:09.348 [info] eventdns: Resolve requested for f
Jul 19 04:36:09.348 [info] launch_resolve(): Launching eventdns request for "h"
Jul 19 04:36:09.348 [info] eventdns: Resolve requested for h
Jul 19 04:36:09.349 [info] eventdns: Removing timeout for request b797c000
Jul 19 04:36:09.350 [info] eventdns: Setting timeout for request b7c5e800
Jul 19 04:36:09.351 [info] eventdns: Setting timeout for request b172a400
Jul 19 04:36:09.351 [info] eventdns: Removing timeout for request b79eb800
Jul 19 04:36:09.351 [info] eventdns: Setting timeout for request b79f7000
Jul 19 04:36:09.351 [info] eventdns: Removing timeout for request b7a03200
Jul 19 04:36:09.351 [info] eventdns: Setting timeout for request b79f7400
Jul 19 04:36:09.352 [info] launch_resolve(): Launching eventdns request for "z"
Jul 19 04:36:09.352 [info] eventdns: Resolve requested for z
Jul 19 04:36:09.353 [info] launch_resolve(): Launching eventdns request for "www."
Jul 19 04:36:09.353 [info] eventdns: Resolve requested for www.
Jul 19 04:36:09.353 [info] launch_resolve(): Launching eventdns request for "www."
Jul 19 04:36:09.353 [info] eventdns: Resolve requested for www.l
Jul 19 04:36:09.353 [info] launch_resolve(): Launching eventdns request for "d"
Jul 19 04:36:09.353 [info] eventdns: Resolve requested for d
Jul 19 04:36:09.353 [info] launch_resolve(): Launching eventdns request for "p"
Jul 19 04:36:09.353 [info] eventdns: Resolve requested for p
Jul 19 04:36:09.354 [info] launch_resolve(): Launching eventdns request for "www.m"
Jul 19 04:36:09.354 [info] eventdns: Resolve requested for www.m
Jul 19 04:36:09.354 [info] launch_resolve(): Launching eventdns request for "www.t"
Jul 19 04:36:09.354 [info] eventdns: Resolve requested for www.t
Jul 19 04:36:09.354 [info] launch_resolve(): Launching eventdns request for "www.s"
Jul 19 04:36:09.354 [info] eventdns: Resolve requested for www.s
Jul 19 04:36:09.359 [info] launch_resolve(): Launching eventdns request for "www.t"
Jul 19 04:36:09.359 [info] eventdns: Resolve requested for www.t
Jul 19 04:36:09.362 [info] eventdns: Removing timeout for request b79f7000
Jul 19 04:36:09.363 [info] eventdns: Setting timeout for request b79f7a00
Jul 19 04:36:09.363 [info] eventdns: Removing timeout for request b5bdfe00
Jul 19 04:36:09.363 [info] eventdns: Setting timeout for request b5cd5000
Jul 19 04:36:09.365 [info] eventdns: Removing timeout for request b172a400
Jul 19 04:36:09.365 [info] eventdns: Setting timeout for request b5cd5400
Jul 19 04:36:09.367 [err] Error from libevent: event_queue_remove: 0xb172a438(fd 0) not on queue 1

comment:5 Changed 11 years ago by nickm

A stack trace would be what would help lots here; can you get one? The log isn't terribly helpful.

comment:6 Changed 10 years ago by phobos

Any chance you've been able to get a trace?

comment:7 Changed 10 years ago by mfr

Infortunatly no.

I'm not running a Tor node for the moment and i have not experienced this problem after this period of July.

comment:8 Changed 10 years ago by nickm

I'm going to close this as "works for me"; there isn't enough info here to figure out what happened without a stack
trace. If anybody runs into this again, we should reopen the bug.

comment:9 Changed 10 years ago by nickm

flyspray2trac: bug closed.

comment:10 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.