R: R: R: R: R: No output on check_snmp

Rob Blake rob.blake at gmail.com
Mon Mar 19 17:25:59 CET 2007


On 3/19/07, Marco Borsani <m.borsani at it.net> wrote:
>
>  Hi all
>
>
>
> The problem could be the pipe "|" in the return code of the command
> check_snmp ..
>
>
>
> OK – 18582*  |* *  *iso.3.6.1.4.1.9.9.147.1.2.2.2.1.5.40.6=18582
>
>
>
> What can I do not understand is WHY before, the pipe "|" was read and
> processed by nagios without any problem ?!?!?
>
>
>
> Is it a new features/bug for release 1.4.3 ?
>
>
>
> Marco
>


The pipe is not the problem. The pipe in the output of the plugin is the
delimeter for the plugin output and the plugin perfdata. This is a normal
feature of most Nagios plugins.

The problem is that Nagios cannot execute the plugin, so I would guess that
you have a configuration error somewhere or a permissions issue. The command
definition you posted earlier seems ok, but can you post an example service
definition. What does ls -l in the $USER1$ macro directory show?

Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070319/3ea7879a/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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


More information about the Users mailing list