sudo update-rc.d -f tor remove
sudo update-rc.d -f polipo remove
/etc/init.d/polipo stop
/etc/init.d/tor stop
Tor Exited Unexpectedly If Tor exits immediately after trying to start, you most likely have another Tor process already running. Check the message log to see if any of the last few messages in the list are highlighted in yellow and contain a message similar to the following: connection_create_listener(): Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?If you find an error message like the one above, you will need to stop the other Tor process before starting a new one with Vidalia. On Windows, you would need to look for tor.exe in your Task Manager. On most other operating systems, the ps command can help you find the other Tor process. If Tor had been running successfully for awhile (that is, longer than a few seconds), then you should check the message log for information about any errors Tor experienced before it exited. Such errors will be highlighted in either red or yellow.