Morgen,
ich habe ein kleines Problem.
Tor startet beim Booten und doch nicht.
Ich beschreibe Mal die Symtome:
Ich starte meinen Rechner und finde in der boot-log folgendes:
Jun 23 08:40:00 rc2: There is no /var/run/tor directory. Creating one for you. Jun 23 08:40:00 rc2: Raising maximum number of filedescriptors (ulimit -n) to 8192. Jun 23 08:40:00 rc2: Starting tor daemon: tor... Jun 23 08:40:00 rc2: Jun 23 08:40:00.860 [notice] Tor v0.1.2.14. This is experimental software. Do not rely on it for strong anonymity. Jun 23 08:40:00 rc2: Jun 23 08:40:00.864 [notice] Initialized libevent version 1.1a using method epoll. Good. Jun 23 08:40:00 rc2: Jun 23 08:40:00.864 [notice] Opening OR listener on 0.0.0.0:9090 Jun 23 08:40:00 rc2: Jun 23 08:40:00.865 [notice] Opening Directory listener on 0.0.0.0:9091 Jun 23 08:40:00 rc2: Jun 23 08:40:00.865 [notice] Opening Socks listener on 127.0.0.1:9050 Jun 23 08:40:00 rc2: done.
Das ist auch so korrekt.
Nun suche ich nach dem Prozess:
ps -A | grep tor 3264 ? 00:00:00 usb-storage 4739 ? 00:00:00 hald-addon-stor 4741 ? 00:00:00 hald-addon-stor 4746 ? 00:00:00 hald-addon-stor 5582 ? 00:00:03 ktorrent
Da ist er nicht.
Dann klappere ich Mal die Ports ab:
$ netstat -a | grep 9050 $ netstat -a | grep 9090 $ netstat -a | grep 9091 $ netstat -a | grep 9030
Auch nicht...
Schaue ich Mal die Logs an:
$ ls -l total 20 -rw-r--r-- 1 debian-tor adm 0 2007-06-23 08:45 log -rw-r--r-- 1 debian-tor adm 2070 2007-06-23 08:40 log.1
Auch seltsam...
Wenn ich aber tor manuell starte:
$ sudo /etc/rc2.d/S20tor start Raising maximum number of filedescriptors (ulimit -n) to 8192. Starting tor daemon: tor... Jun 23 09:04:40.923 [notice] Tor v0.1.2.14. This is experimental software. Do not rely on it for strong anonymity. Jun 23 09:04:40.927 [notice] Initialized libevent version 1.1a using method epoll. Good. Jun 23 09:04:40.927 [notice] Opening OR listener on 0.0.0.0:9090 Jun 23 09:04:40.928 [notice] Opening Directory listener on 0.0.0.0:9091 Jun 23 09:04:40.928 [notice] Opening Socks listener on 127.0.0.1:9050 done.
Dann schaut alles viel besser aus:
$ ps -A | grep tor 3264 ? 00:00:00 usb-storage 4739 ? 00:00:00 hald-addon-stor 4741 ? 00:00:00 hald-addon-stor 4746 ? 00:00:00 hald-addon-stor 5582 ? 00:00:05 ktorrent 15620 ? 00:00:07 tor $ netstat -a | grep 9050 tcp 0 0 localhost:9050 *:* LISTEN $ netstat -a | grep 9090 tcp 0 0 *:9090 *:* LISTEN tcp 0 0 xxxx:9090 yyyy:63137 ESTABLISHED tcp 0 0 xxxx:9090 yyyy:63137 ESTABLISHED tcp 0 0 xxxx:9090 yyyy:63137 ESTABLISHED tcp 0 0 xxxx:9090 yyyy:63137 ESTABLISHED tcp 0 0 xxxx:9090 yyyy:63137 ESTABLISHED tcp6 0 0 xxxx:9090 yyyy:63137 TIME_WAIT tcp6 0 0 xxxx:9090 yyyy:63137 TIME_WAIT $ netstat -a | grep 9091 tcp 0 0 *:9091 *:* LISTEN $ netstat -a | grep 9030 $ ls -l total 24 -rw-r--r-- 1 debian-tor adm 1001 2007-06-23 09:05 log -rw-r--r-- 1 debian-tor adm 2070 2007-06-23 08:40 log.1 $ cat log Jun 23 09:04:40.928 [notice] Tor 0.1.2.14 opening new log file. Jun 23 09:04:41.559 [notice] Your Tor server's identity key fingerprint is 'xxx xxx xxx xxx' Jun 23 09:04:53.546 [notice] We now have enough directory information to build circuits. Jun 23 09:05:01.815 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Jun 23 09:05:01.815 [notice] Now checking whether ORPort xxx:80 and DirPort xxx:443 are reachable... (this may take up to 20 minutes -- look for log messages indicating success) Jun 23 09:05:05.827 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Jun 23 09:05:14.878 [notice] Not advertising DirPort (Reason: BandwidthRate under 50KB) Jun 23 09:05:17.877 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jun 23 09:05:45.002 [notice] Performing bandwidth self-test...done.
Hat jemand eine Idee, was da schief läuft? Und wie ich das hinbekomme?
Grüße