NSClient++ Help (#1) - ExternalCommands?: failed to create process in UNKNOWN (#948) - Message List

ExternalCommands?: failed to create process in UNKNOWN

Hello,

Sometimes we had some alarms with message ExternalCommands?: failed to create process ... The severity of this message is UNKNOWN. Is-it possible to change this severity to CRITICAL ?

Regards, Samuel Mutel.

  • Message #2506

    I think it is not due to configuration because it is not in UNKNOWN all the time. We have a lot of alarm due to the system himself:

    19: The media is write protected. 1450: Insufficient system resources exist to complete the requested service. 1455: The paging file is too small for this operation to complete.

    The difficulty is:

    • These kind of alarm should be CRITICAL
    • The alarms regarding the configuration should be UNKNOWN

    Regards, Samuel Mutel.

    • Message #2510

      I think you can use CheckHelpers for this there should be some rewrite thing there. It is also possible with both Lua and PythonScripts? as well as a wrapper batchfile...

      Perhaps Is should make it configurable as well?

      The idea is to extend external script for 0.4.2 to support a nummber of new configuration options as well as templates (much like targets and schedules).

      Michael Medin

Subscriptions