NSClient++ Help (#1) - NSclient NSCA module Question. [SOLVED] (#495) - Message List

NSclient NSCA module Question. [SOLVED]

Hello everybody,

First of all i want to thanks and congratulate the NSClient++ team because NSClient++ is great and made my life easier !

I'm actually using the NSCA module of NSCLIENT++ and i having a strange problem. I want to send back 15 check result using the NSCA module but only get back 12 of them on my Nagios server.

In the nsclient.log it look like the check are done and sended and on my Nagios server he only receive 12 of those check according to the logs.

It's there a sort of limitation in the NSCA module of NSCLIENT ? Or in NSCA maybe ?

Thank you in advance.

See you.

Nitsuj

  • Message #1544

    Haha, the "team" would be me I guess... :P

    Anyways...

    Check the return length... NSCA supports something along the lines of 512 chars 8including performance data) which is not much...

    Michael Medin

    • Message #1545

      Hehe, thanks to you them !

      Check the return length... NSCA supports something along the lines of 512 chars 8including performance data) which is not much...

      Oh, that's the problem ! Sorry i wasn't aware of the nsca lenght ! Thanks for your quick feed back !

      • Message #1546

        Is it possible to tell to nsclient++ to send back the result in more them one return or something to work around this problem.

        Thanks for your feed back anyway !

        • Message #1547

          possibly...

          For NRPE you can extend the buffer and it should be possible to do the same for NSCA. Problem is it requires you to recompile "NSCA server" (or for NRPE: NRPE client) so it is not for everyone. When I added support for this for NRPE I added an option you could set and I guess I could something similar for NSCA (in the NSCA case I would probably suggest you run two NSCA servers on different ports one "standard length" and one "longer length").

          Let me know if you are interested, if so I will see if I can add this next weekend.

          I have plans to in either 0.4.x or 0.5.x add a "more generic" protocol which supports configurable lengths and such.

          Michael Medin

          • Message #1548

            I already had to recompile the NSCA server to get rid of a future timestamp error due to server located in different timezone. I quickly looked at NSCA source code to change the lenght, look's like it's only a constant to change, so it wont be a problem.

            But i dont know if i will have time to test this before at least two week's ,I'm really overbooked atm. So there is no rush for you to add this option in nsclient++.

            It's very kind from you Michael.

    • Message #1852

      hi,

      in which file can i find the return length?

      ty

      • Message #1878

        For NSclient++ in nsc.ini For NSCA (server) include/common.h

        The values need to be in sync.

        Michael Medin

Subscriptions