I had similar problems on 8.2RC1 and found the following by running
squidGuard on testfiles.
squidGuard -c /etc/squid/squidGuard.conf <test.pass
1) The logdir directive
logdir /var/log/squidGuard
wants to create
/var/log/squidGuard/log/squidGuard.log
2002-03-11 15:07:01 [8237] squidGuard: can't write to logfile
/var/log/squidGuard/log/squidGuard.log
When I created that subdirectory squidGuard would log.
2) an empty rewrite section would cause errors. When commented out
#rewrite {}
squidGuard would initialize normally
2002-03-11 15:07:01 [8237] parse error in configfile
/etc/squid/squidGuard.conf line 148
had the empty rewrite
Restarting squid - blocking started to work.
The cgi-scripts generate unsuitable output but the system dows block.
Tons more testing to do before this looks serviceable but I am encouraged.
Jim Tarvid
On Monday 11 March 2002 07:53 pm, you wrote:
> >>>>2. Does any of the filtering in squidGuard work? It
> >>>>doesn't seem to catch anyting on either keyword or url.
> >>>
> >>>yes, you should remove the .db files in
> >>>/usr/share/squidGuard-1.2.0/db/banneddestination/ and restart squid and
> >>>try if this works for you ...
> >>
> >>Nope...
> >
> > any error messages ?
> >
> > tail -f /var/log/squidGuard/squidGuard.log
> > tail -f /var/log/messages
> > tail -f /var/log/squid/store.log
>
> I'll double check tonight, but I looked in the logs and
> didn't see anything in there. ( the only log I haven't
> loked in is squid/store.log
>
> -randy
