[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: spawn_enough_dnsworkers
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: spawn_enough_dnsworkers
- From: tildeOne tor router <admin@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 01 Jul 2005 19:39:36 +0200
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Fri, 01 Jul 2005 13:40:14 -0400
- In-reply-to: <42C2FC43.7000005@tilde-one.dyndns.org>
- References: <42BA63E1.2030405@tilde-one.dyndns.org> <20050623080151.GL29002@localhost.localdomain> <42BA7375.6060106@tilde-one.dyndns.org> <20050629192733.GS29002@localhost.localdomain> <42C2FC43.7000005@tilde-one.dyndns.org>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29.06.2005 21:53, tildeOne tor router wrote:
> On 29.06.2005 21:27, Roger Dingledine wrote:
> | On Thu, Jun 23, 2005 at 10:31:49AM +0200, tildeOne tor router wrote:
> |> Ok, I didn't describe this very well. Indeed when looking at the logs
> |> I'd think there is no problem. But the following points make me think
> |> there is:
> |>
> |> - - no DSL activity (normally heavy action while running tor)
> |> - - http://serifos.eecs.harvard.edu:8000/cgi-bin/exit.pl?sortbw=1&addr=1
> |> showing the "unresponsive node" flag
> |> - - when restarting tor -> no such process, none killed
> |> - - everytime this happened the last entry in the log was spawn_enough...
> |
> | Ok, I think the spawn_enough_dnsworkers log entry is just a coincidence.
> |
> | The real problem is that your Tor process is crashing unexpectedly and
> | without any log entries to indicate what's going on.
> |
> | Perhaps you are running a buggy version of libevent? You need at least
> | libevent 1.1 on Linux, and 1.1a on *BSD.
> |
> | (Are these problems still happening for you, or did they go away?)
> |
> | --Roger
> |
>
> Hi Roger,
>
> libevent is 1.1 on Linux. It hasn't happened again in the meantime (I
> had to restart the machine relative often for other reasons though, so
> tor wasn't running for more than a day without a break) , I'll be
> watching out.
>
> --
> +-+-+-+-+-+-+-+-+ +-+-+
> |t|i|l|d|e|0|n|e| |O|R|
> +-+-+-+-+-+-+-+-+ +-+-+
>
> server key fingerprint
> 5F69 47DA 52A0 99B7 06C8 8319 6DE8 4803 7817 D32A
>
> signing key fingerprint
> A812 3E53 75A0 21A4 C73B 7438 35B4 F926 582O 4CEC
>
It happened again (this time with version 0.1.0.11):
Jul 01 12:58:11.014 [notice] Your DirPort is reachable from the outside.
Excellent.
Jul 01 13:00:20.064 [notice] Your ORPort is reachable from the outside.
Excellent. Publishing server descriptor.
...
Jul 01 17:59:42.204 [notice] conn_close_if_marked(): Conn (addr
[scrubbed], fd 117, type OR, state 5) is being closed, but there are
still 168960 bytes we can't write. (Marked at main.c:579)
Jul 01 18:22:37.592 [notice] spawn_enough_dnsworkers(): 9 of 12
dnsworkers are idle. Killing one.
Jul 01 18:22:37.592 [notice] spawn_enough_dnsworkers(): 8 of 11
dnsworkers are idle. Killing one.
After this no traffic at all, the tor.pid was still there but no process
running and therefor none killed when restarting.
Now I don't think it's just a coincidence.
- --
+-+-+-+-+-+-+-+-+ +-+-+
|t|i|l|d|e|0|n|e| |O|R|
+-+-+-+-+-+-+-+-+ +-+-+
server key fingerprint
5F69 47DA 52A0 99B7 06C8 8319 6DE8 4803 7817 D32A
signing key fingerprint
A812 3E53 75A0 21A4 C73B 7438 35B4 F926 582O 4CEC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFCxX/YNbT5JlggTOwRAol+AJ9RM9WRfGgi+fP17Qym8GEI7dWO+QCfVfeO
pakvmNqhSbiNlHgiEI3IWFk=
=hwwy
-----END PGP SIGNATURE-----