NSClient++ Help (#1) - NSC.ini not including other config files? (#487) - Message List

NSC.ini not including other config files?

Hey folks,

I am trying something that I thought would be simple, but it doesn't seem to be working...

I have a local_defs.ini file on each NSClient++ machine, and I want to include it from the main NSC.ini. So, I placed the copy in the NSClient++ folder (the same as the NSC.ini file), and modified the NSC.ini file like so:

[includes]
;# The order when used is "reversed" thus the last included file will be "first"
;# Included files can include other files (be carefull only do basic recursive checking)
;
; myotherfile.ini
; real.ini
local_defs.ini

As best I can tell, this is the correct syntax? But, when I restart NSClient++, it does not recognize any of the commands I have placed in the local_defs.ini:

check_nrpe -H HOSTNAME -c check_openmanage UNKNOWN: No handler for that command

The local_defs.ini looks like:

command[check_openmanage]=check_openmanage.exe -p -b bat_charge=ALL/ctrl_fw=ALL/ctrl_driver=ALL --omreport F:\dellopenmanage\oma\bin\omreport.exe

(all on one line of course)

Am I misunderstanding what this can do? Am I just missing something?

Thanks much!

Benny

  • Message #1527

    Yes you are missing something.

    The included file is included "as an INI" file so it has to follow the INI syntax. Compleate with propper "headers" like so:

    [NRPE Commands]
    command[check_openmanage]=check_openmanage.exe -p -b bat_charge=ALL/ctrl_fw=ALL/ctrl_driver=ALL --omreport F:\dellopenmanage\oma\bin\omreport.exe
    

    (or whatever the heading is dont recall off the top of my head)

    Michael Medin

    • Message #1529

      Thank you thank you thank you. I was missing just that one detail... Now I'm finally able to have a single, standardized config file that I can distribute.

      Benny

Subscriptions