Re: [Nagios-users] Probme in output of CHECK_MAILQ

[Andreas E. <ae...@op...>]

Nilesh wrote:
> Andreas Ericsson wrote:
> 
>> Nilesh wrote:
>>
>>> Tomasz Pilat wrote:
>>>
>>>> Hello Mr. linux admin,
>>>>
>>>> N> i enabled dont_blame_nrpe=1 and restarted xinetd again.
>>>> N> but still no luck ....
>>>>
>>>> N> same error ...
>>>>
>>>>> From nrpe.conf:
>>>>
>>>>
>>>>
>>>>
>>>> # 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.
>>>>
>>>>  
>>>>
>>> Ya did even that also.
>>> recompiled nrpe with --enable-command-args
>>> butnot luck
>>> i'm getting following error
>>> CHECK_NRPE: Error receiving data from daemon.
>>> for check_mailq only
>>> all other plugins are giving me proper output ..
>>>
>>
>> That probably means that check_mailq prints some output to stderr, 
>> which fucks NRPE up. What happens when you run the check_mailq command 
>> manually exactly as it's typed in the nrpe.conf file when logged in as 
>> the NRPE pseudo-user?
>> You can also try running it like this;
>>
>> $command > /dev/null
>>
> Here is the output of check_mailq while executing from the system from 
> where nrpe is running.
> 
> $ /usr/local/nagios/libexec/check_mailq -w 9 -c 10
> Program mode requires special privileges, e.g., root or TrustedUser.
> OK: mailq is empty|unsent=0;9;10;0
> 
> 
> and while redirecting output to /dev/null it gives
> 
> $ /usr/local/nagios/libexec/check_mailq -w 9 -c 10 >> /dev/null
> Program mode requires special privileges, e.g., root or TrustedUser.
> 

That's your problem right there. Your mailq command requires higher 
privileges. check_mailq (or mailq) prints this to stderr, and this 
causes nrpe to fail. Fix that and try again.

> 
> With Regards
> 
> Linux Admin
> 
>> ($command being the real command line here). If you get any output at 
>> all, that means you're getting some at stderr.
>>
>>> waitng for help
>>>
>>> regards
>>> linux admin
>>>
>>>
>>>
>>>
>>>> Maybe you should try this?
>>>>
>>>> Ponc
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> SF email is sponsored by - The IT Product Guide
>>>> Read honest & candid reviews on hundreds of IT Products from real 
>>>> users.
>>>> Discover which products truly live up to the hype. Start reading 
>>>> now. http://productguide.itmanagersjournal.com/
>>>> _______________________________________________
>>>> Nagios-users mailing list
>>>> Nag...@li...
>>>> 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
>>>>
>>>>
>>>>  
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> SF email is sponsored by - The IT Product Guide
>>> Read honest & candid reviews on hundreds of IT Products from real users.
>>> Discover which products truly live up to the hype. Start reading now. 
>>> http://productguide.itmanagersjournal.com/
>>> _______________________________________________
>>> Nagios-users mailing list
>>> Nag...@li...
>>> 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
>>>
>>
> 
> 

-- 
Andreas Ericsson                   and...@op...
OP5 AB                             www.op5.se
Lead Developer