More info on my own tor problems - Fixed? NOT

Fri Dec 5 17:28:39 UTC 2008

Tor 0.2.1.7 just died on me with a message about a dns failure and now I 
cannot restart it.  No error messages (in Tork).  Firing up vidalia...I get 
this AGAIN:

Dec 05 12:27:41.833 [Notice] Tor v0.2.1.7-alpha (r17216). This is experimental 
software. Do not rely on it for strong anonymity. (Running on Linux i686)
Dec 05 12:27:41.847 [Warning] Linelist option '__HashedControlSessionPassword' 
has no value. Skipping.
Dec 05 12:27:41.849 [Warning] Skipping obsolete configuration option 'Group'
Dec 05 12:27:41.850 [Warning] ControlPort is open, but no authentication 
method has been configured.  This means that any program on your computer can 
reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as 
soon as possible.
Dec 05 12:27:41.851 [Notice] Initialized libevent version 1.4.7-stable using 
method epoll. Good.
Dec 05 12:27:41.852 [Notice] Opening OR listener on 0.0.0.0:9001
Dec 05 12:27:41.854 [Notice] Opening Directory listener on 0.0.0.0:9030
Dec 05 12:27:41.855 [Notice] Opening Socks listener on 127.0.0.1:9050
Dec 05 12:27:41.856 [Notice] Opening Control listener on 127.0.0.1:9051
Dec 05 12:27:41.857 [Warning] Error setting configured groups: Operation not 
permitted
Dec 05 12:27:41.859 [Warning] Failed to parse/validate config: Problem with 
User value. See logs for details.
Dec 05 12:27:41.860 [Error] Reading config failed--see warnings above.

Back to 0.2.0.31 or so.  Tor-0.2.1.7-alpha IS broken.

praedor

On Friday 05 December 2008 08:42:30 Praedor Atrebates wrote:
> For the second day now I have been successful (finally) at operating
> tor-0.2.1.7-alpha via Tork (0.29.2).
>
> The "fix" for me was to manually edit the torrc.sample and save it as torrc
> in /etc/tor and then search out any and all other torrc files on my system
> and link them all to the base torrc I placed in /etc/tor.  After doing
> this, I was still unable to start tor so I deleted my ~/.tor directory and
> tried again by starting it from the CLI.  This did get tor started and it
> ran for a while until I killed it.  I was then able to start tor from Tork
> and it remained stable.  This morning I started it again from Tork and it
> is (so far) still operating.
>
> Up to this point, neither Tork nor Vidalia was able to configure or run
> tor.
>
> praedor
>
> On Thursday 04 December 2008 08:25:26 Praedor Atrebates wrote:
> > Forgot to add:  I saw the "unable to open /etc/tor/torrc" message and
> > fixed that and tried again.  I get essentially the same messages except
> > lacking the above statement:
> >
> > Dec 04 08:13:34.430 [Notice] Tor v0.2.1.7-alpha (r17216). This is
> > experimental software. Do not rely on it for strong anonymity. (Running
> > on Linux i686) Dec 04 08:13:34.431 [Warning] Linelist option
> > '__HashedControlSessionPassword' has no value. Skipping.
> > Dec 04 08:13:34.432 [Warning] Skipping obsolete configuration option
> > 'Group' Dec 04 08:13:34.432 [Warning] ControlPort is open, but no
> > authentication method has been configured.  This means that any program
> > on your computer can reconfigure your Tor.  That's bad!  You should
> > upgrade your Tor controller as soon as possible.
> > Dec 04 08:13:34.433 [Notice] Initialized libevent version 1.4.7-stable
> > using method epoll. Good.
> > Dec 04 08:13:34.433 [Notice] Opening OR listener on 0.0.0.0:9001
> > Dec 04 08:13:34.434 [Notice] Opening Socks listener on 127.0.0.1:9050
> > Dec 04 08:13:34.434 [Notice] Opening Control listener on 127.0.0.1:9051
> > Dec 04 08:13:34.434 [Warning] Error setting configured groups: Operation
> > not permitted
> > Dec 04 08:13:34.435 [Warning] Failed to parse/validate config: Problem
> > with User value. See logs for details.
> > Dec 04 08:13:34.435 [Error] Reading config failed--see warnings above.
> >
> > On Thursday 04 December 2008 08:17:18 Praedor Atrebates wrote:
> > > I have had a long-running problem upgrading to tor-0.2.1.7-alpha.  I
> > > usually use Tork as my tor manager (version 0.29.2 rpm - I can't build
> > > the latest because I am using kde 4 and it wont build on such a system)
> > > and run the configuation wizard after every tor upgrade.  This has
> > > worked perfectly up until 0.2.1.7-alpha.
> > >
> > > The problem is that no matter what I do, be it configure tor via Tork
> > > or do it manually with a text editor, I cannot get tor to run.  It
> > > crashes very quickly and, from Tork, produces no useful log
> > > information.  It just stops.
> > >
> > > I have now tried with vidalia and I am still unable to run tor but I am
> > > getting useful log data:
> > >
> > > Dec 04 08:05:41.407 [Notice] Tor v0.2.1.7-alpha (r17216). This is
> > > experimental software. Do not rely on it for strong anonymity. (Running
> > > on Linux i686) Dec 04 08:05:41.409 [Warning] Unable to open
> > > configuration file "/etc/tor/torrc".
> > > Dec 04 08:05:41.410 [Error] Reading config failed--see warnings above.
> > > Dec 04 08:06:24.666 [Notice] Tor v0.2.1.7-alpha (r17216). This is
> > > experimental software. Do not rely on it for strong anonymity. (Running
> > > on Linux i686) Dec 04 08:06:24.669 [Warning] Skipping obsolete
> > > configuration option 'Group' Dec 04 08:06:24.673 [Notice] Initialized
> > > libevent version 1.4.7-stable using method epoll. Good.
> > > Dec 04 08:06:24.675 [Notice] Opening OR listener on 0.0.0.0:9001
> > > Dec 04 08:06:24.679 [Notice] Opening Socks listener on 127.0.0.1:9050
> > > Dec 04 08:06:24.682 [Notice] Opening Control listener on 127.0.0.1:9051
> > > Dec 04 08:06:24.686 [Warning] Error setting configured groups:
> > > Operation not permitted
> > > Dec 04 08:06:24.689 [Warning] Failed to parse/validate config: Problem
> > > with User value. See logs for details.
> > > Dec 04 08:06:24.693 [Error] Reading config failed--see warnings above.
> > >
> > >
> > > I have no idea what the problem is with the torrc file.  I merely took
> > > the sample provided with the software and uncommented the applicable
> > > parts (after Tork failed to configure it) and copy it to torrc.  What
> > > is the deal with tor-0.2.1.7?  What has changed vis a vis configuration
> > > that appears to break it compared to the any and all of the previous
> > > versions? Most important of all, how do I get past this so I can start
> > > running tor again?
> > >
> > > praedor