Hey Volker, Could you try to issue a "netstat -tulpn" on the server and post your output (anonymized) here? It seems that there is something (else) running on 9001.
Yours faithfully, Andre Mankel [email protected] I'm not quite sure but could that correlate with this one [1]? Ken says Port 9001 is still allocated to the old process when restarting. [1] [email protected] https://lists.torproject.org/pipermail/tor-talk/2016-February/040271.html ----- Original Message ----- From: Volker Mink [mailto:[email protected]] Received-SPF: none (no valid SPF record) Sent: Mon 15. Feb. 2016 10:03:20 PM +0100 CET To: [email protected] Subject: Re: [tor-relays] TOR service wont start with ORPort enabled > Hi ! > > Nope, that was my first idea. No old TOR process running. > > Best, > volker > >> On 15 Feb 2016, at 00:10, Volker Mink <[email protected]> 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? > > Is your old Tor process still running? > > Tim > > Tim Wilson-Brown (teor) > > teor2345 at gmail dot com > PGP 968F094B > > teor at blah dot im > OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F _______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
