Nagios Support Forum

Hi,

I am testing NagiosXI.

Environment: Azure
CentOS for the NagiosXI host
Usually Ubuntu 16.04 for all monitored hosts.

I have installed the agent on the first host, and immediately upon creation of monitoring on Nagios, everything us listed as Down.

I understand that Ping is disabled in Azure, so when I created the monitoring for that host I UNselected ping.

Any thoughts or advice would be greatly appreciated. Thanks in advance!

I would verify that your Azure has port 5666 allowed in the security group.

Like they have ping disabled by default, likely port 5666 isn't open until you specifically allow it

https://docs.microsoft.com/en-us/azure/ ... art-portal

While all services are now listed as ok, the host continues to be listed as down: "CRITICAL - 10.3.0.29: rta nan, lost 100%" Is this a ping issue or something else?

InscrutableDude wrote:While all services are now listed as ok, the host continues to be listed as down: "CRITICAL - 10.3.0.29: rta nan, lost 100%" Is this a ping issue or something else?

It would be the Ping issue... However you can change the Host check to use something else if you like...meaning, a different type of check, maybe a http check? Depends on the server.

Ok, if that's viable I'll do it. As I mentioned in the question, the host being monitored is Ubuntu, the Nagios instance is on CentOS.

I an in the UI, and I can't see how to modify the actual services etc that are being monitored on a particular host. I see time intervals etc, but nothing like the original config screen that let me specify what to monitor.

Thanks for any directions.

If you're trying to change the Host Alive check, you can see this document:

https://assets.nagios.com/downloads/nag ... _In_XI.pdf

Or maybe you're requesting more general information, you wording doesn't make it entirely clear.

https://support.nagios.com/kb/article.php?id=539

Ok, i googled for a bit and found this which seems to have fixed the problem:

https://assets.nagios.com/downloads/nag ... _In_XI.pdf

I'll continue to chase down the problem with Azure, but this works for now.

Thanks all!

Was there anything further we can help with on this or is okay to close the thread?