Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I'm looking for a free server monitoring software. Basically, I want to know if a server has lost power or is in a down state. I guess what i'm asking for is something that will sent a "PING" every once in a while to check if it's still up and running.
This is in a Windows Domain environment, but I can run the app on Windows or Linux. It really doesn't matter to me.
Maybe, something with a web interface or an app that runs on a single server that I can login to would be fine.
I'm looking for a free server monitoring software. Basically, I want to know if a server has lost power or is in a down state. I guess what i'm asking for is something that will sent a "PING" every once in a while to check if it's still up and running.
This is in a Windows Domain environment, but I can run the app on Windows or Linux. It really doesn't matter to me. Maybe, something with a web interface or an app that runs on a single server that I can login to would be fine.
Loads of things you can use, but if you're wanting to monitor this ONE THING now, chances are good you've set foot on a slippery slope that will wind up being, "Y'know, since we're monitoring THIS, can we monitor XXX and YYY...as well??"
For your use-case now, a simple bash script that sleeps for X minutes and sends a ping is all you'd need. But I'd suggest something like Nagios or Zabbix, so you can monitor the network hardware as well. Getting an alert that a server is down at dark-O-thirty in the morning isn't good, but getting it because the network switch went down (which may be someone elses problem) is even worse. Being able to do SNMP monitoring pretty easily, poking switches/disk space/memory is a good thing. And it gives you a central web-accessible interface.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,800
Rep:
Quote:
Originally Posted by TB0ne
Loads of things you can use, but if you're wanting to monitor this ONE THING now, chances are good you've set foot on a slippery slope that will wind up being, "Y'know, since we're monitoring THIS, can we monitor XXX and YYY...as well??"
For your use-case now, a simple bash script that sleeps for X minutes and sends a ping is all you'd need. But I'd suggest something like Nagios or Zabbix, so you can monitor the network hardware as well. Getting an alert that a server is down at dark-O-thirty in the morning isn't good, but getting it because the network switch went down (which may be someone elses problem) is even worse. Being able to do SNMP monitoring pretty easily, poking switches/disk space/memory is a good thing. And it gives you a central web-accessible interface.
When one of my previous employers was started using Nagios for their large network, getting 27 pages about servers in a remote data center were common. Then I added the network gear to the monitoring. (Our network team wasn't happy about our monitoring their gear -- gotta love office politics -- and I had to have the server admins give the server's IP address as well as their default route when setting up their monitoring.) If a router went down, the Nagios alert rules made sure the network team got the alert, not the server admins whose systems were behind the downed network box.
I found it pretty nice to be able to have Nagios checking for "XXX" and "YYY". It was a pity when the company outsourced everything to a 3rd party data center provider and Nagios was replaced with something that was only set up to ping.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.