Sorry, I am being slow here? Isn't the obvious error in the log file "parse error in configfile /etc/squid/squidguard.conf line 14" ? Which, I assume, is caused by the empty source statement at line 14.
Ian -----Original Message----- From: Doug Poland [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 19:10 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Squidguard Not Blocking Urls Wall, Shawn said: > After reading through most of the postings, I still can't figure > out why squidguard doesn't block any urls. I'm running berkeley > 3.2.9 and I've give permission to the squidgurad dirs. I did > notice this recouring problem in my squid cache log: > > 2002/09/20 07:40:43| Starting Squid Cache version 2.4.STABLE4 for > i586-mandrake-linux-gnu... 2002/09/20 07:40:43| Process ID 4669 > 2002/09/20 07:40:43| With 1024 file descriptors available > 2002/09/20 07:40:43| DNS Socket created on FD 4 > 2002/09/20 07:40:43| Adding nameserver 205.233.109.40 from > squid.conf 2002/09/20 07:40:43| helperOpenServers: Starting 5 > 'squidGuard' processes 2002/09/20 07:40:43| User-Agent logging is > disabled. > 2002-09-20 07:40:43 [4670] (squidGuard): can't write to logfile > /var/log/squidGuard/log/squidGuard.log 2002-09-20 07:40:43 [4672] > (squidGuard): can't write to logfile > /var/log/squidGuard/log/squidGuard.log 2002-09-20 07:40:43 [4671] > (squidGuard): can't write to logfile > /var/log/squidGuard/log/squidGuard.log 2002-09-20 07:40:43 [4673] > (squidGuard): can't write to logfile > /var/log/squidGuard/log/squidGuard.log 2002-09-20 07:40:43 [4674] > (squidGuard): can't write to logfile > /var/log/squidGuard/log/squidGuard.log 2002-09-20 07:40:43 [4670] > parse error in configfile /etc/squid/squidguard.conf line 14 > 2002-09-20 07:40:43 [4670] going into emergency mode > 2002-09-20 07:40:43 [4671] parse error in configfile > /etc/squid/squidguard.conf line 14 2002-09-20 07:40:43 [4671] > going into emergency mode > 2002-09-20 07:40:43 [4672] parse error in configfile > /etc/squid/squidguard.conf line 14 2002-09-20 07:40:43 [4672] > going into emergency mode > 2002-09-20 07:40:43 [4674] parse error in configfile > /etc/squid/squidguard.conf line 14 2002-09-20 07:40:43 [4673] > parse error in configfile /etc/squid/squidguard.conf line 14 > 2002-09-20 07:40:43 [4674] going into emergency mode > 2002-09-20 07:40:43 [4673] going into emergency mode > 2002/09/20 07:40:43| Unlinkd pipe opened on FD 14 > 2002/09/20 07:40:43| Swap maxSize 102400 KB, estimated 7876 > objects 2002/09/20 07:40:43| Target number of buckets: 393 > 2002/09/20 07:40:43| Using 8192 Store buckets > 2002/09/20 07:40:43| Max Mem size: 8192 KB > 2002/09/20 07:40:43| Max Swap size: 102400 KB > 2002/09/20 07:40:43| Rebuilding storage in /var/spool/squid > (CLEAN) 2002/09/20 07:40:43| Using Least Load store dir selection > 2002/09/20 07:40:43| Set Current Directory to /var/spool/squid > 2002/09/20 07:40:43| Loaded Icons. SquidGuard is going into emergency mode and therefore nothing is being blocked. Check the log file existance and permissions and make sure the squidGuard process can write to it. -- Regards, Doug
