-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manish Kumar [07.02.2012 19:57]:
> The details of the issue is below:- > > *When nrpe service on HP-UX started using this command: * > > /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -d > > > *And from nagiosXI server:* > > [root@mmkndnagxi libexec]# ./check_nrpe -H 10.204.100.74 -n -p 5667 > -c check_mem -a '-w 65 -c 75' > > CHECK_NRPE: Socket timeout after 10 seconds. Does the nrpe daemon listen on port 5667? On our installations, it listens on 5666. On linux, I can check this with the netstat command (on the server) or with nmap (from remote), but I don't know about HP-UX's means. > *When nrpe service on HP-UX started using this command: * > > /usr/local/nagios/bin/nrpe -n -c /usr/local/nagios/etc/nrpe.cfg -d > > > *And from nagiosXI server:* > > [root@mmkndnagxi libexec]# ./check_nrpe -H 10.204.100.73 -t 60 -p > 5667 -c check_mem -a '-w 65 -c 75' > > CHECK_NRPE: Error - Could not complete SSL handshake. If you tell the server not to use SSL (with the -n option), you should tell it the client too (by using ./check_nrpe -H 10.204.100.73 -n -t ...). And... does the server listen to port 5667? ;-) HTH Werner -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8ykNQACgkQk33Krq8b42NUigCdHLmXqE6W+Vayjc6xqK4RO43u Kk8AnRoDNcUE3/4CdIRRDrhOcTPoCnJZ =TTcA -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
