Page 1 of 1

Nagios LocalHost issue - connection refused

Posted: Tue Apr 25, 2017 10:34 am
by caterpillartce
Hello,

We use Nagios to monitor our application servers, which are all on Windows. And once in a while if we get "connection refused" error with those servers being monitored, we would start/restart NSCLIENT service and problem would be fixed. But this time the connection refused error is with Nagios server itself, which is Linux. Not familiar with Linux server, I am not sure how to fix the problem. Nagios otherwise functions fine and the monitoring for our application servers is still working properly, it is just the monitoring of Nagios server itself is having issue (see below for the alert email message). Thanks for the help!

-------------------------------

***** Nagios XI Alert *****

Nagios has detected a problem with this service.

Notification Type: PROBLEM

Service: Drive D: Disk Usage
Host: localhost
Host Description: localhost
State: CRITICAL
Info:
connect to address 127.0.0.1 and port 12489: Connection refused

Re: Nagios LocalHost issue - connection refused

Posted: Tue Apr 25, 2017 10:46 am
by caterpillartce
Also to clarify, only c: drive, d: drive and uptime monitoring show "connection refused"; everything else on localhost - http, ping, ssh, current load, current users, ... are all good.

Re: Nagios LocalHost issue - connection refused

Posted: Tue Apr 25, 2017 11:00 am
by tgriep
The Nagios XI server (localhost) is running linux but the checks you ran against it are only for Windows systems so they will never work as the server does not have C or D drives, etc..
What you need to do is to remove those checks that are failing by logging in to the XI GUI and going to the Core Config Manager > Services menu, search for those checks and delete them.
After deleting them, Apply the Configuration and the error should be gone.

Re: Nagios LocalHost issue - connection refused

Posted: Tue Apr 25, 2017 11:11 am
by caterpillartce
yes, thank you! I just found out a coworker mistakenly added localhost to a windows server group, which has all those monitoring services...

this thread can be closed.,

Thanks for the help!