Opened 12 years ago

Last modified 7 years ago

#388 closed defect (Works for me)

tor crashes after 6 hours

Reported by: mcncyo Owned by: phobos
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.0.18
Severity: Keywords:
Cc: mcncyo Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

tor crashes with this error after about 6 hours

using redhat 3.

Feb 07 19:45:06.358 [warn] connection_watch_events(): Error from libevent setting read event state for 1023 to watched: No such file or directory
Feb 07 19:45:06.373 [warn] connection_watch_events(): Error from libevent setting read event state for 1023 to watched: No such file or directory
Feb 07 19:45:13.787 [warn] connection_unregister(): Error removing read event for 1023
Feb 07 19:45:13.787 [warn] connection_unregister(): Error removing write event for 1023

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

Child Tickets

Change History (16)

comment:1 Changed 12 years ago by weasel

Actually, it's 0.1.1.26 with libevent 1.2a. ulimit -n is 1024.

comment:2 Changed 12 years ago by mcncyo

yep peter has the correct info.

comment:3 Changed 12 years ago by nickm

I'm assuming "Redhat 3" is really "Redhat Enterprise 3".

I don't suppose you managed to get a stack trace out of this? If not, it would help if you could turn
on core dumps "ulimt -c unlimited", and restart Tor to see if it can be made to give more debugging info next time?

(Note: DO NOT send us the core.)

comment:4 Changed 12 years ago by mcncyo

I was wrong this is exactly what I have I fogot I upgrade to 4 a couple of months ago.

1 Gigabyte \ SuperCeleronMarkII \ GA-8LD533
1 Intel \ 2.4 Ghz \ P4 Celeron
2 Generic \ 512 MB \ DDR 266
1 Unknown \ Onboard \ IDE
1 Seagate \ 80GB:IDE:7200RPM Barracuda \ ST380011AS


Installed Software

  • Redhat Enterprise Linux - OS ES 4.0
  • Urchin Urchin 5
  • DarkORB CPanel 6


I did a ulimit -n 8192 and it hasn't crash yet and it has been running for about 12 hours.

I just set ulimit -c unlimited and restart with ulimit -n 8192 just now. So i will update this ticket in about 12 hours if anything change.

comment:5 Changed 12 years ago by nickm

If the bug doesn't reappear, try setting ulimt -c ulimited, and ulimit -n 1024. This might help force the bug
to arise faster, and give us a core we can try to examine.

comment:6 Changed 12 years ago by mcncyo

IT has been crashing without a message in the .log file and no core files.
I am running what you suggest now.

comment:7 Changed 12 years ago by mcncyo

ok I got a bunch of errors

Feb 12 14:26:32.905 [warn] connection_connect(): Error creating network socket: Too many open files
Feb 12 14:26:32.916 [warn] connection_connect(): Error creating network socket: Too many open files
Feb 12 14:26:32.918 [warn] connection_connect(): Error creating network socket: Too many open files
Feb 12 14:26:34.684 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.684 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.685 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.685 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.686 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.686 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.687 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.688 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.689 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.689 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.690 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.690 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.690 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.691 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.691 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.691 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.692 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.692 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.693 [warn] connection_connect(): Error creating network socket: Too many open files
Feb 12 14:26:34.694 [warn] spawn_dnsworker(): Couldn't construct socketpair: Too many open files
Feb 12 14:26:34.694 [warn] spawn_enough_dnsworkers(): Spawn failed. Will try again later.
Feb 12 14:26:34.709 [warn] connection_connect(): Error creating network socket: Too many open files
Feb 12 14:26:34.730 [warn] Couldn't open "/home/tor/.tor/bw_accounting.tmp" for writing: Too many open files
Feb 12 14:26:34.730 [err] accounting_run_housekeeping(): Couldn't record bandwidth usage to disk; exiting.

comment:8 Changed 12 years ago by nickm

So it looks like we're running out of sockets; that's not so weird.

The weird thing is that we're supposed to keep around 32 extra sockets or so beyond what we're using for
connections, so we never run out. I wonder what's making us run out anyway.

comment:9 Changed 12 years ago by phobos

You might wish to try the 0.1.2.8-beta rpm. It uses libevent-1.3a.

comment:10 Changed 12 years ago by phobos

For what it is worth, the latest 0.1.2.10-rc rpm includes libevent 1.3b.

comment:11 Changed 12 years ago by mcncyo

I just switch to a new web hosting provider and havn't had a chance to install tor on it. I will try to install tor on it soon.

comment:12 Changed 12 years ago by phobos

Does Tor work now?

comment:13 Changed 12 years ago by mcncyo

sorry havn't had time to install tor yet been busy setting up a new company. When I get a chance I will install tor on it.

comment:14 Changed 12 years ago by phobos

Ok. I'm going to assume the bug was related to something in the old environment. If it returns, feel free to
open this back up.

comment:15 Changed 12 years ago by phobos

flyspray2trac: bug closed.

comment:16 Changed 7 years ago by nickm

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