package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1

[Graham Strong]

First-time user of this facility. I'm just following the instructions generated by the do-release-upgrade process.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: squid 3.5.12-1ubuntu7.2
ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
Uname: Linux 3.13.0-95-generic i686
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: i386
Date: Tue Sep 20 22:25:53 2016
DuplicateSignature: package:squid:3.5.12-1ubuntu7.2:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-11-24 (666 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.3)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: squid3
Title: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-09-20 (0 days ago)
mtime.conffile..etc.squid.squid.conf: 2014-12-13T17:14:53.262193

[Christian Ehrhardt  (paelzer)]

From the Log:
Removing obsolete conffile /etc/squid3/msntauth.conf ...
Preserving user changes to /etc/squid/squid.conf (renamed from /etc/squid3/squid.conf)...
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

Hi,
it seems you formerly had a custom squid configuration that now fails to work.
The issue seems to be around "/var/spool/squid3"
Might that have been renamed to just squid as well?

Yeah I see that the new dir is "/var/spool/squid" now instead.

So this is a case where your local configuration is incompatible with the new layout.
I'd recommend to change the config or system setup so they match against each other.

I wonder thou if the package upgrade should take care of those in a maintainer script.
I'd have some ideas, but then users could have done arbitrary things with their /var/spool/squid3 so any postinst handling might be dangerous killing what an admin had set up.
So I think this should stay as is.

In your case as said before I'd recommend adapting setup or config file.

Setting the bug to incomplete, please reopen if you think this is an issue in the package itself or if the recommended workaround doesn't work.

[Graham Strong (stronggr)]

First of all, thank you for your response.

As far as I am aware, the only thing I would have done with Squid was to
customize Squid.conf. Unlikely to have changed a directory name. At the
time of first installing/commissioning I would have been very cautious
about making alterations that didn't need to be made.

The tardiness in responding to your reply, was that this particular system
was also in the process of giving a HDD failure. It wasn't obvious and
there were a few things in the latest Ubuntu LTS server release (16.04.1)
that was distracting me from seeing this problem. As well, my other (file)
server also decided to lock up. I'm currently running in it in recovery
mode. From the internet forums, it seem like this may be a graphic card
driver - I believe nVidia are not forthcoming with the Linux community on
providing information etc for their cards.

So, I have the system up again, but Squid appears to be dropping the URL.
Will hit the internet and see what solutions there are.

Once again, thanks for your response.

On 22 September 2016 at 23:52, ChristianEhrhardt <<email address hidden>
> wrote:

