Ubuntu
squid3 package

package squid3 3.1.15-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #891445 reported by Chris Halse Rogers
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
squid3 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Installing squid3 (as a dependency of squid-deb-proxy) onto a clean system fails when the postinst tries to start squid3.

dmesg contains [99409.540189] init: squid3 pre-start process (31725) terminated with status 2.

Tracing that back with trusty echo statements in the upstart script shows it dying at the line:
    cdr=`grepconf2 cache_dir /var/spool/squid`

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: squid3 3.1.15-1ubuntu2
ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0
Uname: Linux 3.1.0-2-generic x86_64
ApportVersion: 1.26-0ubuntu1
Architecture: amd64
Date: Thu Nov 17 12:29:28 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111107)
SourcePackage: squid3
Title: package squid3 3.1.15-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

lp:~gandelman-a/ubuntu/precise/squid3/lp891445
Ubuntu branches: Pending requested
Diff: 144 lines (+43/-56)
3 files modified
debian/changelog (+11/-0)
debian/rules (+1/-1)
debian/squid3.upstart (+31/-55)
lp:ubuntu/precise/squid3
Revision history for this message
Chris Halse Rogers (raof) wrote :
Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in squid3 (Ubuntu):
status: New → Confirmed
Revision history for this message
Adam Gandelman (gandelman-a) wrote :

Hi Chris--

Thanks for reporting this. Both the grepconf2() and grepconf() functions are attempting to parse a config file at /etc/squid/squid.conf, when it should be checking for the file at /etc/squid3/squid.conf

There is also an issue in the maxfds() function returning non-zero in absense of /etc/default/squid3 (which is not shipped with the package). This also causes the pre-start action to fail.

The first issue ends up not showing up if the previous squid(v2) is installed on the system as well. The latter is a blocker regardless. Both are addressed in the linked branch.

I'm curious to know why the sysv init script from squid(v2) was converted to the squid3 upstart job as opposed to the sysv init script that is actually packaged with squid3.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package squid3 - 3.1.15-1ubuntu3

---------------
squid3 (3.1.15-1ubuntu3) precise; urgency=low

  * debian/squid3.upstart: Properly return 0 from maxfds() if $SQUID_MAXFD is
    unset, else pre-start will fail as well. Also fix paths to config file.
    (LP: #891445)
  * debian/squid3.upstart: Modify to better reflect functionality of Debian's
    squid3.rc
  * debian/rules: Fix permissions on upstart job
 -- Adam Gandelman <email address hidden> Wed, 16 Nov 2011 18:26:25 -0800

Changed in squid3 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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