<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hi.<o:p></o:p> I have installed Nagios server on a linux machine successfully and am able to monitor Linux, Solaris and windows clients.<o:p></o:p> Lastly I have to monitor HP-UX clients also but am unable to do so.<o:p></o:p> <o:p></o:p> On the hp-ux machine I followed the following configuration steps-<o:p></o:p> <o:p> </o:p> <![if !supportLists]> <![endif]>1. Create a shared (NFS) filesystem location for the depot and plug-in files. Download the files from the Internet and save them to the shared location. <o:p></o:p> <![if !supportLists]> <![endif]>2. Prior to installing the nrpe client onto the HP-UX machines, prepare a generic nrpe.cfg file that can be copied onto and subsequently modified on each workstation. Have it located in the shared filesystem mentioned in the previous step. <o:p></o:p> <![if !supportLists]> <![endif]>3. Copy the appropriate depot, plug-in, and generic nrpe.cfg files to the /tmp directory of the workstation. <o:p></o:p> <![if !supportLists]> <![endif]>4. At the workstation console, log in as root or a sudoer account. <o:p></o:p> <![if !supportLists]> <![endif]>5. Invoke SAM. The pathname to the binary is /usr/sbin/sam <o:p></o:p> <![if !supportLists]> <![endif]>6. Select the Software Management option. <o:p></o:p> <![if !supportLists]> <![endif]>7. Select Install Software to Local Host <o:p></o:p> <![if !supportLists]> <![endif]>8. Change the Source Depot Type to Local Directory. <o:p></o:p> <![if !supportLists]> <![endif]>9. Under Source Depot Path, provide the full pathname to the depot file. For <o:p></o:p> example, if the depot file is in the /tmp directory, the pathname would be /tmp/nrpe-1.8-B.versionnumber.depot <o:p></o:p> <![if !supportLists]> <![endif]>10. Mark the depot for installation. SAM will first conduct an analysis of the file. Any errors or warnings should be corrected before proceeding. If there are no problems reported, the nrpe client can be installed onto the system. The location of the program will be /opt/nrpe. <o:p></o:p> <![if !supportLists]> <![endif]>11. Change to the /opt/nrpe directory and create the libexec directory using the mkdir command. <o:p></o:p> <![if !supportLists]> <![endif]>12. Move the plugin’s gzip file from the /tmp directory to libexec. <o:p></o:p> <![if !supportLists]> <![endif]>13. Run the gzip and tar commands to uncompress and extract the plugins. <o:p></o:p> <![if !supportLists]> <![endif]>14. Copy the generic nrpe.cfg file to the /opt/nrpe directory, and modify it to accommodate the configuration and services of the HP workstation. <o:p></o:p> <![if !supportLists]> <![endif]>15. Change to the /sbin/init.d directory. <o:p></o:p> <![if !supportLists]> <![endif]>16. Run the vi, or comparable, text editor utility to create a file called nrpe. The file will have the following text: /opt/nrpe/bin/nrpe –c /opt/nrpe/nrpe.cfg –daemon The above command will have the nrpe client run as a daemon on the workstation. The –c option has the binary file reference the nrpe.cfg file in the directory shown above. <o:p></o:p> <![if !supportLists]> <![endif]>17. Change the permissions of the newly created file to read and execute for all users via the chmod 555 nrpe command syntax. <o:p></o:p> <![if !supportLists]> <![endif]>18. Change the ownership of the /sbin/init.d/nrpe file to user bin, group bin via the chown bin:bin nrpe command. <o:p></o:p> <![if !supportLists]> <![endif]>19. Change to the /sbin/rc2.d directory. <o:p></o:p> <![if !supportLists]> <![endif]>20. Create a symbolic link to the /sbin/init.d/nrpe file using the following command: ln –s /sbin/init.d/nrpe Snumbernrpe <o:p></o:p> The number that is used can be anyone that is currently available. <o:p></o:p> <![if !supportLists]> <![endif]>21. Manually start the nrpe client program using the script that was created in the /sbin/init.d directory. <o:p></o:p> <![if !supportLists]> <![endif]>22. Modify the appropriate files on the Nagios server to accommodate the new client, and restart the application as necessary. <o:p></o:p> <o:p> </o:p> I have added the required entries on my linux server.<o:p></o:p> I start the daemon on hp-ux machine-<o:p></o:p> <o:p> </o:p> $ /opt/nrpe/bin/nrpe -c /opt/nrpe/nrpe.cfg -d<o:p></o:p> $ netstat -a|grep nrpe<o:p></o:p> tcp 0 0 *.nrpe *.* LISTEN<o:p></o:p> $ ps -ef|grep nrpe<o:p></o:p> nagios 21853 1 0 May 25 ? 0:55 bin/nrpe -n -c nrpe.cfg -d<o:p></o:p> nagios 950 929 1 12:36:05 pts/ta 0:00 grep nrpe<o:p></o:p> <o:p> </o:p> the logs show-<o:p></o:p> May 29 12:38:42 srirama nrpe[968]: Starting up daemon<o:p></o:p> May 29 12:38:42 srirama nrpe[968]: Listening for connections on port 5666<o:p></o:p> May 29 12:38:42 srirama nrpe[968]: Allowing connections from: 127.0.0.1,172.22.56.40<o:p></o:p> <o:p> </o:p> Where 172.22.56.40 is the IP address of nagios server.<o:p></o:p> <o:p> </o:p> But when I try to run nrpe on hp-ux machine I get the following error-<o:p></o:p> $ /opt/nrpe/libexec/check_nrpe -H localhost<o:p></o:p> CHECK_NRPE: Received 0 bytes. Are we allowed to connect to the host?<o:p></o:p> <o:p> </o:p> On the server I get the error-<o:p></o:p> CHECK_NRPE: Received 0 bytes from daemon.check the remote server logs for error messages.<o:p></o:p> <o:p> </o:p> I have tried whatever was possible but am unable to configure hp-ux for nagios. Only the ping check is working. Nrpe is not working,<o:p></o:p> Kindly help.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html> Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.