[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Some of my observations on runing new alpha version of Tor



Ok first i will attempt to translatie the complete error message:
Event type: Error
Event source: Service Control Manager
Event category:    None
Event Id:        7023
Date:           2007-06-10
Time:                13:12:46
User:             None
Computer:       xxx
Description:
Service "Tor Win 32 Service" terminated, following error occured:
In the service occured an exception during access control demand.
--
im not sure if the translation of the description field is clear
enough and completly correct
now for the rest
first of all i didnt notice the problem with stable bundle when
creating the service thru vidalia.
as it turned out vidalia creates the service somewhat different than
tor when called from commandline
Vidalia creates service with current user credentials?
not completly sure bout that, but when you inspect the service (then
go to login tab it states that the service runs with credentials of
local system account (upper option checked)
when creating the service with Tor from comand line the lower option
is selected and account data for LocalService is present
one more thing that is different is that when creating the service
with following command line >tor.exe --service install -options -f
c:\torrc ControlPort 9051 all options are surrounded with "" ie
service path looks something like this "C:\Program Files\Tor\tor.exe"
--nt-service "-f" "c:\torrc" "ControlPort" "9051" when created with
vidalia it looks like this
"C:\Program Files\Tor\tor.exe" --nt-service -f c:\torrc ControlPort 9051
but i'm not sure if this is critical (no logs from tor when i try to
start it with this tor service call)
just the log entry i mentioned earlier
next try installing the service without -options and placing torrc in
localservice application data tor directory with with my version ow
windows is
C:\Documents and Settings\LocalService\Dane aplikacji\tor
tor service installed with following command: C:\Program Files\Tor>tor
--service install
Running on a Post-Win2K OS, so we'll assume that the LocalService account exist
s.
IMPORTANT NOTE:
   The Tor service will run under the account "NT AUTHORITY\LocalService".  Th
is means
   that Tor will look for its configuration file under that
   account's Application Data directory, which is probably not
   the same as yours.
Done with CreateService.
Service installed successfully
Service failed to start : W us│udze wyst╣pi│ wyj╣tek podczas obs│ugi ┐╣dania ko
ntroli.
Thats all what i get in commandline window servicepath is as follows
"C:\Program Files\Tor\tor.exe" --nt-service login credentials of localservice
in system log are 3 entries about
1. succesfull start signal sent to process
2. service entering stopped state
3 previously mentioned error

here are contents of my torrc file that caused the error)
---
SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
Log debug file C:\Documents and Settings\LocalService\Tor.log.txt
ControlPort 9051
Nickname popo-test
---
contents of logile after the service failed none the logfile is not even created
when i remove Nickname line everything starts normally no error
messages and logfile looks as follows
--
Jun 13 20:48:42.046 [notice] Tor 0.1.2.14 opening new log file.
Jun 13 20:48:42.046 [debug] parse_dir_server_line(): Trusted dirserver
at 128.31.0.34:9031 (46DB)
Jun 13 20:48:42.046 [debug] parse_dir_server_line(): Trusted dirserver
at 128.31.0.34:9032 (E45D)
Jun 13 20:48:42.046 [debug] parse_dir_server_line(): Trusted dirserver
at 86.59.21.38:80 (1F85)
Jun 13 20:48:42.046 [debug] parse_dir_server_line(): Trusted dirserver
at 140.247.60.64:80 (F5FC)
Jun 13 20:48:42.046 [debug] parse_dir_server_line(): Trusted dirserver
at 194.109.206.212:80 (EAD6)
Jun 13 20:48:42.046 [info] or_state_load(): Loaded state from
"C:\Documents and Settings\LocalService\Dane aplikacji\tor/state"
Jun 13 20:48:42.484 [info] tor_mmap_file(): Couldn't mmap file
"C:\Documents and Settings\LocalService\Dane
aplikacji\tor/cached-routers": File not found
Jun 13 20:48:42.484 [info] update_router_have_minimum_dir_info(): We
have 0 of 5 network statuses, and we want more than 2.
Jun 13 20:48:42.484 [notice] I learned some more directory
information, but not enough to build a circuit.
Jun 13 20:48:42.484 [info]
update_router_descriptor_client_downloads(): Not enough networkstatus
documents to launch requests.
Jun 13 20:48:42.484 [info]
update_router_descriptor_client_downloads(): Not enough networkstatus
documents to launch requests.
Jun 13 20:48:42.484 [info] update_networkstatus_client_downloads():
For 5/5 running directory servers, we have 0 live network-status
documents. Downloading 5.
Jun 13 20:48:42.484 [info] router_pick_directory_server(): No
reachable router entries for dirservers. Trying them all again.
Jun 13 20:48:42.484 [info] router_pick_directory_server(): Still no
reachable router entries. Reloading and trying again.
Jun 13 20:48:42.484 [info] tor_mmap_file(): Couldn't mmap file
"C:\Documents and Settings\LocalService\Dane
aplikacji\tor/cached-routers": File not found
Jun 13 20:48:42.484 [info] directory_get_from_dirserver(): No router
found for network status; falling back to dirserver list
Jun 13 20:48:42.484 [debug] directory_initiate_command(): private 0,
want_to_tunnel 0.
Jun 13 20:48:42.484 [debug] directory_initiate_command(): initiating
network-status fetch
Jun 13 20:48:42.484 [debug] connection_connect(): Connecting to [scrubbed]:80.
Jun 13 20:48:42.484 [debug] connection_connect(): Connection to
[scrubbed]:80 in progress (sock 396).
Jun 13 20:48:42.484 [debug] connection_add(): new conn type Directory,
socket 396, n_conns 3.
Jun 13 20:48:42.484 [debug] write_to_buf(): added 4 bytes to buf (now 4 total).
Jun 13 20:48:42.484 [debug] write_to_buf(): added 221 bytes to buf
(now 225 total).
Jun 13 20:48:42.484 [debug] write_to_buf(): added 34 bytes to buf (now
259 total).
Jun 13 20:48:42.484 [info] update_router_have_minimum_dir_info(): We
have 0 of 5 network statuses, and we want more than 2.
Jun 13 20:48:42.484 [info] or_state_save(): Saved state to
"C:\Documents and Settings\LocalService\Dane aplikacji\tor/state"
Jun 13 20:48:42.484 [debug] conn_read_callback(): socket 212 wants to read.
Jun 13 20:48:42.484 [debug] connection_handle_listener_read():
Connection accepted on socket 408 (child of fd 212).
Jun 13 20:48:42.484 [debug] connection_add(): new conn type Socks,
socket 408, n_conns 4.
...
Jun 13 20:48:59.390 [notice] Got stop/shutdown request; shutting down cleanly.
Jun 13 20:48:59.484 [debug] global_read_bucket now 6291456.
Jun 13 20:48:59.500 [info] or_state_save(): Saved state to
"C:\Documents and Settings\LocalService\Dane aplikacji\tor/state"
--
if its ok next time i will just attach a file with logdump
if Tor runs as a client everything works ok but if i enable anything
server related tor dies before even being able to write something into
logfile (not only serrver but dns tordns server port causes the same
(functionality that is firs avaiable in this version of Tor)

Today i checked latest stable vidalia bundle but with Tor service
created from commandline same results as with alpha

Tomorow I will try to get some archival versions and test them (i
usually used vidalia sience its there, and had quite long pause with
(over one year without Tor installed) but i will try to determine if
older versions have same problem on my system
0.1.2.14 - error
0.1.0.17 - error (no mather what credentials will not run as service)
I will test other versions as soon as i have some free time and report
with results

2007/6/11, phobos@xxxxxxxxxx <phobos@xxxxxxxxxx>:
On Sun, Jun 10, 2007 at 08:15:26PM +0200, porzech@xxxxxxxxx wrote 2.2K bytes in 30 lines about:

       First, is this behavior the same as a previous version of Tor?

: Usługa Tor Win32 Service zakończyła działanie; wystąpił następujący
: błąd:
: W usłudze wystąpił wyjątek podczas obsługi żądania kontroli.

       Can you translate this to English?

: -----------------
: I then started to change things in torrc and figured out that enabling
: any options related to Tor server functions triggers this error

       Do you have the output from Tor as to what it doesn't like about
       the config?


--
Andrew