package squid 3.5.12-1ubuntu7.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Stephen Parry]

error occurred during upgrade to xenial
stat: cannot stat '/var/spool/squid3': No such file or directory
chown: cannot access '/var/spool/squid3': No such file or directory
dpkg: error processing package squid (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (229-4ubuntu16) ...
Errors were encountered while processing:
 squid
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/squid.0.crash'
Error in function:

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: squid 3.5.12-1ubuntu7.3
Uname: Linux 4.4.50-rh54-20170220215556.xenU.i386 i686
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: i386
Date: Mon Mar 6 16:16:22 2017
DuplicateSignature: package:squid:3.5.12-1ubuntu7.3:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
SourcePackage: squid3
Title: package squid 3.5.12-1ubuntu7.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-03-06 (0 days ago)
mtime.conffile..etc.squid.squid.conf: 2015-10-01T04:50:38

[Nish Aravamudan (nacc)]

I believe the package scripts are attemping to handle the default case, where /var/spool/squid3 was renamed to /var/spool/squid. Did you use a custom directory?

[Stephen Parry (sgparry)]

No, but I may have had problems with the rename during a previous
upgrade. When I looked at the server there was quite a mess of squid
versus squid3 named directories. What is the release history for squid
versus squid3 naming?

On 07/03/2017 00:49, Nish Aravamudan wrote:
> I believe the package scripts are attemping to handle the default case,
> where /var/spool/squid3 was renamed to /var/spool/squid. Did you use a
> custom directory?
>
> ** Changed in: squid3 (Ubuntu)
> Status: New => Incomplete
>

[Nish Aravamudan (nacc)]

On 07.03.2017 [01:03:43 -0000], Stephen Parry wrote:
> No, but I may have had problems with the rename during a previous
> upgrade. When I looked at the server there was quite a mess of squid
> versus squid3 named directories. What is the release history for squid
> versus squid3 naming?

Trusty would be squid3, Xenial would be squid, presuming you were doing
an LTS -> LTS upgrade. Or did you mean something more specific?

[Launchpad Janitor (janitor)]

[Expired for squid3 (Ubuntu) because there has been no activity for 60 days.]

[Glen Ritchie (spikeles)]

I just had this same issue occur with an upgrade from trusty to xenial.

Wouldn't even let me uninstall the squid package from the newly upgraded system until I created the directory '/var/spool/squid3', then the package worked and I could uninstall/reinstall.

Luckily it was in a virtual machine, so I was able to revert to the pre-upgrade state to see what was going on before the upgrade and verified that the /var/spool/squid3 directory existed before the upgrade started so it's been removed by *something* at some point before the attempt to uninstall squid.

[Niels Erik Jensen (nej-f)]

hope to get it fixst