package squidguard 1.5-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Bug #1313200 reported by Steve Jelfs
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
squidguard (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

During upgrade to 14.04

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: squidguard 1.5-2
ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
Date: Sat Apr 26 22:13:39 2014
DuplicateSignature: package:squidguard:1.5-2:ErrorMessage: subprocess installed post-installation script returned error exit status 1
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2013-06-24 (306 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
SourcePackage: squidguard
Title: package squidguard 1.5-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago)

Revision history for this message
Steve Jelfs (y9a7s7tjd2jxyc-steve-si9yrl01qsu4bt) wrote :
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 squidguard (Ubuntu):
status: New → Confirmed
Revision history for this message
Joerg Delker (ubuntu-delker) wrote :

When upgrading to trusty, this error has hit me, too.

After some investigation I figured that there are some flaws in /usr/sbin/update-squidgard, which is called during the configure phase on install/update.

1) update-squidguard calls a "su - proxy squidguard ..." at the end to rebuild the database.
This fails with
    Rebuild SquidGuard database - this can take a while.
    This account is currently not available.
That's no surprise because the "proxy" user was created previously with
    proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
The invocation of "su" checks for a valid shell, which "/usr/sbin/nologin" isn't.

2) update-squidguard tries to restart squid at the very end, but actually fails to do so, because it checks for appropriate init.d files.
With squid3 (3.3.8-1ubuntu6) there aren't any, because this package is already upstart enabled.

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

This bug was fixed in the package squidguard - 1.5-3

---------------
squidguard (1.5-3) unstable; urgency=medium

  * debian/control:
    - Bump Standards-Version to 3.9.5 (no changes).
    - Remove needless build dependency to perl.
    - Perl packages only recommended to squidguard. Closes: #751003
    - Squid packages only recommended to squidguard. Closes: #756293
  * debian/rules:
    - add again hardened flags through dpkg-buildflags. Closes: #760726
    - Don't install obsolete documentation files.
    - Add --with-nolog=yes to disable debug logging (thanks to J. Redondo).
  * Fix compiler warnings in y.tab.c.bison, sg.y.in (add -DLDAP_DEPRECATED)
  * Fix compiler warnings in sgDiv.c.in (better sprintf formatting).
  * Add italian translation for debconf. Closes: #761097
  * Add more information about time configuration (time-config.txt).
  * Optimize reload of squid in update-squidguard. LP: #1313200

 -- Joachim Wiedorn <email address hidden> Mon, 22 Sep 2014 16:40:44 +0200

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

Other bug subscribers

Remote bug watches

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