*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have dug all over the place looking for a solution for this, so if someone has one or knows where I can find one, I would appreciate it.
Squid:2.5 (used to save bandwidth)
We provide Wi-Fi service.
We are having problems with squid crashing and blocking any web traffic to our clients. Clients are getting the good 'ol "Page can't be displayed". We have several sites and some of the other guys are trying to figure out why it is crashing, and reviewing logs but our group hasn't heard anything yet for an exact cause. Meanwhile, we don't know about it crashing until Support gets a call about not being able to view a page. They log in and manually restart squid and see it was off/crashed.
I am looking for one or a group of possible solutions:
1.) Currently when squid crashes.. it does not "auto-restart" (I am awaiting a email on specifically what type of crash it is. Does the program close all together? or just hung is some fashion.)
So is there a way to get squid or FreeBSD to recognize the crash if per say the program closes all together and restart on its own? **keep in mind on crash/ noone can pull up a web page if that helps)
2.) Can Squid be configured on fail to allow all traffic instead of all traffic being blocked?
3.) Is there a way to set something up that will monitor Apache and Squid and email notify of a failure as well as a piece of the log file?
If there is any information needed let me know and I will get whats needed to help figure this out.