Hello, > But if squidguard dies, it doesn't mean that squid dies too. > > To sum up : How can I see that squidguard is in emergency mode ?
I don't know about how to see if 'squidguard is in emergency mode,' but I have hacked on squidguard for months now, and many of my hacks have caused squidguard to die :) What I notice is that squid makes note of a dead redirector in the squid cache.log. There will be a note for each time the redirector is called and the thread dies. This is one of the only ways that I was able to debug my squidguard hacks. That is, by monitoring the squid cache.log. Here is a snippet from my cache log while I was still hacking squidguard. I had 10 redirector_children running at the time, and all six (6) calls here to the redirector caused that instantiantion of squidguard to die (I had some bad hack code that was killing squidguard). Then for squid there were not enough redirectors running to handle additional redirector calls, so squid had a fatal error: 2003/12/18 23:01:30| WARNING: redirector #1 (FD 5) exited 2003/12/18 23:01:31| WARNING: redirector #2 (FD 6) exited 2003/12/18 23:01:31| WARNING: redirector #3 (FD 7) exited 2003/12/18 23:01:31| WARNING: redirector #4 (FD 8) exited 2003/12/18 23:01:31| WARNING: redirector #5 (FD 9) exited 2003/12/18 23:01:31| WARNING: redirector #6 (FD 10) exited 2003/12/18 23:01:31| storeDirWriteCleanLogs: Starting... 2003/12/18 23:01:31| Finished. Wrote 1692 entries. 2003/12/18 23:01:31| Took 0.0 seconds (839702.2 entries/sec). FATAL: Too few redirector processes are running Squid Cache (Version 3.0-PRE3-CVS): Terminated abnormally. I hope this makes sense? It appears that the only visibility into redirector thread life is through cache.log. There is probably a way in squid.conf to setup some type of email alert mechanism to let you know if redirectors are dying. I would ask the squid-users list about that? Murrah Boswell
