Opened 13 years ago

Last modified 7 years ago

#360 closed defect (Works for me)

Error from libevent: event_queue_remove: 0xfa5260(fd -1) not on queue 1

Reported by: Maschi Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.2.3-alpha
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi,

the following error message appeared one time in the logfile:
---snip---
Nov 15 11:51:26.681 [err] Error from libevent: event_queue_remove: 0xfa5260(fd -1) not on queue 1
---snap---

System:
Server road2nowhere
OS: SuSE 10.0 64Bit
libevent version: 1.1-2
Openssl version: OpenSSL 0.9.7g 11 Apr 2005

regards,
Joerg

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (9)

comment:1 Changed 13 years ago by Maschi

Oups, forgot this info:

The Tor server is connectable and in use (tested with tcpdump).

comment:2 Changed 13 years ago by Maschi

My first comment was a mistake.
The Tor server died.

comment:3 Changed 13 years ago by nickm

Looks like an internal libevent bug, but it'll be hard to track down without a backtrace or core file.
Has this happened again? Do you have any more information about what was going on when it crashed?

comment:4 Changed 13 years ago by phobos

Try updating to 0.1.2.8-beta.

comment:5 Changed 13 years ago by phobos

The latest libevent available to suse is 1.1-2 which is 1.1a with some patches applied as far as I can tell.
Your best bet may be to uninstall the suse package, manually compile the source and install libevent 1.3b.

comment:6 Changed 13 years ago by phobos

Did you ever compile libevent 1.3b and test out tor? The latest 0.1.2.12-rc rpm for SuSe contains libevent 1.3b
statically included in the Tor binary.

comment:7 Changed 13 years ago by nickm

No sign of the origianl bug reporter since February. Since nobody else has reported this, and since
libevent 1.3b fixes a number of bugs in 1.1a, I'm going to close this bug as "Works for me".

Joerg: if you have a chance to look at this issue again, and the latest stable Tor (0.1.2.14) and the
latest stable libevent (1.3b) _still_ have this problem, then please re-open the bug.

comment:8 Changed 13 years ago by nickm

flyspray2trac: bug closed.
Nearly 4 months with no sign of bug, or bug reporter.

comment:9 Changed 7 years ago by nickm

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