Opened 10 years ago

Last modified 7 years ago

#1112 closed defect (Won't fix)

Tor can´t open directory

Reported by: h Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.1.19
Severity: Keywords:
Cc: h, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

After I installed Tor it ran. (I wanted to create a bridge, as requested in the blog ). After restarted the computer,
it doesn´t work. The message protocol says :

Okt 03 00:35:24.218 [Warnung] Error creating directory "C:
Dokumente und Einstellungen
*\366rg
Anwendungsdaten
tor": Invalid argument
Okt 03 00:35:24.218 [Warnung] Failed to parse/validate config: Couldn't access/create private data directory ""C:
Dokumente und Einstellungen
*\366rg
Anwendungsdaten
tor""
Okt 03 00:35:24.218 [Fehler] Reading config failed--see warnings above.

Im not the only one, this question I found, but it wasn´t solved:

http://www.multimediaxis.de/showthread.php?t=119538

Also other directorys I can´t open to write since then.

But I´ll wait for an answer, before I try to deinstall tor.

MfG h

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Change History (6)

comment:1 Changed 10 years ago by nickm

Hm. What is the DataDirectory line in your torrc file?

Are you editing the torrc file by hand, or are you running a controller program?

What version of Windows are you running, exactly?

[The extra quotation marks make me think that you or a controller program has possibly put unnecessary quotation
marks in the DataDirectory line. The DataDirectory line does not need quotation marks in order to have spaces in the
file name.

comment:2 Changed 10 years ago by h

1 I don´t know, this is the torrc file:

# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it

BridgeRelay 1
# If set, Tor will accept connections from the same machine (localhost only)
# on this port, and allow those connections to control the Tor process using
# the Tor Control Protocol (described in control-spec.txt).
ControlPort 9051
# Serve directory information from this port, and act as a directory cache.
DirPort 9030
# Address/port ranges for which to accept or reject outgoing connections on
# behalf of Tor users.
ExitPolicy reject *:*
HashedControlPassword 16:*
# Where to send logging messages. Format is minSeverity[-maxSeverity]
# (stderr|stdout|syslog|file FILENAME).
Log notice stdout
# Set the server nickname.
Nickname Hugo
# Advertise this port to listen for connections from Tor clients and servers.
ORPort 443
RelayBandwidthBurst 30720
RelayBandwidthRate 20480
# Bind to this address to listen to connections from SOCKS-speaking
# applications.
SocksListenAddress 127.0.0.1

2 No, I use Vidalia

3 XP SP3

comment:3 Changed 10 years ago by h

The problem is a non ASCII-Character in the data directory path :

https://trac.vidalia-project.net/ticket/354

It´s not solved.

So I have to change the path on each start by hand.

H

comment:4 Changed 10 years ago by Sebastian

I just started Tor giving a path with an Umlaut in the torrc location (via tor.exe -f), and the torrc file contained a datadirectory entry with an umlaut as well. I think that's probably a Vidalia bug, not Tor

comment:5 Changed 10 years ago by phobos

flyspray2trac: bug closed.
This is a vidalia bug, as seen in the comments. Closing here, as the bug is already reported there.

comment:6 Changed 7 years ago by nickm

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