<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=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> From the nrpe.cfg<o:p></o:p> <o:p> </o:p> # COMMAND ARGUMENT PROCESSING<o:p></o:p> # This option determines whether or not the NRPE daemon will allow clients<o:p></o:p> # to specify arguments to commands that are executed. This option only works<o:p></o:p> # if the daemon was configured with the --enable-command-args configure script<o:p></o:p> # option. <o:p></o:p> #<o:p></o:p> # *** ENABLING THIS OPTION IS A SECURITY RISK! *** <o:p></o:p> # Read the SECURITY file for information on some of the security implications<o:p></o:p> # of enabling this variable.<o:p></o:p> #<o:p></o:p> # Values: 0=do not allow arguments, 1=allow command arguments<o:p></o:p> <o:p> </o:p> dont_blame_nrpe=1<o:p></o:p> <o:p> </o:p> But as the commands are working remotely from the shell on the nagios-server, isn’t this already working? Is there a difference between sending the commands (as either the nagios or root user) from the nagios-server to beatrix (my monitored server)<o:p></o:p> <o:p> </o:p> So if the commands work that way, shouldn’t they work from the automated checks?<o:p></o:p> <o:p> </o:p> (Im pretty new to nagios)<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: Voigt, Thomas [mailto:Thomas.Voigt@netkom.de] Sent: 12 August 2009 14:29 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Check issues on Solaris with NRPE not dealing with ARGS<o:p></o:p> </div> </div> <o:p> </o:p> Hi Brian,<o:p></o:p> <o:p></o:p> Brian O'Mahony wrote:<o:p></o:p> <o:p></o:p> > So it looks like the args are not being passed to the solaris box. I just don’t understand what im doing wrong here. (I am also looking at check_mem and check_users but have forgon those until I get the issue with the ARGS resolved)<o:p></o:p> <o:p></o:p> did you read the following in your nrpe.cfg?<o:p></o:p> <o:p></o:p> ##########################################################################<o:p></o:p> # COMMAND ARGUMENT PROCESSING # This option determines whether or not the NRPE daemon will allow clients # to specify arguments to commands that are executed. This option only works # if the daemon was configured with the --enable-command-args configure script # option. # # *** ENABLING THIS OPTION IS A SECURITY RISK! *** # Read the SECURITY file for information on some of the security implications # of enabling this variable. # # Values: 0=do not allow arguments, 1=allow command arguments<o:p></o:p> <div> <o:p></o:p> </div> dont_blame_nrpe=0 ##########################################################################<o:p></o:p> <div> <o:p></o:p> </div> <div> Maybe you have to recompile nrpe with "./configure --disable-ssl --enable-command-args" ?<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> The other way is to work with static parameters in the nrpe.cfg file. If possible... <o:p></o:p> </div> <o:p> </o:p> -- Greetings from Weimar / Germany<o:p></o:p> Thomas Voigt<o:p></o:p> <o:p></o:p> </div> <pre> The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you. </pre></body> </html>