Re: Squid problems

[nx13372 <nx13372a@net.vodafone.pt>]

nx13372 wrote:

> Adam Aube wrote:
>
> > nx13372 wrote:
> >
> >  
> >
> > > Hi all,
> > > All i do, was:
> > > #/etc/init.d/squid stop
> > > #rm -fr /var/spool/squid
> > > #rm /var/log/squid
> > > #squid -z
> > > #/etc/init.d/squid restart
> > > Squid starts ok.
> > > Now squid works, but don't cache. The
> > > #du -sh /var/spool/squid     is always 16452!
> > >   
> >
> >
> > Are there any entries in access.log? Are any of these TCP_HIT entries?
> >
> > Can you post your squid.conf (without blank lines or comments)?
> >
> > Adam
> >
> >
> >  
> Yes:
>
> 1090559466.268  12102 x.x.x.x TCP_HIT/200 534126 GET 
> http://http.us.debian.org/debian/pool/main/s/samba/libsmbclient_3.0.5-1_i386.deb 
> - NONE/- application/x-debian-package
> 1090584975.009   3905 x.x.x.x TCP_HIT/200 6652 GET 
> http://fedoranews.org/images/intro-computer.png - NONE/- image/png
>
> The only thing that grows is access.log!
> I'm getting mad! Since i already triple check everything (owner and 
> group of all squid files, squid.conf, iptables) couldn't this be a 
> kernel bug? I'm using a transparent proxy, and there's a lot of 
> options that must be enabled in kernel! I'm using kernel 2.4.26-3.
>
> thanks
No it's not a kernel problem. I reboot using the "old" 2.4.25 and the 
same result.
Is there anyone using squid as a transparent proxy (on Sarge or Sid)?
Or should i report this as a bug?

thanks.