On Friday 24 July 2009 13:03:57 DM wrote: > Look at the line in the config file containing the Socks listener > entry and see if you added an extra character after the port number. > This is what I have, unaltered from the original sample file:
## Replace this with "SocksPort 0" if you plan to run Tor only as a ## server, and not make any local application connections yourself. SocksPort 9050 # what port to open for local application connections SocksListenAddress 127.0.0.1 # accept connections only from localhost #SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also > On Jul 24, 2009, at 7:58 AM, Bob Williams wrote: > > On Friday 24 July 2009 12:47:41 Christian Fromme wrote: > >> Hi, > >> > >> On Fri, Jul 24, 2009 at 1:44 PM, Bob > >> > >> Williams<[email protected]> wrote: > >>> On Friday 24 July 2009 12:37:50 Christian Fromme wrote: > >>>> Can you restart Tor and see if that puts any messages in your > >>>> logfile? > >>>> If not, you seem to have changed some configuration settings in the > >>>> meantime, breaking it. > >>> > >>> Thanks. How do I restart Tor? I originally started it with > >>> > >>> ~> tor -f /etc/tor/torrc > >>> > >>> but when I rerun that command, I get > >>> > >>> ~> tor -f /etc/tor/torrc > >>> Jul 24 12:41:40.393 [notice] Tor v0.2.0.35. This is experimental > >>> software. Do not rely on it for strong anonymity. (Running on Linux > >>> x86_64) > >>> Jul 24 12:41:40.393 [notice] Initialized libevent version 1.4.5- > >>> stable > >>> using method epoll. Good. > >>> Jul 24 12:41:40.393 [notice] Opening Socks listener on > >>> 127.0.0.1:9050 > >>> Jul 24 12:41:40.393 [warn] Could not bind to 127.0.0.1:9050: Address > >>> already in use. Is Tor already running? > >>> Jul 24 12:41:40.393 [warn] Failed to parse/validate config: Failed > >>> to > >>> bind one of the listener ports. > >>> Jul 24 12:41:40.393 [err] Reading config failed--see warnings above. > >>> > >>> How do stop and restart tor? > >> > >> The way you use, you restart it by: > >> > >> ~> killall tor > >> ~> tor -f /etc/tor/torrc > > > > Of course! Thank you. Unfortunately, I get the same result > > > > 12:53 barrowhillfarm:~> killall tor > > 12:53 barrowhillfarm:~> tor -f /etc/tor/torrc > > Jul 24 12:54:15.469 [notice] Tor v0.2.0.35. This is experimental > > software. Do > > not rely on it for strong anonymity. (Running on Linux x86_64) > > Jul 24 12:54:15.470 [notice] Initialized libevent version 1.4.5- > > stable using > > method epoll. Good. > > Jul 24 12:54:15.470 [notice] Opening Socks listener on 127.0.0.1:9050 > > Jul 24 12:54:15.470 [warn] Could not bind to 127.0.0.1:9050: Address > > already > > in use. Is Tor already running? > > Jul 24 12:54:15.470 [warn] Failed to parse/validate config: Failed > > to bind one > > of the listener ports. > > Jul 24 12:54:15.470 [err] Reading config failed--see warnings above. > > 12:54 barrowhillfarm:~> > > > > I know there is nothing else trying to use port 9050 as /etc/ > > services says so: > > > > # 9027-9079 Unassigned > > > > What next? > > -- > > Bob -- Bob
