[Nagios-users] Antwort: Re: NSCA and long output
Looking at the NSCA sources, common.h has: #define MAX_PLUGINOUTPUT_LENGTH 512 I'm guessing that's the issue right there. The first thing I'd try is to bump that up to 4096, and recompile send_nsca and nsca. I haven't looked very carefully at the source or tried this myself, but it seems like a good place to start. Mike Yes that's right. I use this since a couple of days. But you have to check the value in nagios source code (include/nagios.h) too. It muste be at least the same or higher. Thomas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
Re: [Nagios-users] Antwort: Re: NSCA and long output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/05/08 01:12 AM, Thomas Borger wrote: Looking at the NSCA sources, common.h has: #define MAX_PLUGINOUTPUT_LENGTH 512 I'm guessing that's the issue right there. The first thing I'd try is to bump that up to 4096, and recompile send_nsca and nsca. I haven't looked very carefully at the source or tried this myself, but it seems like a good place to start. Mike Yes that's right. I use this since a couple of days. But you have to check the value in nagios source code (include/nagios.h) too. It muste be at least the same or higher. A value of 4096 will likely work well in Linux as pipes guarantee that this many bytes can be written at once in that OS. POSIX requires 512 bytes so this may vary between operating systems (PIPE_BUF should tell you what the limit is). Anything larger will likely cause fragments to be lost and/or interleaved (the latter can happen if you have multiple writers at the same time). See pipe(7) for more details. The proper fix would bu using PROCESS_FILE instead to load long output. Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIPg436dZ+Kt5BchYRAjWNAKDmDsCnTFCAoiuapdy/KKShPyaA0wCffry8 H4pbn7Iv+aqaj1Lp+kIrJjs= =cEsA -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
[Nagios-users] Antwort: Re: NSCA and long output
On May 28, 2008, at 11:54 AM , Aaron Mills wrote: What I'm really trying to get is multi-line output. Nagios/NRPE supports this (v3.x) e.g.: TEXT OUTPUT | OPTIONAL PERFDATA LONG TEXT LINE 1 LONG TEXT LINE 2 This works for NRPE, but not with NSCA, since NSCA can only take a single line as an argument. What I'm trying to achieve is sending process monitoring data back passively like so: PROCS OK: Proc1: 3 processes running Proc2: 1 process running Proc3: 1 process running Any ideas? Hi Marc, I have a simila requirement here. As i refer before, i have change the two values in common.h (NSCA) and nagios.h (Nagios) to synchronize the MAX_INPUT Buffers to 7168 Byte. Then I recompiled all NSCA-Versions (Linux and Windows), Nagios and wrote my own plugins for some checks which produce one output line like: check test OK = host aBRhost bBRhost cBRhost dBR The Nagios-GUI interpret the HTML-Tag and show your multiple lines if the corresponding switch in cgi.cfg is set. (escape_html=0) In my case are round about 15 lines possible. best regards Thomas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
