Opened 4 years ago

Last modified 14 months ago

#17145 new defect

<tor.exe --service install -options -f ...\torrc> returns Error 1064 on Windows

Reported by: TORques Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7.2-alpha
Severity: Normal Keywords: windows, win32, nt-service, tor-relay, 033-triage-20180320, 033-removed-20180320, 031-unreached-backport
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

tor --service install -options -f C:\tor\torrc

from https://www.torproject.org/docs/faq#NTService failed to start the service (Error 1064: An exception occured in the service when handling the control request).

But other options works:

tor.exe --service install -options ControlPort 9051

start the Tor Win32 Service and creates the folder C:\Documents and Settings\LocalService\Application Data\tor - tor.exe works like a client only (no disk torrc file, no relay keys). This is useless because i can't use my torrc and run the relay.

The only way to create a running tor service for a relay is to use the "sc create..." in cmd command line as irc#tor<coderman_> suggested. So this is how it works:

sc create "Tor Win32 Service" binPath= "\"C:\tornou\Tor\tor.exe\" --nt-service -f \"C:/tornou/Data/Tor/torrc\""

returns ImagePath="C:\tornou\Tor\tor.exe" --nt-service -f "C:/tornou/Data/Tor/torrc" and the service is running.

From this point of view, if nobody will fix the related bug, the https://www.torproject.org/docs/faq#NTService may be updated with this "sc create... working option".

Regards,
torQUES

Child Tickets

Change History (12)

comment:1 Changed 2 years ago by nickm

Keywords: windows win32 nt-service tor-relay added
Severity: Normal

comment:2 Changed 21 months ago by Cisif

Same here!
Windows 10 x86, Expert-Bundle-0.3.1.7

comment:3 Changed 21 months ago by cypherpunks

Summary: <tor.exe --service install -options -f ...\torrc> returns Error 1064 in Win32 XP<tor.exe --service install -options -f ...\torrc> returns Error 1064 on Windows

Are you running a relay?
Why x86?
Why not 0.3.1.8?

comment:4 in reply to:  3 Changed 21 months ago by Cisif

Replying to cypherpunks:

Are you running a relay?
Why x86?
Why not 0.3.1.8?

  • No, that's the office PC that need access for some sites (anonymity is not the goal).
  • Long story (old hardware, absence of x64 drivers, etc).
  • Have just tried 0.3.1.8 - same problem.
Version 1, edited 21 months ago by Cisif (previous) (next) (diff)

comment:5 Changed 21 months ago by nickm

Keywords: 031-backport added
Milestone: Tor: unspecifiedTor: 0.3.2.x-final

comment:6 Changed 21 months ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

comment:7 Changed 21 months ago by cypherpunks

  1. Make a new shortcut to "cmd.exe" (no ") on your desktop.
  2. Right-click it and "run as admin".
  3. Type "X:/Tor/tor.exe --service install -options -f X:/Tor/tordata/torrc" (no ").

comment:8 in reply to:  7 Changed 21 months ago by Cisif

Replying to cypherpunks:

  1. Make a new shortcut to "cmd.exe" (no ") on your desktop.
  2. Right-click it and "run as admin".
  3. Type "X:/Tor/tor.exe --service install -options -f X:/Tor/tordata/torrc" (no ").

Same error (1064).

Last edited 21 months ago by Cisif (previous) (diff)

comment:9 Changed 17 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:10 Changed 17 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:11 Changed 17 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: unspecified

These tickets were marked as removed, and nobody has said that they can fix them. Let's remember to look at 033-removed-20180320 as we re-evaluate our triage process, to see whether we're triaging out unnecessarily, and to evaluate whether we're deferring anything unnecessarily. But for now, we can't do these: we need to fix the 033-must stuff now.

comment:12 Changed 14 months ago by teor

Keywords: 031-unreached-backport added; 031-backport removed

0.3.1 is end of life, there are no more backports.
Tagging with 031-unreached-backport instead.

Note: See TracTickets for help on using tickets.