package squid 2.7.STABLE3-4.1ubuntu1 failed to install/upgrade:

Bug #367157 reported by Rick Simnett
4
Affects Status Importance Assigned to Milestone
squid (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: squid

I was upgrading from 8.10 to 9.04, and received this error.

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage:
 ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelModules: ath_hal
Package: squid 2.7.STABLE3-4.1ubuntu1
SourcePackage: squid
Title: package squid 2.7.STABLE3-4.1ubuntu1 failed to install/upgrade:
Uname: Linux 2.6.27-11-generic x86_64

Revision history for this message
Rick Simnett (sinfotech) wrote :
Revision history for this message
Andreas Olsson (andol) wrote :

Could you repost the /var/log/dist-upgrade/ contents? It apparently got truncated to 40bytes...

Changed in squid (Ubuntu):
status: New → Incomplete
Revision history for this message
Rick Simnett (sinfotech) wrote :

Here is the contents of the entire directory. I tar and gzip'd them.

Hope this helps.

:)

Revision history for this message
Andreas Olsson (andol) wrote :

Yeah, those files might have helped :) Just not sure if the archive was gzip'd...

Don't think this is a generic problem. I installed squid on a fresh 8.10, did a do-release-upgrade to Jaunty, and Squid was still working. Of course, that was with only the default configuration.

Looking in your /var/log/dist-upgrade/term.log I see quite a few attempts to access the non-existent path /null. At one occasion it happens right next to your "subprocess post-installation script returned error exit status 1".

Can you find anything in your squid configuration which would explain why the upgrade would want to access /null?

Revision history for this message
Rick Simnett (sinfotech) wrote :

Actually yes, I have the cachedir set to /null so that my squid configuration doesnt cache any of the pages it visits.

Revision history for this message
Andreas Olsson (andol) wrote :

Having a non existing cachedir doesn't seem to the entirely proper solution.

http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#head-c1da1b7113875d4bb84170e3de291298cb1be7f3

The reason this error occurred was because the package manager tried to read the permission of a folder which turned out not to exist. Not entirely sure if this is classify as a bug, considering it is the result of a somewhat faulty configuration.

Revision history for this message
Rick Simnett (sinfotech) wrote :

hmmm I would have to agree with you, there should be a directory /null I dont know why I dont have it there. I apologize. A faulty configuration definitelyw ould be the issue in this case.

Revision history for this message
Andreas Olsson (andol) wrote :

Well, since we seem to agree I'll be setting the status of this bug to Invalid.

By the way, if I understand that FAQ entry correctly; since you'r running Squid 2.7 you might not even need a cache_dir entry if you'r not going to do any caching. Anyhow, I'm really no Squid expert, so I will leave the figuring out to you.

Changed in squid (Ubuntu):
status: Incomplete → Invalid
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.