Discovering host issues via NRPE

[njg]

Hello,

I'm taking a look a NagiosXI and have performed a fresh installation on an Amazon AMI. The NagiosXI server details are as follows;

RHEL 6 64-bit
Installed version is 2014R2.0 performed via the Source Installer

The installation of the server itself seemed to work fine. However, I've installed the NRPE agent on a separate RHEL 6 64-bit server in AWS and when I try to add it via auto-discovery or by manually adding a NRPE client issues occur. The symptoms are;

- Client addition never seems to complete, the "Waiting for configuration" stage never finishes
- CPU goes to 100% due to a php process. The process is running "/usr/bin/php -q nagiosql_login.php"
- Under /usr/local/nagios/var the cmdsubsys.log is growing at an alarming rate, tailing the log the following error messages are being appended time after time...
PHP Warning: fgets() expects parameter 1 to be resource, boolean given in /usr/local/nagios/scripts/nagiosql_login.php on line 53
PHP Warning: feof() expects parameter 1 to be resource, boolean given in /usr/local/nagios/scripts/nagiosql_login.php on line 51

I've opened up ICMP and port 5666 between the hosts. Any ideas what is going wrong here?

I appreciate any help you can provide.

Nathan

[lmiltchev]

I've installed the NRPE agent on a separate RHEL 6 64-bit server in AWS...

How did you install NRPE? Did you follow our documentation?

http://assets.nagios.com/downloads/nagi ... _Agent.pdf

Run the following commands from the Nagios XI server and show us the output:

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H <client ip>
nmap <client ip> -p 5666

[njg]

Hi thanks for the reply.

Yes I did follow the document. However, I later found that NCPA didn't work either and showed exactly the same issue, which made me think that it was an issue with the server rather than a specific agent.

I think I may know the cause, the error pointing to the nagiosql_login script made me think back to when I first configured the server. I set a nagiosadmin password with a "<" symbol in it, afterwards I thought that may be that wasn't a great idea as the GUI subsequently replayed the set password back to me missing the "<" and everything after it, so I changed it.

I rebuilt the server and this time set an alphanumeric only password. Now NCPA works fine.

[tmcdonald]

The < and > characters are used in HTML to signify the tags, so it is possible they are being stripped somewhere.

So if that's all, are we clear to close the thread?