The basic deck does not run properly under vagrant
At 2013-09-12 10:22:11 Arturo Filastò wrote: A user reported that when installing ooni-probe in Vagrant and running the basic deck they experience this issue:
Log opened.
[!] pypcap or dnet not installed. Certain tests may not work.
.
Sent 1 packets.
Starting Tor...
[D] Setting control port as 8802
[D] Setting SOCKS port as 8801
[D] Checking if backend is present
unexpected error in processEnded
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/twisted/internet/abstract.py", line 304, in readConnectionLost
self.connectionLost(reason)
File "/usr/local/lib/python2.7/dist-packages/twisted/internet/process.py", line 275, in connectionLost
self.proc.childConnectionLost(self.name, reason)
File "/usr/local/lib/python2.7/dist-packages/twisted/internet/process.py", line 899, in childConnectionLost
self.maybeCallProcessEnded()
File "/usr/local/lib/python2.7/dist-packages/twisted/internet/process.py", line 912, in maybeCallProcessEnded
_BaseProcess.maybeCallProcessEnded(self)
--- <exception caught here> ---
File "/usr/local/lib/python2.7/dist-packages/twisted/internet/_baseprocess.py", line 60, in maybeCallProcessEnded
proto.processEnded(Failure(reason))
File "/usr/local/lib/python2.7/dist-packages/txtorcon/torconfig.py", line 348, in processEnded
raise RuntimeError('\n'.join(self.stdout) + "\n\nTor exited with error-code %d" % status.value.exitCode)
exceptions.RuntimeError: Sep 12 10:02:19.158 [notice] Tor v0.2.3.25 (git-3fed5eb096d2d187) running on Linux.
Sep 12 10:02:19.158 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Sep 12 10:02:19.158 [notice] Read configuration file "/tmp/tortmpLQMTyT".
Sep 12 10:02:19.159 [notice] Initialized libevent version 2.0.16-stable using method epoll (with changelist). Good.
Sep 12 10:02:19.159 [notice] Opening Socks listener on 127.0.0.1:8801
Sep 12 10:02:19.160 [warn] Could not bind to 127.0.0.1:8801: Address already in use. Is Tor already running?
Sep 12 10:02:19.160 [notice] Opening Control listener on 127.0.0.1:8802
Sep 12 10:02:19.160 [warn] Could not bind to 127.0.0.1:8802: Address already in use. Is Tor already running?
Sep 12 10:02:19.160 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Sep 12 10:02:19.160 [err] Reading config failed--see warnings above.
Tor exited with error-code 255
This seems to be related to the fact that Tor has already binded to that port or that some tor process stays still running, because after doing killall -9 tor
the application starts properly.
This bug was reported by lehoax.
This issue was automatically migrated from github issue https://github.com/TheTorProject/ooni-probe/issues/194