nickm at freehaven.net
Fri Sep 28 14:31:40 UTC 2007
On Thu, Sep 27, 2007 at 04:46:11PM -0700, Michael_google gmail_Gersten wrote:
> I had a server crash today.
> I first shut down the Or-port, to try to let all connections close.
> When it was time to actually say "Time to stop", I re-enabled the
> Or-port, and then sent a sigint. (If I send sigint without first
> re-enabling the or-port, Tor assumes that it should stop immediately,
> without notifying the clients).
> Tor crashed about a minute later. I don't know if it was related or not.
> This is 1.2.17
Interesting! Is this reproducible?
> Note: Even 50 minutes after closing my or port, I was still almost at
> full bandwidth (I had just started to see a drop below full).
Most strange. I'm wondering whether your server was accepting new
circuits (which would be wrong) or whether all this bandwidth was in
old circuits (which would be unlikely).
Oh! By any chance is your ORListenAddress set in your torrc? The
code in server_mode in router.c is:
if (options->ClientOnly) return 0;
return (options->ORPort != 0 || options->ORListenAddress);
This could be problematical. Roger: is this really what we want to
> Sep 27 15:32:57 stbmac Tor: Received reload signal (hup).
> Reloading config.\n
> Sep 27 15:32:57 stbmac Tor: Closing no-longer-configured OR
> listener on 0.0.0.0:9001\n
> Sep 27 15:32:57 stbmac Tor: Closing old OR listener on 0.0.0.0:9001\n
> Sep 27 16:22:59 stbmac Tor: Received reload signal (hup).
> Reloading config.\n
> Sep 27 16:22:59 stbmac Tor: Opening OR listener on 0.0.0.0:9001\n
> Sep 27 16:23:00 stbmac Tor: Your Tor server's identity key
> fingerprint is 'nsavaxBangKremvax 11E5 D291 5CE9 89C9 F258 1BEC A49A
> 127D 7022 AC15'\n
> Sep 27 16:23:00 stbmac Tor: Now checking whether ORPort
> 126.96.36.199:9001 and DirPort 188.8.131.52:9030 are reachable...
> (this may take up to 20 minutes -- look for log messages indicating
> Sep 27 16:23:07 stbmac Tor: Interrupt: will shut down in 240
> seconds. Interrupt again to exit now.\n
> Sep 27 16:24:10 stbmac Tor: Resolved "img9.imagepile.net" which
> was already resolved; ignoring\n
> Sep 27 16:24:10 stbmac Tor: eventdns: Nameserver
> 184.108.40.206 is back up\n
> Sep 27 16:24:12 stbmac crashdump: tor crashed
> Sep 27 16:24:12 stbmac crashdump: crash report written to:
Did you get a core? Was there anything useful in tor.crash.log?
There's nothing in the log above that indicates where the crash might
have come from.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 652 bytes
Desc: not available
More information about the tor-dev