Nagios Support Forum

Nagios Core 4.3.4

I had a major system issue and I rebuilt my entire hardware info structure

All My ESXI Hosts were rebuilt
All my VMs were intact since they all were stored on external NAS devices.

I have not run Nagios during that time.

Today finally I decided to start my Nagios Monitoring again.

I have Windows 2012 Windows 2016 Windows 2019 Servers Desktop Windows 10 7 and 8 Some Linux, Meraki Devices Cisco Devices Printers all monitored by Nagios.

I first ran this command
/usr/local/nagios/bin/nagios -vv /usr/local/nagios/etc/nagios.cfg

Was successful no errors

Then I started the Nagios service

All Windows servers/desktops have this issue
All my devices are ok just machine with nsclient which is 4.4.23

Any ideas

Thank you

Tom

I figured this out.
My Nagios Core 4 is running on Ubuntu 16.4 and when my system failure the server went down .
After a restart the ip address was using DHCP and used a different address then my nsclients ini file had.

After resetting the ip address on the Nagios server all but one server/desktop starting working fine.

The one desktop had a firewall issue that I resolved today.

All working great. Glad to be back up and monitoring again.


This issue can be locked.

Thank you

kwhogster wrote:I figured this out.
My Nagios Core 4 is running on Ubuntu 16.4 and when my system failure the server went down .
After a restart the ip address was using DHCP and used a different address then my nsclients ini file had.

After resetting the ip address on the Nagios server all but one server/desktop starting working fine.

The one desktop had a firewall issue that I resolved today.

All working great. Glad to be back up and monitoring again.


This issue can be locked.

Thank you

Glad to hear this is resolved!

Locking thread