Vidalia detected that the Tor software exited unexpectedly?
- by Rana Muhammad Waqas
I have installed the vidalia by following these instructions everything went as they mentioned. When I started vidalia it gave me the error:
Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.
I found that bug here and followed their instructions to fix it and now after that
it says:
Vidalia detected that the Tor software exited unexpectedly.
Please check the message log for recent warning or error messages.
Logs of Vidalia
Oct 18 02:15:06.937 [Notice] Tor v0.2.3.25 (git-3fed5eb096d2d187)
running on Linux. Oct 18 02:15:06.937 [Notice] Tor can't help you if
you use it wrong! Learn how to be safe at
https://www.torproject.org/download/download#warning Oct 18
02:15:06.937 [Notice] Read configuration file
"/home/waqas/.vidalia/torrc". Oct 18 02:15:06.937 [Notice] We were
compiled with headers from version 2.0.19-stable of Libevent, but
we're using a Libevent library that says it's version 2.0.21-stable.
Oct 18 02:15:06.938 [Notice] Initialized libevent version
2.0.21-stable using method epoll (with changelist). Good. Oct 18 02:15:06.938 [Notice] Opening Socks listener on 127.0.0.1:9050 Oct 18
02:15:06.938 [Warning] Could not bind to 127.0.0.1:9050: Address
already in use. Is Tor already running? Oct 18 02:15:06.938 [Warning]
/var/run/tor is not owned by this user (waqas, 1000) but by debian-tor
(118). Perhaps you are running Tor as the wrong user? Oct 18
02:15:06.938 [Warning] Before Tor can create a control socket in
"/var/run/tor/control", the directory "/var/run/tor" needs to exist,
and to be accessible only by the user account that is running Tor.
(On some Unix systems, anybody who can list a socket can connect to
it, so Tor is being careful.) Oct 18 02:15:06.938 [Warning] Failed to
parse/validate config: Failed to bind one of the listener ports. Oct
18 02:15:06.938 [Error] Reading config failed--see warnings above.
Please Help !