Re: [squid-users] Upgrading from 2.5.9 to 2.6.5 - woes + squish woes

D & E Radel wrote:
> Henrik Nordstrom wrote:
>> tis 2007-05-29 klockan 16:50 +1200 skrev D & E Radel:
>>
>>> Dang! Adding the line: "HTTP_PORT 3128" stops the error, but now I
>>> get no authentication prompt in my browser. Restarting squid is fine,
>>> but it doesn't seem to talk to my client's browser anymore.
>>
>> So what do you get?
>>
>> Any output from "squid -k parse"?
>
>
> Nothing. Nada.
>
>
>> Is accesses recorded in access.log?
>
>
> Nope.
>
>
>> Is the browser configured to use the proxy?
>
>
> Yes. It was working fine after upgrade to latest stable Debian version,
> but not after installing squish.
>
>
>> Regards
>> Henrik
>
>
> Thanks for the reply Henrik. Sorry about my delay. I suspect that Squish
> install somehow kacked my squid. I don't see how it could have though. I
> think perhaps the easiest way out, is to restore to an earlier drive
> image and retry the debian upgrade - but not install squish this time.
>
> Is there an alternative method to limit users to xMB downloads per day?
> Many thanks.
>
> Cheers.
> D.Radel.

An update. I reverted to an earlier HD image. Did the upgrade from Sarge to Etch (i.e. Squid 2.5.9
to 2.6.5) again. Everything worked ok. I did a diff on the original squid.conf and the modified one
by the Debian update and the only difference is the "HTTP_PORT 3128" line.

I must then conclude that the "make install" from squish borked my previous squid install. Removing
all the squish lines from squid.conf and the crontab, and deleting the squish folders still left me
with a borked squid. No output from "squid -k parse". No new accesses recorded in the access.log.
Just squid stopped talking to the browsers.

My squid is working again, but I don't think that I will try squish again. Any other options for
quota in squid?

Regards,
D.Radel.
Received on Sun Jun 03 2007 - 16:57:11 MDT