Hi all,
I'm trying to set up a Tor bridge relay as an NT service under Windows 2003 x64. It runs, but only when I -don't- pass it a torrc file.
Specifically, I've tried the following: 1. Installed service using "tor --service install". This installed the Tor service, with files located in "C:\Documents and Settings\LocalService\tor". I copied a torrc file into this directory and edited it to correctly set the ports and other options to be a bridge relay. After placing this file into the directory, attempting to start the service results in error 1064: an exception occurred in the service when handling the control request. Renaming or removing the torrc file allows the service to start.
2. After reading some old posts to tor-talk and tor-relays, I ensured that the directory has full permissions assigned to SERVICE and LOCAL SERVICE accounts. No change.
3. I removed the service and created a new directory for the configuration and log files, located at "C:\torsvc". I installed the service again with "tor --service install -option -f "C:\torsvc\torrc". I also ensured the new directory had all permissions set correctly. The service installed as "tor -net-service" without any options and executed successfully. I stopped the service and fixed the path in the registry to include "-f "C:\torsvc\torrc"", but then the service wouldn't start any more.
4. I verified the permissions on the torsvc directory. After removing the -f option from the service, the service starts successfully again, albeit without my configs (including log locations which would tell me what was going wrong).
Sorry to be a bother, but could anybody offer me some enlightenment on what I'm missing???
-Lance
On 23/11/2012 9:46 PM, Lance Hathaway wrote:
Sorry to be a bother, but could anybody offer me some enlightenment on what I'm missing???
Never mind, I figured it out. Apparently I had an invalid character in my Nickname, which caused Tor to dump itself without writing any sort of info to the configured log file. Looks good now.
-Lance
On 24.11.2012 17:28, Lance Hathaway wrote:
Never mind, I figured it out. Apparently I had an invalid character in my Nickname, which caused Tor to dump itself without writing any sort of info to the configured log file. Looks good now.
What kind of character did you use? Sounds like a good bug report.
I used a dash. Something to logically separate two parts of the nickname without requiring a space, you know. Of course, had I not been configuring it at close to midnight, I probably would have noticed that the manual says it must be alphanumeric only. Because it's written down as such in the manual, I'm not sure it can be properly classified as a bug.
The only really frustrating part was that nothing was written to the log file. When I woke up the next morning and fiddled with it a bit more, I realized that I could try running Tor through my local account and reference the suspect torrc file. When I did, it happily printed out the equivalent of "you didn't read the manual, dummy!" to stdout and quit right back to the command line. That led me to fixing the problem statement, and hence my the crashes.
I'd love to see Tor write all errors to the configured log file, including errors with the torrc file. And if logging isn't configured or is misconfigured, it might be appropriate to spit something into the default logging for the system (Windows Events, /var/log/messages, etc.). But for now, I'm willing to accept a resolution of "read the fancy manual."
-Lance
On 25/11/2012 3:46 AM, Moritz Bartl wrote:
On 24.11.2012 17:28, Lance Hathaway wrote:
Never mind, I figured it out. Apparently I had an invalid character in my Nickname, which caused Tor to dump itself without writing any sort of info to the configured log file. Looks good now.
What kind of character did you use? Sounds like a good bug report.
tor-relays@lists.torproject.org
-
Lance Hathaway -
Moritz Bartl