package squid3 3.1.19-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Errors were encountered while processing:
squid3
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: squid3 3.1.19-1ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-25-
ApportVersion: 2.0.1-0ubuntu8
AptOrdering:
squid3: Install
squid: Install
squid3: Configure
squid: Configure
Architecture: i386
Date: Mon Jun 18 20:13:48 2012
DuplicateSignature:
Setting up squid3 (3.1.19-1ubuntu3) ...
/var/lib/
dpkg: error processing squid3 (--configure):
subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
SourcePackage: squid3
Title: package squid3 3.1.19-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
modified.
modified.
tags: | removed: need-duplicate-check |
Changed in squid3 (Ubuntu): | |
status: | New → Confirmed |
Thank you for your report.
This looks like a local configuration problem, rather than a bug in Ubuntu. You seem to have deleted your squid configuration, so it cannot be expected to restart successfully.
You can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.
If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.