Hi Chip,
I suspected the same thing but i've restarted everything -
even the whole machine...
So everything is working.. I've tried to add something new
to squidGuard. I stop and restart everything (including
the whole server) and SG passes everything through.. so
I restore the previous SG conf and stop and restart everything
and it's still passing everything through... I've fixed this
previously by building a small SG conf (with one one site),
checking that works and then slowly building it back up to
where it was before one by one..
Any ideas?
Andrew
Andrew,
It doesn't sound like a squidguard problem since the command-line interface
is working. It sounds like squid isn't handing the request off to
squidguard. Have you tried restarting squid? Perhaps instead of "squid -k
reconfigure" you should try stopping and then starting the squid proxy
service.
Chip Burkitt
Andrew Nelson wrote:
Hi,
I've had this problem a few times in the past and it's driving me crazy.
I have squidguard working fine, blocking some sites for some groups of
users and allows some for others.. It's quite a large squidGuard.conf
file (~780 lines) because there's various sites, various user groups
within the sites and I allow them to manipulate their various allow/deny
lists through an interface that the 'site managers' can add users into.
Occasionally after I make a change (ie add a new block list or
user group to the squidGuard conf), and restart everything,
rebuild the databases, squid just allows everything through.
SquidGuard is DEFINATELY NOT in emergency mode, the log
file just looks like it normally does, and trying direct commands
to squidGuard like:
echo "www.playboy.com 192.168.102.140 testuser GET" | squidGuard -c
/usr/local/squid/etc/squidGuard.conf
ALWAYS returns the correct response (ie blocking playboy), but
when you point a browser at squid with this username and IP, it
just allows it.
The line in squid is:
redirect_program /usr/local/bin/squidGuard -c
/usr/local/squid/etc/squidGuard.conf
I've fixed this problem in the past by starting with a completely fresh
config file, and adding back in the sites one by one, restarting and
rebuilding each time and checking that it's working after each one.
When I get to the bottom (and have the same file I had to start with),
it's still working and the problem has gone away...
Is there a bug somewhere? the config file is too big to rebuild
one-by-one
now and I don't know what that does to make it work anyway.
Can anyone help?
Thanks,
Andrew.
<< chip.vcf >>
