Nagios Support Forum

I've noticed after I reboot a server and am monitoring things like uptime with NSClient++ that it returns:

CRITICAL: uptime: 21:40h

for example until it's been up for 24 hours. Any idea why a server that's up less than 24 hours is considered critical?

Does anyone know if you can use the rest calls to NSClient on a in this case Windows box without requiring credentials? Username or Password?

Thanks.

JR

I have a windows 2012 essentials server with a web front end that allows me to access my network remotely. I've been checking it with Nagios to verify the site is up and if not and doesn't come back after several checks, reboots the server. Recently I went from Essentials 2012 R2 to 2016. 2016 is st...

Think this is the term. So I have centos setup out of the box with just Nagios on it. When I go to the server name it pulls up servername/Nagios and there is my console. I am now trying to install a separate application on the same system which also has it's own websites. Don't want to break anythin...

yep

I had to go a bit more extreme or maybe having a vendor develop a 64-bit version is more extreme. I replaced the SATA drive in the enclosure with a SAS one and because it no longer was getting all these alerts about functionality the drive didn't support, the leak went away or was greatly reduced. JR

Here is what I ended up following:

http://www.howtovmlinux.com/articles/mo ... 4-x-x.html

Seemed to work without issue other than the home page defaulted back to home instead of services so have to manually fix that.

Thanks.

JR

After a lot of troubleshooting it comes down to LSI or Avago's storlib.dll file. I have removed all other SNMP based tools and this is the only one when I remove it the memory leak goes away. Plus the only one that activates the 32-bit SNMP environment on the server. All the others run under 64-bit ...

Think it's still leaking however I assume a program running on Nagios that makes a call to the server requesting the results of a particular MIB indentifier can't itself be the memory leak because the calling app is on the nagios server, not the server being monitored with the leak? Is that accurate...

Yeah been there done that as they say. No more updates. I guess the next logical thing to do is stop the SNMP checks for my intel raid and see if it goes away. Making the assumption that if no calls are being made the memory leak will not grow????

Thanks.

JR