Squid3 3.1.11-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Paul Shiner]

Error updating Squid 3 from 3.0/18 STABLE to any of the newer versions. Tried 3 updated versions.

All give this error:

Errors were encountered while processing:
 squid3
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)

*** The package "squid3" failed to install or upgrade.

Setting up squid3 (3.0.STABLE19-1ubuntu0.2) ...
chown: invalid user: `proxy\r:winbindd_priv\r'
dpkg: error processing squid3 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 squid3

Squid installs but doesn't configure.
Squid upgrade also blows away all my custom Error pages as well but guess that's a different issue.
Note - I always tell it to keep existing Squid.conf file.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: squid3 3.1.11-1ubuntu0.1
ProcVersionSignature: Ubuntu 2.6.35-32.65-server 2.6.35.14
Uname: Linux 2.6.35-32-server x86_64
Architecture: amd64
Date: Wed Feb 22 12:15:51 2012
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
SourcePackage: squid3
Title: package squid3 3.1.11-1ubuntu0.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to natty on 2012-02-22 (0 days ago)

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug.

The error message you pointed to:

chown: invalid user: `proxy\r:winbindd_priv\r'

suggests that if you edit /etc/squid3/squid.conf you should find lines without a trailing newline. Adding newlines should solve this problem. Could you post your /etc/squid3/squid.conf to this bug?

[Paul Shiner (paul-shiner)]

Fixed - thanks!!

I won't lie - I have no idea what a trailing new line is!

But as this was a test system I was testing the upgrade on, I simply moved the "squid.conf" to "squid.conf.temp" and put the default "squid.conf.dpkg" as "squid.conf"

I then re ran "apt-get upgrade" and it ran without the error.

"dpkg -s squid3" now thinks it's "installed ok" so I;m assuming it's all happy again.

I shall work on removing the dodgy lines from our squid.conf as it is a completely custom handwritten configuration file and more than likely to have these dodgy "trailing newlines".

I have to work on the squid.conf file anyway as squid upgrade has completely change the way NTLM authentication works... as it's broken on upgrade :(

Many Thanks for quick response.

Paul

[Paul Shiner (paul-shiner)]

I got VI to show special characters

Looks like there were lots of random:

 ^I

characters (capital i) embedded in quite a few of the comments. Usually just after the # character that shows it's a comment line, but some were mid-way through the comment line.

I can't confirm, because I'm now running the latest version on my test server. I can update you when I try update again, after cleaning up config file.. but I suspect this is the reason when changing the config file to vanilla one works.

Thanks,

Paul

[Robie Basak (racb)]

Marking as Invalid as it sounds like this was a local configuration problem and not a bug in Ubuntu.