Greetings Joop, >2006-09-20 13:54:33 [6730] /var/lib/squidGuard/db/risse/allowedsites: >Permission denied >2006-09-20 13:54:33 [6730] going into emergency mode >2006-09-20 13:54:33 [6731] init >domainlist /var/lib/squidGuard/db/risse/allowedsites >2006-09-20 13:54:33 [6731] /var/lib/squidGuard/db/risse/allowedsites: >Permission denied
...etc... When you ran squidguard manually as root you didn't get the permission errors, but when squid invokes squidguard, you do. That seems to suggest that squid isn't running as user squid, or if so, can't (for some reason??) access your /var/lib/squidGuard/db/* directories. Try giving the squid user a shell such as /bin/bash in the /etc/passwd file (which it may have already), changing to the squid user, and rerunning your debug mode test command to squidguard. See what I mean? Running as root doesn't give you a problem, so switch user to squid and try again. # vi /etc/passwd (or an editor of your chosing) # su - squid $ echo "http://www.google.nl 10.0.1.1/- - GET" | /usr/sbin/squidGuard -c /etc/squidguard.conf -d I bet you don't get your blank line then. You can then manually verify file permissions as such: $ cat /var/lib/squidGuard/db/aggressive/domains ...and see if in fact the squid user is able to read them. The good news is that the errors in the log seem to point to file permission problems which are pretty easy to fix. The other possibility is that the squid config file is causing squid to run as a user other than squid. Maybe start up squid and use: # ps aux | grep squid ...to see what as what user squid is running. Cheers, --Scott!
