Carole Gimenez wrote: > Hi all, > > As i have no response on nagiosplug-help mailing list, i permit to write > on this. > > The output of my check_disk appears in truncated manner in the nagios > interface web: > > DISK OK - free space: / 14659 MB (59% inode=99%): /dev 1860 MB (99% > inode=96%): /boot/efi 484 MB (97% inode=-): /usr/local 34678 MB (99% > inode=99%): /soleil1 40007 MB (32% inode=99%): /soleil3 56847 MB (55% > inode=99%): /soleil2 58028 MB (56% inode=99%): /soleil4 58048 MB (56% > inode=99%): /soleil5 25967 MB (25% inode=99%): /soleil6 73645 MB (71% ino > > Is there a solution to this problem? >
Yes, although the complexity of the solution depends on how you're running this check and how desperate you are to maintain the output as it is. If you aren't rabid about keeping the output, you can specify checks that check one partition at a time, which will make output a lot shorter and therefore not susceptible to running into the input limits in Nagios (or whatever transports might see the plugin along the way). That's the "doesn't matter how you run it" answer though. Is it being run via nrpe? If yes, you'll need to extend the NRPE protocol (there are presently discussions regarding this on nagios-devel@) to be able to send arbitrarily long output. What nagios version are you using? If 2.x or 2.x, you may have to increase the input limit in the header files and then re-compile Nagios. AFAIU, Nagios 3 already supports arbitrarily long input from plugins, so that shouldn't be a problem. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] 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
