PDA

View Full Version : [ubuntu] Tor node problem



bitf
July 2nd, 2009, 01:17 AM
I started running a Tor node using Vidalia, it worked fine on the first day, but on the seconed day I got the message

Jul 01 19:03:51.972 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Jul 01 19:03:51.972 [Notice] Closing partially-constructed listener OR listener on 0.0.0.0:9001
Jul 01 19:03:51.972 [Notice] Closing partially-constructed listener Directory listener on 0.0.0.0:9030
Jul 01 19:03:51.972 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Jul 01 19:03:51.972 [Error] Reading config failed--see warnings above.

A system monitor check confirmed was not running, so I figured it was the fact that had changed the torc files to make it firewall friendly, but when I reset it to what I believe was the original configuration and the restarted the computer, the messages persisted.
Could it be that my IP has been reset at least once between use or is it something else?

Boondoklife
July 2nd, 2009, 02:07 AM
Can you post the output of `netstat -an | grep 127.0.0.1` and `netstat -pa | grep localhost`

bitf
July 2nd, 2009, 03:04 AM
Can you post the output of `netstat -an | grep 127.0.0.1` and `netstat -pa | grep localhost`
respectively:
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN

and:

(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 localhost.localdoma:ipp *:* LISTEN -
tcp 0 0 localhost.localdom:9050 *:* LISTEN -

Boondoklife
July 2nd, 2009, 04:20 AM
respectively:
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN

and:

(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 localhost.localdoma:ipp *:* LISTEN -
tcp 0 0 localhost.localdom:9050 *:* LISTEN -

put a sudo infront of the second command. It does indeed appear that tor is already running as you can see it on localhost and 127.0.0.1.

Are you not able to connect to it?

bitf
July 2nd, 2009, 05:17 AM
put a sudo infront of the second command. It does indeed appear that tor is already running as you can see it on localhost and 127.0.0.1.

Are you not able to connect to it?
Here it is (part of it)
tcp 0 0 localhost.localdom:9050 *:* LISTEN 3198/tor
How do I stop it so I can control it through Vidalia?

bitf
July 3rd, 2009, 09:31 PM
bump

Boondoklife
July 3rd, 2009, 10:15 PM
Doesnt vidalia simply connect to the tor service? I know with windoes there is a way to tell it not to start tor so maybe there is an option in there you can change.

I dont use vidalia, I have tor installed on my NAS and just your firefox-torbutton to connect to it.

bitf
July 3rd, 2009, 11:45 PM
Doesnt vidalia simply connect to the tor service? I know with windoes there is a way to tell it not to start tor so maybe there is an option in there you can change.

I dont use vidalia, I have tor installed on my NAS and just your firefox-torbutton to connect to it.
I tried telling Vidalia not to start Tor until I tell it to, but got the same error message when I started Tor

Boondoklife
July 4th, 2009, 12:12 AM
Well only thing left I can think of would be to check the services that are started, System -> Admin -> Services If to r is there disable it.

bitf
July 4th, 2009, 12:23 AM
Well only thing left I can think of would be to check the services that are started, System -> Admin -> Services If to r is there disable it.

It's not there (Tor, not the services)

Boondoklife
July 4th, 2009, 12:32 AM
try to kill it and then start vidalia

killall -9 tor

bitf
July 4th, 2009, 10:27 PM
try to kill it and then start vidalia

killall -9 tor

Did that, netstat confirmed that Tor was not running. But Vidalia wouldn't start Tor, the logs were:
Jul 04 16:21:38.419 [Warning] Error setting configured user: <myname> not found
Jul 04 16:21:38.419 [Warning] Failed to parse/validate config: Problem with User value. See logs for details.
Jul 04 16:21:38.419 [Error] Reading config failed--see warnings above.

Boondoklife
July 4th, 2009, 10:47 PM
Did that, netstat confirmed that Tor was not running. But Vidalia wouldn't start Tor, the logs were:
Jul 04 16:21:38.419 [Warning] Error setting configured user: <myname> not found
Jul 04 16:21:38.419 [Warning] Failed to parse/validate config: Problem with User value. See logs for details.
Jul 04 16:21:38.419 [Error] Reading config failed--see warnings above.

Looks like your config is not setup right, check the log as it says and see what it says.

bitf
July 5th, 2009, 04:56 AM
Looks like your config is not setup right, check the log as it says and see what it says.
which log?

bitf
July 7th, 2009, 12:32 AM
bump

bitf
July 9th, 2009, 03:52 PM
bump

bitf
July 10th, 2009, 03:03 PM
bump
bump