On Mon, Jul 03, 2006 at 02:26:40PM +0200, Florian Reitmeir wrote: > What do you expect? Is this a statement or a call for help? Both. Tor used to be really aggressive on this box, now it's mostly idling. I've verified the pipe should be able of at least ~500 kByte/s throughput. > If you want help it would be helpful to add some system data: > - debian version (woody/sarge/etch/sid...) testing/unstable I have in /etc/apt/sources.list deb http://mirror.noreply.org/pub/tor sarge main deb-src http://mirror.noreply.org/pub/tor sarge main deb http://mirror.noreply.org/pub/tor experimental-0.1.1.x-sarge main deb-src http://mirror.noreply.org/pub/tor experimental-0.1.1.x-sarge main > - architecture, kernel version i386, 2.6.8-2-686 It's a 1.8 GHz Duron box with 256 MBytes which typically has some 5-6% tor CPU load and about 30% memory according to top. > - tor version v0.1.1.21 > - tor node name? redgene > - and maybe a description what the term "tor crashes" means, is it a memory > leak? freezes the whole system? do you have some nice logs? whats in Nothing, the task just dies (I usually notice it by looking on serifos), and that's it. Nothing in the logs. Perhaps at least for Debian the init scripts should be more aggressive, and restart the task immediately when it's crashed. > /var/log/tor/log after the crash? Nothing unusual as far as I can see: Jul 03 06:25:34.506 [notice] Tor 0.1.1.21 opening new log file. Jul 03 14:32:13.626 [notice] hibernate_begin(): Interrupt: will shut down in 30 seconds. Interrupt again to exit now. Jul 03 14:32:43.584 [notice] consider_hibernation(): Clean shutdown finished. Exiting. Jul 03 14:32:49.316 [notice] Tor 0.1.1.21 opening log file. Jul 03 14:32:49.527 [notice] Your Tor server's identity key fingerprint is 'redgene 3BB0 DC6E A321 256D DD11 5519 7DBD 3F1E 4862 3549' Jul 03 14:32:50.523 [notice] We now have enough directory information to build circuits. Jul 03 14:32:50.687 [notice] router_orport_found_reachable(): Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jul 03 14:32:51.383 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Jul 02 06:25:22.809 [notice] Tor 0.1.1.21 opening new log file. Jul 03 06:25:34.435 [notice] do_hup(): Received reload signal (hup). Reloading config. Jul 01 06:25:31.956 [notice] Tor 0.1.1.21 opening new log file. Jul 01 23:16:39.030 [notice] hibernate_begin(): Interrupt: will shut down in 30 seconds. Interrupt again to exit now. Jul 01 23:17:09.703 [notice] consider_hibernation(): Clean shutdown finished. Exiting. Jul 01 23:17:24.867 [notice] Tor 0.1.1.21 opening log file. Jul 01 23:17:25.349 [notice] Your Tor server's identity key fingerprint is 'redgene 3BB0 DC6E A321 256D DD11 5519 7DBD 3F1E 4862 3549' Jul 01 23:17:27.182 [notice] We now have enough directory information to build circuits. Jul 01 23:17:27.746 [notice] router_orport_found_reachable(): Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jul 01 23:17:28.275 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Jul 02 06:25:22.758 [notice] do_hup(): Received reload signal (hup). Reloading config. Jun 30 06:25:31.988 [notice] Tor 0.1.1.21 opening new log file. Jul 01 06:25:31.955 [notice] do_hup(): Received reload signal (hup). Reloading config. Jun 29 06:25:03.123 [notice] Tor 0.1.1.21 opening new log file. Jun 30 06:25:31.987 [notice] do_hup(): Received reload signal (hup). Reloading config. Jun 28 06:25:32.537 [notice] Tor 0.1.1.21 opening new log file. Jun 29 06:25:03.122 [notice] do_hup(): Received reload signal (hup). Reloading config. -- Eugen* Leitl <a href="http://leitl.org";>leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE
Attachment:
signature.asc
Description: Digital signature