package tor 0.1.2.17-1 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Bug #149679 reported by Arlos
68
This bug affects 8 people
Affects Status Importance Assigned to Milestone
tor (Ubuntu)
Fix Released
Undecided
Jacob Appelbaum

Bug Description

Binary package hint: tor

Have been running 7.10 Beta, and doing regular package updates for couple months now. Had 288? updates to install, I had waited a day because of a notice saying some packages were not authorized, canceled out and waited. Used sudo apt-get update per instructions in a forum, then clicked the regular update icon, with no non-authorized notice. After letting it download and install, I had a crash report detected. TOR update error: "E: tor: subprocess post-installation script returned error exit status 1"

ProblemType: Package
Architecture: i386
Date: Fri Oct 5 16:20:51 2007
DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: tor 0.1.2.17-1
PackageArchitecture: i386
SourcePackage: tor
Title: package tor 0.1.2.17-1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux Arlos-Ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

Revision history for this message
Arlos (arlos70-ntuf) wrote :
Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Here is the error:

Setting up tor (0.1.2.17-1) ...
debian-tor uid check: ok
debian-tor homedir check: ok
Raising maximum number of filedescriptors (ulimit -n) to 8192.
Starting tor daemon: tor...
Oct 05 16:20:51.873 [notice] Tor v0.1.2.17. This is experimental software. Do not rely on it for strong anonymity.
Oct 05 16:20:51.876 [notice] Initialized libevent version 1.3b using method epoll. Good.
Oct 05 16:20:51.876 [notice] Opening Socks listener on 127.0.0.1:9050
Oct 05 16:20:51.876 [notice] Opening Socks listener on 192.168.0.1:9100
Oct 05 16:20:51.876 [warn] Could not bind to 192.168.0.1:9100: Cannot assign requested address
Oct 05 16:20:51.876 [notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050
Oct 05 16:20:51.876 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Oct 05 16:20:51.876 [err] Reading config failed--see warnings above.
invoke-rc.d: initscript tor, action "start" failed.
dpkg: error processing tor (--configure):
 subprocess post-installation script returned error exit status 1

Changed in tor:
status: New → Confirmed
Weems (leoville)
Changed in tor:
assignee: nobody → leoville
Revision history for this message
Orion (lafoudre) wrote :

I have the same bug:

***@****-laptop:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up tor (0.2.0.34-1~intrepid+1) ...
Raising maximum number of filedescriptors (ulimit -n) to 32768.
Starting tor daemon: tor...
Jun 16 20:35:57.267 [notice] Tor v0.2.0.34 (r18423). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
Jun 16 20:35:57.269 [notice] Initialized libevent version 1.3e using method epoll. Good.
Jun 16 20:35:57.269 [notice] Opening Socks listener on 127.0.0.1:9050
Jun 16 20:35:57.269 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Jun 16 20:35:57.269 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Jun 16 20:35:57.269 [err] Reading config failed--see warnings above.
invoke-rc.d: initscript tor, action "start" failed.
dpkg: error processing tor (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of tor-geoipdb:
 tor-geoipdb depends on tor (>= 0.2.0.34-1~intrepid+1); however:
  Package tor is not configured yet.
dpkg: error processing tor-geoipdb (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                          Errors were encountered while processing:
 tor
 tor-geoipdb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Runa A. Sandvik (runasand) wrote :

@Orion: it seems like something is wrong with your tor config and that is why the installation fails. Could you paste the contents of the configuration file here?

Revision history for this message
Orion (lafoudre) wrote :

Now it's work but i have reinstall ubuntu totaly

Revision history for this message
jb (tigergrr) wrote :

i had the same error message as Orion but with a newer version of tor-geoipdb. when update manager attempted to do the upgrade i was running Tor including a relay node at the time so i used Vidalia to shut down Tor. i then opened a terminal and did the sudo apt-get update then sudo apt-get upgrade and here was the result:

sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up tor (0.2.1.21-1~karmic+1) ...
Raising maximum number of filedescriptors (ulimit -n) to 16384.
Starting tor daemon: tor...
Jan 04 20:51:55.333 [notice] Tor v0.2.1.21. This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
Jan 04 20:51:55.337 [notice] Initialized libevent version 1.4.11-stable using method epoll. Good.
Jan 04 20:51:55.337 [notice] Opening Socks listener on 127.0.0.1:9050
done.

Setting up tor-geoipdb (0.2.1.21-1~karmic+1) ...

Revision history for this message
Jacob Appelbaum (jacob-appelbaum) wrote :

Is this bug still relevant?

Changed in tor (Ubuntu):
assignee: Weems (leoville) → Jacob Appelbaum (jacob-appelbaum)
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.