Nagios Support Forum

I'm new to Nagios and trying to setup a monitoring environment specific to our Windows and Exchange environment.

I've setup a Nagios Core Version 4.2.0 server on Ubunto 16.04. I'm learning a lot but still have a long way to go.

The server seems to be running like it should but I can't get my first host to show up in it. I've loaded NSClient++ 0.5.2035 on a Windows 2012 server, loaded the modules, configured the Allowed Hosts in the nsclient.ini but can't seem to get the host to show up on the server.

The logging has been switched to debug and I'm getting messages like this. Let's say the Nagios Core Server is 192.168.0.30. Doesn't this look healthy? Wouldn't I see the Windows Host client in the Nagios portal under Hosts? I have restarted the Nagios process on the server.

I'm probably missing something silly. Thanks for your patience.

2018-02-15 14:52:01: debug:c:\source\master\modules\NRPEServer\NRPEServer.cpp:126: Allowed hosts definition: 127.0.0.1(255.255.255.255), 192.168.0.30(255.255.255.255)
2018-02-15 14:52:01: debug:c:\source\master\modules\NRPEServer\NRPEServer.cpp:127: Server config: address: :5666, ssl enabled: none, cert: C:\Program Files\NSClient++/security/certificate.pem (PEM), , dh: C:\Program Files\NSClient++/security/nrpe_dh_512.pem, ciphers: ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH, ca: C:\Program Files\NSClient++/security/ca.pem, options:
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:111: Binding to: [::]:5666(ipv6)
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:214: Attempting to bind to: [::]:5666(ipv6)
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:107: Binding to: 0.0.0.0:5666(ipv4), reopen: true, reuse: true
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:214: Attempting to bind to: 0.0.0.0:5666(ipv4)
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: NSCAClient
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: NSCAServer
2018-02-15 14:52:02: debug:c:\source\master\modules\NSCAServer\NSCAServer.cpp:94: Allowed hosts definition: 127.0.0.1(255.255.255.255), 192.168.0.30(255.255.255.255)
2018-02-15 14:52:02: debug:c:\source\master\modules\NSCAServer\NSCAServer.cpp:95: Starting server on: address: :5667, ssl enabled: none, cert: C:\Program Files\NSClient++/security/certificate.pem (PEM), , dh: C:\Program Files\NSClient++/security/nrpe_dh_512.pem, ciphers: ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH, ca: C:\Program Files\NSClient++/security/ca.pem, options:
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:111: Binding to: [::]:5667(ipv6)
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:214: Attempting to bind to: [::]:5667(ipv6)
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:107: Binding to: 0.0.0.0:5667(ipv4), reopen: true, reuse: true
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:214: Attempting to bind to: 0.0.0.0:5667(ipv4)
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: NSClientServer
2018-02-15 14:52:02: debug:c:\source\master\modules\NSClientServer\NSClientServer.cpp:86: Allowed hosts definition: 127.0.0.1(255.255.255.255), 10.192.0.7(255.255.255.255)
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:111: Binding to: [::]:12489(ipv6)
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:214: Attempting to bind to: [::]:12489(ipv6)
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:107: Binding to: 0.0.0.0:12489(ipv4), reopen: true, reuse: true
2018-02-15 14:52:02: debug:c:\source\master\include\socket/server.hpp:214: Attempting to bind to: 0.0.0.0:12489(ipv4)
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: PythonScript
2018-02-15 14:52:02: debug:c:\source\master\modules\PythonScript\python_script.cpp:93: boot python
2018-02-15 14:52:02: debug:c:\source\master\modules\PythonScript\python_script.cpp:108: Prepare python
2018-02-15 14:52:02: debug:c:\source\master\modules\PythonScript\python_script.cpp:115: init python
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: SMTPClient
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: Scheduler
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: SimpleCache
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: SimpleFileWriter
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: SyslogClient
2018-02-15 14:52:02: debug:c:\source\master\service\plugin_manager.cpp:227: Loading plugin: WEBServer
2018-02-15 14:52:02: debug:c:\source\master\modules\WEBServer\WEBServer.cpp:161: Using certificate: C:\Program Files\NSClient++/security/certificate.pem
2018-02-15 14:52:02: debug:c:\source\master\modules\WEBServer\WEBServer.cpp:185: Loading webserver on port: 8443
2018-02-15 14:52:02: debug:c:\source\master\service\NSClient++.cpp:317: NSClient++ - 0.5.2.35 2018-01-28 Started!
2018-02-15 14:52:02: debug:c:\source\master\service\NSClient++.cpp:441: Starting: DONE

I should add that earlier, the log file ended with this but still no host in the portal. I changed the ssl option to true and seemed to give the new results above.

2018-02-15 08:38:09: debug:c:\source\master\include\nrpe/server/protocol.hpp:92: Accepting connection from: 192.168.0.30, count=1
2018-02-15 08:38:18: error:c:\source\master\include\socket/connection.hpp:273: Seems we other end is not using ssl: unknown protocol
2018-02-15 08:38:18: error:c:\source\master\include\socket/connection.hpp:274: Please review the ssl option as well as ssl options in settings.

Can you show us the configuration files for the Windows host and it's services from your Nagios Core box? Also, show us any relevant commands and templates, that are used in your Windows config.

Have you restarted nagios after adding the host/services? Do you see any config errors when you verify the configuration?
Note: Modify the above command if the path to the nagios binary and/or the main config file is different.

Attaching the nsclient.ini on the Windows Host. I'll add the other information shortly.

I have restarted Nagios Process after running the NSClient++ service on the Host.

The only host below is the actual Nagios Core server.

Nagios Core 4.2.0
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-01-2016
License: GPL

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 8 services.
Checked 1 hosts.
Checked 1 host groups.
Checked 0 service groups.
Checked 1 contacts.
Checked 1 contact groups.
Checked 24 commands.
Checked 5 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 5 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check

It seems like that you have only one host and 8 services defined on your Nagios Core server.

Checking objects...
Checked 8 services.
Checked 1 hosts.

I would assume this is your localhost and it's services. You need to define your Windows host and it's services in order to see them in the GUI. Installing an agent on the remote Windows machine will allow you to monitor this hosts, but you still need to define it on the Nagios server. I hope this makes sense.

Please, review our official documentation on object definitions (host & service definitions in particular) here:
https://assets.nagios.com/downloads/nag ... tions.html

That was it! I thought I would see the client in Nagios Core before doing anything on the server.

Used this link to help as well: https://www.tecmint.com/how-to-add-wind ... ng-server/

Thank you very much.

Glad to hear it! Are we alright to close this up then?