Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#4336 closed defect (fixed)

Updated Tor crashes on Win7/x86_64

Reported by: tmpname0901 Owned by:
Priority: High Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: karsten, erinn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (8)

comment:1 Changed 8 years ago by nickm

Milestone: Tor: 0.2.2.x-final

comment:2 Changed 8 years ago by Sebastian

Status: newneeds_information

Hi, and many thanks for reporting this! Can you see in your message log if you see any message like "Configured to measure directory request statistics, but no GeoIP database found!"? If so, that would be very helpful to know!

Thanks!

comment:3 Changed 8 years ago by Sebastian

Cc: karsten erinn added

Ah yes. I think that's it. When you install tor as a different user, our current packages have issues with the path and don't load the geoip file correctly. This caused the #4340 crash. We should also try harder making geoip available to all users when installed in this way...

comment:4 Changed 8 years ago by tmpname0901

Yep, the lack of geoip was the problem. I copied from file from the admin account to the user account and all appears to be well.

Now that I knew what to look for, I noticed that the lack of geoip was noted in the message log from the prior run of Tor, but early in the bootstrap process and marked Notice. Because it was not a Warning and because the bootstrap seemed to be successful, the notice was easy to overlook.

Off-topic request: if you're going to do another spin of Tor to fix this, could you build it with the current libevent? Version 2.0.15 was released over 2 weeks ago (the graphic on their website notwithstanding). Thanks.

comment:5 Changed 8 years ago by Sebastian

glad to hear this is fixed for you (and it will be fixed with the next release for everyone, whether they have a geoip file or not). I'm keeping this bug open until we've filed stuff for the other issues/identified them better.

comment:6 in reply to:  5 Changed 8 years ago by rransom

Resolution: fixed
Status: needs_informationclosed

Replying to Sebastian:

glad to hear this is fixed for you (and it will be fixed with the next release for everyone, whether they have a geoip file or not). I'm keeping this bug open until we've filed stuff for the other issues/identified them better.

  • #4635 is ‘Vidalia Bundles for Windows don't install system-wide and should’. (We may have had other tickets for that already.)
  • #4374 and #4347 cover ‘Tor in Vidalia Bundle for Windows can't find its geoip file’.

comment:7 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:8 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.