add a
2>&1
to your command line to redirect stderr to stdout. Then you will see the error message in nagios.
Regards,
Sven
This is the webinject list, not nagios. Please get help about how to configure and debug your Nagios installation
on the nagios-users list or in any nagios forum. But since your webinject runs fine when executed by hand, i
don't think its a webinject problem.
Sven
On 09/11/10 16:55, Lipstars wrote:
> Well, since nagios reports work perfectly with Webinject 1.41, it
> could may be a problem with Webinject 1.51 , that's why i made a
> thread...
>
> Same configuration, same rights, same location, I can't see how it
> could be a nagios problem... but maybe i'm wrong.
>
> Could it be possible to upload your "Webinject.pl" v.1.52 and v1.53
> please ?
I uploaded the full tar.gz and a prebuild check_webinject to:
http://labs.consol.de/nagios/check_webinject/
If it works from the command line, it should work with nagios. You can test it as
your nagios user with:
env -i ./check_webinject
Regards,
Sven
did you try that as your nagios user?
On 09/13/10 15:57, Lipstars wrote:
>> env -i ./check_webinject
If that works, can you show me your command definition?
Regards,
Sven
Use absolute paths for your config and testcases.
And change your command_line to
command_line $USER1$/Webinject/check_webinject $ARG1$ -c $ARG2$ 2>&1
Sven
Troubleshooting
Beware that if you run WebInject with a user other than the default 'nagios', some files may be created with this user. Nagios will obtain an error if it can't write to these files. So give the ownership of these files to 'nagios' or remove them and run WebInject again as the 'nagios' user (the one declared in nagios.cfg). If you have file ownership issues, this will show up in Nagios with an error like "Return code of 13 for check of service ... on host ... was out of bounds"
Make sure the 'nagios' user has sufficient rights to execute webinject.pl, and to write to output files http.log, result.xml, and result.html. (if you don't have this setup correctly, you will get back invalid return codes from the plugin)
I am currently adding some fixes and will release a 1.54 soon. I will add proper error messages for this too.
Sven
On 09/14/10 12:27, Lipstars wrote:
> Yea i already saw that on the Webinject site. But as I said it,
> everything works great with Webinject 1.41. Then I installed Webinject
> 1.53 under the nagios user, so he should have enough rights. I also
> checked again and again if he had the good rights on each files/
> directories and everything seems to be OK... so maybe the error isn't
> correctly handled by the new Webinject I don't know :(
could you please try the attached new version? If it works for you, i will create
a new release. At least there should be a more useful error message with this
version.
Sven
>> 20KAfficherT�l�charger
Only if you use the check_webinject. Not when you use the webinject.pl.
Have you tried to set the report_type in your config.xml?