Announcement

Collapse
No announcement yet.

Failure to upload/import Nagios checkcommands.cfg

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Failure to upload/import Nagios checkcommands.cfg

    I have a fully working installation of Nagios 2.0 with 300+ hosts and 300+ services under Centos 4.3. My config is held using a tool called nagiosQL (php + mysql) which I am trying to replace with Oreon.

    I have successfully installed Oreon (documentation could be better - many problems but got there in the end) and am now trying to import my working
    Nagios cfg files. I think I understand from other forum posts that I need to
    load my checkcommands.cfg and misccommands.cfg files individually first
    and then the rest as an archive.

    Problem is that the load procedure does not recognise any of my command
    definitions in checkcommands.cfg and just says 0 entries found. I have played with the format of the file but still get the same problem. I suspect
    this could be because nagiosQL generates cfg without any templates and your loading routines expect them to be there ?

    Any help you can give would be gratefully received !

  • #2
    one cheat is to put a blank line first of all the file you want to import

    Don't know if it can help you :idea:
    Intel(R) Xeon(TM) CPU 3.4GHz - MemTotal : 1034476 kB
    Centreon 2.4.1 - Nagios 3.2.1 - Nagios Plugins 1.4.15 - Manubulon Plugins tuné
    Fedora Core 5 - 2.6.20-1.2320

    Comment


    • #3
      Thanks for the reply but I am afraid it was not as simple as that ...

      Have finally figured this out after much grief and pain
      The load routine expects the following format for checkcommands at least

      define<space>command{
      \tcommand_name\tsomecommandname
      \tcommand_line\tsomecommandline
      <space><space><space>\t}


      I am not impressed - I hope it gets better from here on in !

      Comment


      • #4
        Further update for anybody who might come across this ...

        It applies to all files and not just checkcommands.cfg
        and occurs because the regular expressions used for
        parsing the lines containing define are limited to
        allow only a single space after the define keyword rather
        than any number of whitespace characters as used elsewhere.

        I will attempt to raise this as a bug if I am allowed.

        Comment


        • #5
          Put it in the bugtrack :

          http://bugs.oreon-project.org/

          / {1,}/ :lol:
          Intel(R) Xeon(TM) CPU 3.4GHz - MemTotal : 1034476 kB
          Centreon 2.4.1 - Nagios 3.2.1 - Nagios Plugins 1.4.15 - Manubulon Plugins tuné
          Fedora Core 5 - 2.6.20-1.2320

          Comment

          Working...
          X