Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You could use nrpe and a check command to telnet to the squid port to see if its still listening.
Instead I would check connectivity with a command like 'check_http -I proxyIp -p proxyPort -u http://somesiteaddre.ss/' instead. If the cache doesn't return outside the URI (maybe add a regex to get certain result) then you know there's something functionally wrong, while checking the port only tells you if the service is listening.
Quote:
Originally Posted by creatorrr
I am kind of a beginner so i really need more info please.
If Nagios is new for you then I strongly suggest reading the docs, backing up the default configs and experiment with testing default services. This should not be mistaken for a "RTFM"-type answer, it's just that the common first error newbies make is to not read the docs. They really are not that hard to get through, you need the knowledge to run it anyway and it makes it easier for you to ask specific questions.
OK, I guess i will neeed to put more effort in explaining the problem if i want to get satisfactory answer.
I am running nagios on CentOS and i am monitoring windows and linux server and netowrk devices with no problem. What i want to know is if anyone of you is monitoring Squid Proxy with Nagios. The plugin for monitoring Squid does not come as a default with the installation of Nagios thus i was looking for some "custom" made Squid plugins. I have found couple but unfortenatelly they happen to be OS specific on none of those appeared to work with Centos. For example, the error message i am getting is "Return code of 126 is out of bounds - plugin may be missing".
So again, my question is if anyone of you know for some Nagios plugin for monitoring squid that would work on Red Hat or CentOS.
Not sure if this is still an ongoing problem, but perhaps this solution might prove useful to someone.
Like a number of people I had problems getting the 'check_squid' plugin to work with my Squid proxy, since I had it listening on port 8080. I found a number of suggestions involving using 'check_http' to check whether the service was running, but this didn't work regardless what I did.
In the end I found a workaround; I edited the 'http.cfg' file located in the /etc/nagios-plugins/config folder, and commented out the 'check_squid' definition. I saved this and the opened the 'tcp_udp.cfg' file in the same location and added the following lines:
This now means that the port 8080 is being checked directly to see if it's active instead of HTTP traffic being sent to the proxy. Certainly seems to have worked for me. In this instance, Nagios was running on a test Ubuntu system, but it should work just as well on Centos/Red Hat, assuming the plugin config directory is in the same location.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.