<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=utf-8"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-GB link=blue vlink=purple> <div class=Section1> Hi Alen, Hi list,<o:p></o:p> <o:p> </o:p> Your issue is related to the knowledge about configuring and using sudo commands, not with Nagios.<o:p></o:p> Although, this knowledge is required for every Nagios plugins containing commands that need root permissions to be allowed to get executed.<o:p></o:p> I know the “check_mem.pl” plugin requires the same kind of configuration.<o:p></o:p> <o:p> </o:p> Setting up a sudo command means editing a user alias, a command alias, and then allow your user alias to run your command alias with some other user permission, ie the root user.<o:p></o:p> <o:p> </o:p> The file you want to edit is /etc/sudoers, edit it with your vi editor by typing as root : visudo<o:p></o:p> (should be located in /usr/sbin/ ) <o:p></o:p> On AIX, you need the “rpm.rte” AIX package, and the sudo rpm coming from your “AIX toolbox for Linux Applications” CD or <a href="ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/">ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/</a><o:p></o:p> <o:p> </o:p> Edit this file as follow : Be carefull about the syntax, it has to be strictly respected :<o:p></o:p> <o:p> </o:p> Add a user alias such as :<o:p></o:p> User_Alias SU_TO_NAGIOS_PLUGINS_USER = nagios<o:p></o:p> Make sure you are using a tabulation between User_Alias and the alias name, also make sure the U and A of User_Alias are uppercase.<o:p></o:p> <o:p> </o:p> Add a command alias such as :<o:p></o:p> Cmnd_Alias SU_TO_NAGIOS_PLUGINS = /usr/local/nagios/current/libexec/tsmonitor db<o:p></o:p> (seems your path uses nagios instead of “nagios-plugins”)<o:p></o:p> Again, make sure you are using a tabulation between Cmnd_Alias and the alias name, and that the C and A of Cmnd_Alias are uppercase.<o:p></o:p> <o:p> </o:p> Then add the authorization such as :<o:p></o:p> SU_TO_NAGIOS_PLUGINS_USER ALL = NOPASSWD: SU_TO_NAGIOS_PLUGINS<o:p></o:p> This line will let the command “/usr/local/nagios/current/libexec/tsmonitor db “ run with root permissions.<o:p></o:p> <o:p> </o:p> Save and exit, AIX will let you know if you have a syntax issue in your /etc/sudoers file, if this is the case, edit the file again to fix it.<o:p></o:p> <o:p> </o:p> Now you can check user Nagios gained this permission by entering :<o:p></o:p> su – nagios –c sudo –l<o:p></o:p> <![if !supportLists]>- <![endif]>sudo –l (Lower L option to list your configured sudo commands)<o:p></o:p> <![if !supportLists]>- <![endif]>su – nagios –c (to run the following command using nagios identity)<o:p></o:p> you should see something like :<o:p></o:p> User nagios may run the following commands on this host:<o:p></o:p> (root) NOPASSWD: /usr/local/nagios/current/libexec/tsmonitor db<o:p></o:p> <o:p> </o:p> Which means user nagios may run :<o:p></o:p> sudo /usr/local/nagios/current/libexec/tsmonitor db<o:p></o:p> <o:p> </o:p> Now you have to use this sudo command in your nrpe.cfg such as :<o:p></o:p> command[tsmonitor_db]=sudo /usr/local/nagios/libexec/tsmonitor db<o:p></o:p> <o:p> </o:p> Hope this helps!!<o:p></o:p> <o:p> </o:p> Cheers,<o:p></o:p> <o:p> </o:p> Quentin Marquez<o:p></o:p> Unix / linux admin<o:p></o:p> Global Technology Services<o:p></o:p> Experian - Monaco<o:p></o:p> Tel : (377) 97 98 54 27<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Grizonic Alen [mailto:Alen.Grizonic@comparex.si] Sent: 29 March 2010 09:48 To: Marquez, Quentin Subject: RE: [Nagios-users] Nagios NRPE: Unable to read output<o:p></o:p> </div> </div> <o:p> </o:p> Thank you very much!<o:p></o:p> <o:p> </o:p> I changed the command in my nrpe.cfg file, but now looks like there is something else blocking the response.<o:p></o:p> Even with a log timeout I get ... CHECK_NRPE: Socket timeout after XY seconds.<o:p></o:p> <o:p> </o:p> I would think of a firewall blocking, but the other commands work and run very fast ... and apparently there is no firewall on that AIX machine.<o:p></o:p> <o:p> </o:p> p.s. Maybe I missed something out ... what did you mean with »you would need to setup a sudo command«?<o:p></o:p> <o:p> </o:p> Just change the command to ...<o:p></o:p> <o:p> </o:p> command[tsmonitor_db]=sudo /usr/local/nagios/libexec/tsmonitor db<o:p></o:p> <o:p> </o:p> ... or something else?<o:p></o:p> <o:p> </o:p> <div> If you have any idea I wuold be more than thankful!<o:p></o:p> <o:p> </o:p> But really J<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Best regards, <o:p></o:p> <o:p> </o:p> Alen<o:p></o:p> <o:p> </o:p> </div> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Marquez, Quentin [mailto:Quentin.Marquez@experian.com] Sent: Friday, March 26, 2010 3:57 PM To: Nagios Users List Subject: Re: [Nagios-users] Nagios NRPE: Unable to read output<o:p></o:p> </div> </div> <o:p> </o:p> Hi Alen,<o:p></o:p> <o:p> </o:p> I don’t know much about this plugin, but it looks like your command requires root permission.<o:p></o:p> Thus you would need to setup a sudo command to run /usr/local/nagios/libexec/tsmonitor db<o:p></o:p> Then use your new sudo command in your nrpe.cfg :<o:p></o:p> command[tsmonitor_db]=sudo /usr/local/nagios/libexec/tsmonitor db<o:p></o:p> <o:p> </o:p> Cheers,<o:p></o:p> Quentin<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Grizonic Alen [mailto:Alen.Grizonic@comparex.si] Sent: 26 March 2010 15:17 To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Nagios NRPE: Unable to read output<o:p></o:p> </div> </div> <o:p> </o:p> Hello!<o:p></o:p> <o:p> </o:p> I know that this post is nothing new, but I still didn't find any solution for it.<o:p></o:p> <o:p> </o:p> I am working on a AIX 5.3 machine with NRPE running under inetd.<o:p></o:p> <o:p> </o:p> On the local AIX machine the command for TSM works fine ...<o:p></o:p> <o:p> </o:p> # ./tsmonitor db<o:p></o:p> db - database utilization 0%, OK<o:p></o:p> <o:p> </o:p> But when I start if from the Nagios server ... <o:p></o:p> <o:p> </o:p> # ./check_nrpe -n -t 60 -H 172.21.100.121 -c tsmonitor_db<o:p></o:p> NRPE: Unable to read output<o:p></o:p> <o:p> </o:p> or from the AIX machine with the NRPE I get ...<o:p></o:p> <o:p> </o:p> # ./check_nrpe -n -t 60 -H localhost -c tsmonitor_db<o:p></o:p> NRPE: Unable to read output<o:p></o:p> <o:p> </o:p> The nrpe.cfg file is properly configured with the commands<o:p></o:p> <o:p> </o:p> command[tsmonitor_db]=/usr/local/nagios/libexec/tsmonitor db<o:p></o:p> command[check_disk/]=/usr/local/nagios/libexec/check_disk -w 20 -c 10 -p /<o:p></o:p> <o:p> </o:p> Where check_disk/ works fine, but tsmonitor_db NOT!<o:p></o:p> <o:p> </o:p> Any suggestions?<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Best regards, <o:p></o:p> <o:p> </o:p> Alen<o:p></o:p> This e-mail has come from Experian, the only business to have been twice named the UK's 'Business of the Year’ <o:p></o:p> <o:p></o:p> ===================================================================================<o:p></o:p> Information in this e-mail and any attachments is confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other binding commitment through the use of this electronic communication unless it is issued in accordance with the Experian Limited standard terms and conditions of purchase or other express written agreement between Experian Limited and the recipient. <o:p></o:p> Although Experian has taken reasonable steps to ensure that this communication and any attachments are free from computer virus, you are advised to take your own steps to ensure that they are actually virus free. <o:p></o:p> Companies Act information:<o:p></o:p> Registered name: Experian Limited <o:p></o:p> Registered office: Landmark House, Experian Way, NG2 Business Park, Nottingham, NG80 1ZZ, United Kingdom<o:p></o:p> Place of registration: England and Wales <o:p></o:p> Registered number: 653331<o:p></o:p> <o:p></o:p> </div> </body> </html>