Your message dated Thu, 12 Oct 2006 21:39:54 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#392650: tor: installation exists with error
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: tor
Version: 0.1.1.24-1
Severity: grave
Justification: renders package unusable



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-scruffy
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages tor depends on:
ii  adduser                      3.97        Add and remove users and groups
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  libevent1                    1.1a-1      An asynchronous event notification
ii  libssl0.9.8                  0.9.8c-3    SSL shared libraries
ii  tsocks                       1.8beta5-2  transparent network access through
ii  zlib1g                       1:1.2.3-13  compression library - runtime

Versions of packages tor recommends:
ii  privoxy                     3.0.5-beta-1 Privacy enhancing HTTP Proxy
pn  socat                       <none>       (no description available)

-- no debconf information

I can't install tor. It exists with following error message:

Raising maximum number of filedescriptors (ulimit -n) to 8192.
Starting tor daemon: tor...
Oct 12 20:16:50.856 [notice] Tor v0.1.1.24. This is experimental 
software. Do not rely on it for strong anonymity.
Oct 12 20:16:50.857 [notice] Initialized libevent version 1.1a using 
method epoll. Good.
Oct 12 20:16:50.857 [notice] connection_create_listener(): Opening Socks 
listener on 127.0.0.1:9050
Oct 12 20:16:50.857 [warn] connection_create_listener(): Could not bind 
to 127.0.0.1:9050: Address already in use. Is Tor already running?
Oct 12 20:16:50.857 [warn] Failed to parse/validate config: Failed to 
bind one of the listener ports.
Oct 12 20:16:50.857 [err] tor_init(): Reading config failed--see 
warnings above. For usage, try -h.
invoke-rc.d: initscript tor, action "start" failed.
dpkg: error processing tor (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 tor
E: Sub-process /usr/bin/dpkg returned an error code (1)


--- End Message ---
--- Begin Message ---
Philip Frei schrieb am Donnerstag, dem 12. Oktober 2006:

> I can't install tor. It exists with following error message:
> 
> Raising maximum number of filedescriptors (ulimit -n) to 8192.
> Starting tor daemon: tor...
> Oct 12 20:16:50.856 [notice] Tor v0.1.1.24. This is experimental 
> software. Do not rely on it for strong anonymity.
> Oct 12 20:16:50.857 [notice] Initialized libevent version 1.1a using 
> method epoll. Good.
> Oct 12 20:16:50.857 [notice] connection_create_listener(): Opening Socks 
> listener on 127.0.0.1:9050
> Oct 12 20:16:50.857 [warn] connection_create_listener(): Could not bind 
> to 127.0.0.1:9050: Address already in use. Is Tor already running?
> Oct 12 20:16:50.857 [warn] Failed to parse/validate config: Failed to 
> bind one of the listener ports.
> Oct 12 20:16:50.857 [err] tor_init(): Reading config failed--see 
> warnings above. For usage, try -h.
> invoke-rc.d: initscript tor, action "start" failed.
> 

Philip Frei schrieb am Donnerstag, dem 12. Oktober 2006:

> I figured out that this is only an error when upgrading tor.
> I remove it (apt-get remove --purge), rebooted and tried a clean
> installation - and it worked.
> But upgrading from 0.1.1.23-1 failed.
> 

So what was listening there?  Upgrading worked for me, so I assume you
had some other process, or a Tor process you started yourself, already
occupying port 9050.

If you can still reproduce this bug - I can't - feel free to reopen it.

Peter
-- 
                           |  .''`.  ** Debian GNU/Linux **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/

--- End Message ---

Reply via email to