> >From the Log:
> Removing obsolete conffile /etc/squid3/msntauth.conf ...
> Preserving user changes to /etc/squid/squid.conf (renamed from
> /etc/squid3/squid.conf)...
> 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
>
> Hi,
> it seems you formerly had a custom squid configuration that now fails to
> work.
> The issue seems to be around "/var/spool/squid3"
> Might that have been renamed to just squid as well?
>
> Yeah I see that the new dir is "/var/spool/squid" now instead.
>
> So this is a case where your local configuration is incompatible with the
> new layout.
> I'd recommend to change the config or system setup so they match against
> each other.
>
> I wonder thou if the package upgrade should take care of those in a
> maintainer script.
> I'd have some ideas, but then users could have done arbitrary things with
> their /var/spool/squid3 so any postinst handling might be dangerous killing
> what an admin had set up.
> So I think this should stay as is.
>
> In your case as said before I'd recommend adapting setup or config file.
>
> Setting the bug to incomplete, please reopen if you think this is an
> issue in the package itself or if the recommended workaround doesn't
> work.
>
>
> ** Changed in: squid3 (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1625569
>
> Title:
> package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess
> installed post-installation script returned error exit status 1
>
> Status in squid3 package in Ubuntu:
> Incomplete
>
> Bug description:
> First-time user of this facility. I'm just following the instructions
> generated by the do-release-upgrade process.
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: squid 3.5.12-1ub...

[Christian Ehrhardt  (paelzer)]

"I'm currently running in it in recovery mode"

=> Uh, good luck recovering!

According to your former response I'll set the bug to incomplete for now.
If my suggestions won't help to fix the issue for you after recovering please reopen and share a bit more about the config/setup that you use to cause the issue.

Given what you said (no "very" custom conf for squid used) I'd consider purging the old package, removing all traces/dirs that you might have made and install a fresh one. That works for me giving me a working squid and I hope it does so for you as well.

[Graham Strong (stronggr)]

OK. Now back to where I was pre 16.04.1 installs.

For my Firewall/caching server, replaced a failing HDD and installed
16.04.1. All OK.

For my File server, that was an interesting exercise. Finally found the
problem: there is a little parameter ( vt-handoff=7 ) on the grub file.
Removing this during a boot, meant that boot went through to completion.
At the moment the semi-permanent solution is to delete quiet splash from
grub in order to stop the presence of vt-handoff. Will look at changing
10_linux script so that I can return to suppression of boot verbiage,
without having the boot halting before boot completion. *Note:* most of the
Internet hits about this problem where related to a desktop install and the
need to do something with the nVidia drivers.

Now I was able to check my File server backup files to see if it was me or
Squid naming everything with "Squid3". I have the original Squid install
conf file (pre 16.04.1); its definitely been Squid that named the various
files with "Squid3" and not just "Squid"

Ideally, Squid should have started with "Squid" as its file naming
convention and then there would have been no problem. Since it didn't, I
would have thought that the onus was on the install procedures to take into
account, a change in the file naming convention.

On 30 September 2016 at 20:42, ChristianEhrhardt <<email address hidden>
> wrote:

> "I'm currently running in it in recovery mode"
>
> => Uh, good luck recovering!
>
> According to your former response I'll set the bug to incomplete for now.
> If my suggestions won't help to fix the issue for you after recovering
> please reopen and share a bit more about the config/setup that you use to
> cause the issue.
>
> Given what you said (no "very" custom conf for squid used) I'd consider
> purging the old package, removing all traces/dirs that you might have
> made and install a fresh one. That works for me giving me a working
> squid and I hope it does so for you as well.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1625569
>
> Title:
> package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess
> installed post-installation script returned error exit status 1
>
> Status in squid3 package in Ubuntu:
> Incomplete
>
> Bug description:
> First-time user of this facility. I'm just following the instructions
> generated by the do-release-upgrade process.
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: squid 3.5.12-1ubuntu7.2
> ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
> Uname: Linux 3.13.0-95-generic i686
> ApportVersion: 2.14.1-0ubuntu3.21
> Architecture: i386
> Date: Tue Sep 20 22:25:53 2016
> DuplicateSignature: package:squid:3.5.12-1ubuntu7.2:subprocess
> installed post-installation script returned error exit status 1
> ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> InstallationDate: Installed on 2014-11-24 (666 days ago)
> InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release
> i386 (20140722.3)
> RelatedPackageVersions:
> dpkg 1.18.4ubuntu1...

[Christian Ehrhardt  (paelzer)]

> For my Firewall/caching server, replaced a failing HDD and installed
> 16.04.1. All OK.

Good that this is ok again.

> Ideally, Squid should have started with "Squid" as its file naming
> convention and then there would have been no problem.

I couldn't agree more, but still lack the time machine to change such things :-)

> Now I was able to check my File server backup files to see if it was me or
> Squid naming everything with "Squid3". I have the original Squid install
> conf file (pre 16.04.1); its definitely been Squid that named the various
> files with "Squid3" and not just "Squid"

Yes in the past all was "squid3" names.
On the update it tries to adapt and handle things to become just "squid" to be like any new install would be.

My former assumption was that you already had some dir named yourself /var/spool/squid - without the "3". That would have broken the transition.
As I said while the maintainer scripts could try to catch that the possible combinations are so manyfold that any fix usually introduces one more error :-/

Thank you a lot for your report and your detailed feedback.
I'm happy that your setup works again.

Given my expectation of fixes for "auto config updates" I'd keep the bug on incomplete to allow it to expire. If you think this is an issue that has to be "fixed" please reset it to new.