[tor-relays] TOR service wont start with ORPort enabled

[SuperSluether]

Try running "sudo lsof -i :9001"

That should tell you what process is bound to the port, and also give 
you the PID so you can kill it.

On 02/14/2016 07:10 AM, Volker Mink wrote:
> I think I found something.....
>
>>> could not bind to 0.0.0.0:9001: address already in use
> Where can i set the binding?
>
> Feb 14 14:04:59 raspberrypi tor[499]: Starting tor daemon...Feb 14
> 14:04:59.318 [warn] Could not bind to 0.0.0.0:9001: Address already in use.
> Is Tor already running?
> Feb 14 14:04:59 raspberrypi tor[499]: Feb 14 14:04:59.324 [warn] Failed to
> parse/validate config: Failed to bind one of the listener ports.
> Feb 14 14:04:59 raspberrypi systemd[1]: tor.service: control process exited,
> code=exited status=1
> Feb 14 14:04:59 raspberrypi tor[499]: Feb 14 14:04:59.328 [err] Reading
> config failed--see warnings above.
> Feb 14 14:04:59 raspberrypi tor[499]: failed.
> Feb 14 14:04:59 raspberrypi systemd[1]: Failed to start LSB: Starts The
> Onion Router daemon processes.
> Feb 14 14:04:59 raspberrypi systemd[1]: Unit tor.service entered failed
> state.
> Feb 14 14:04:59 raspberrypi systemd[1]: Starting Multi-User System.
> Feb 14 14:04:59 raspberrypi systemd[1]: Reached target Multi-User System.
> Feb 14 14:04:59 raspberrypi systemd[1]: Starting Graphical Interface.
> Feb 14 14:04:59 raspberrypi systemd[1]: Reached target Graphical Interface.
> Feb 14 14:04:59 raspberrypi systemd[1]: Starting Update UTMP about System
> Runlevel Changes...
> Feb 14 14:04:59 raspberrypi systemd[1]: Started Update UTMP about System
> Runlevel Changes.
> Feb 14 14:04:59 raspberrypi systemd[1]: Startup finished in 2.206s (kernel)
> + 22.232s (userspace) = 24.439s.
> Feb 14 14:05:04 raspberrypi dhcpcd[496]: eth0: no IPv6 Routers available
> Feb 14 14:05:14 raspberrypi systemd[1]: Time has been changed
> Feb 14 14:07:15 raspberrypi systemd[1]: Starting LSB: Starts The Onion
> Router daemon processes...
> Feb 14 14:07:16 raspberrypi tor[586]: Starting tor daemon...Feb 14
> 14:07:16.092 [warn] Could not bind to 0.0.0.0:9001: Address already in use.
> Is Tor already running?
> Feb 14 14:07:16 raspberrypi tor[586]: Feb 14 14:07:16.098 [warn] Failed to
> parse/validate config: Failed to bind one of the listener ports.
> Feb 14 14:07:16 raspberrypi systemd[1]: tor.service: control process exited,
> code=exited status=1
> Feb 14 14:07:16 raspberrypi tor[586]: Feb 14 14:07:16.103 [err] Reading
> config failed--see warnings above.
> Feb 14 14:07:16 raspberrypi systemd[1]: Failed to start LSB: Starts The
> Onion Router daemon processes.
> Feb 14 14:07:16 raspberrypi systemd[1]: Unit tor.service entered failed
> state.
> Feb 14 14:07:16 raspberrypi tor[586]: failed.
>
>
>> On 14 Feb 2016, at 23:05, Volker Mink <volker.mink at gmx.de> wrote:
>>
>> Hey there.
>>
>> I recently updated my working TOR Exit from Raspian Wheezy to Jessie and
> also updatet my TOR-Version.
>> Now I got the problem, that the TOR-service wont start when I have the
> ORPort in the torrc-file enabled.
>> Port 9001 is forwarded at my router and the Pi is also in the DMZ.
> Can you please send us the Tor log messages?
> They usually say why Tor won't start.
>
> Tim
>
> Tim Wilson-Brown (teor)
>
> teor2345 at gmail dot com
> PGP 968F094B
>
> teor at blah dot im
> OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.torproject.org/pipermail/tor-relays/attachments/20160214/f4484
> b90/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 842 bytes
> Desc: Message signed with OpenPGP using GPGMail
> URL:
> <http://lists.torproject.org/pipermail/tor-relays/attachments/20160214/f4484
> b90/attachment.sig>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> ------------------------------
>
> End of tor-relays Digest, Vol 61, Issue 12
> ******************************************
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160214/2f2d9a3b/attachment-0001.html>