Brandino Andreas wrote:
Hi Rene, yes all plugins have 755 permissions. The plugins have the same permissions (owned by the root and 755) as the working one's.Tuesday, September 5, 2006, 6:44:38 PM, you wrote:Hi Andreas.Am Dienstag, 5. September 2006 16:39 schrieb Andreas Brandino:i am using Suse 10.0 with nagios 1.2.x All perl plugins i try to use return "No output" message. However, all other plugins work just fine. When i run the plugins from command line (as "root" or "daemon") work without problem. Using perl full path in front of the plugin (checkcommands.cfg) still doesnt make any difference. I think this has to do with perl on my system. Any idea?Please check wether all plugings have execution rights for everyone (0755). As far as I remember the SuSE installation didn't set these properly.Rene<> --- - - - --- <> Brandino Andreas [EMAIL PROTECTED] <> --- - - - --- <> Are you by any change using webinject? On the off chance that you are, read on: I had this problem at the exact time that you first posted the issue. My fix was to cd dir && ./webinject.pl ....... which worked fine. Otherwise I kept getting this no output in the web interface which was really bugging me. webinject doesn't handle the full path for the config or test file. In fact it exits 0 which looks like a success but really it fails to open the file(s). You'll see that if you use normal report type. hope that helps. -- Hari Sekhon |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Nagios-users mailing list Nagios-users@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