GitLab

I usually run Tor in a Win7 user account and have been running a 0.2.2.33 relay without any problems. Now the updated 0.2.2.34 Tor crashes after running for about a minute.

To upgrade I shut down the running 0.2.2.33 relay and switched to the system's admin account. I uninstalled the existing Vidalia Bundle and installed vidalia-relay-bundle-0.2.2.34-0.2.15.exe.

I switched back to the user account and ran Vidalia, using the existing Tor and Vidalia config files. First problem: Vidalia can't find the Tor executable because the installation location has changed. I pointed Vidalia to the correct location.

I started Tor via the Vidalia Control Panel and all appeared to be well. Watching the message log I saw the the self-test worked correctly, my bandwidth had been measured, and that my descriptor had been published. Easy-peasy.

After running for about 60-90 seconds a pop-up window appears on my desktop saying that Vidalia is reporting that Tor had exited unexpectedly. I looked at the message log and see no problems whatsoever in the Advanced log screen. The last entry is a notification of start-up success.

I try starting Tor again and again all appears to be well. And again I am informed after 60-90 seconds that Tor has "exited unexpectedly".

Maybe it can't find my pre-existing torrc config file? No, The relay name is correctly shown in the message log. Maybe it can't find my data files? No, I see that the time stamp on the "state" file is updated when I start Tor. (Although the timestamp on the cached descriptor files seems not to change.)

So now I am unable to run the relay that has worked so well for months.

Trac:
Username: tmpname0901