Announcement

Collapse
No announcement yet.

Oreon behaving very weird on file generation

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

  • Oreon behaving very weird on file generation

    I'm running Oreon 1.3.2 with nagios 2.5 to monitor 53 hosts with 235 checks. It was going good, but now, everytime i add a host, it autoweirdmatically add checks from other hosts to that new host. I hope oreon doesn't mess up the config files for good, that i spent some time on


    Here what oreon shows after doing a nagios restart via oreon:

    Code:
    Nagios 2.5
    Copyright (c) 1999-2006 Ethan Galstad (http://www.nagios.org)
    Last Modified: 07-13-2006
    License: GPL
    
    Reading configuration data...
    
    Error: Could not add duplicate serviceextinfo entry for service 'JetDirect' on host 'Link_Internet'.
    Error: Could not allocate memory for serviceextinfo list to add extended info for service 'JetDirect' on host 'Link_Internet'.
    Error: Could not register extended service information (config file '/usr/local/oreon/filesGeneration/nagiosCFG/serviceextinfo.cfg', starting on line 1425)
    
    ***> The name of the main configuration file looks suspicious...
    
    Make sure you are specifying the name of the MAIN configuration file on
    the command line and not the name of another configuration file. The
    main configuration file is typically '/usr/local/nagios/etc/nagios.cfg'
    
    ***> One or more problems was encountered while processing the config files...
    
    Check your configuration file(s) to ensure that they contain valid
    directives and data defintions. If you are upgrading from a previous
    version of Nagios, you should be aware that some variables/definitions
    may have been removed or modified in this version. Make sure to read
    the HTML documentation regarding the config files, as well as the
    'Whats New' section to find out what has changed.
    
    
    cgi.cfg - movement OK
    checkcommands.cfg - movement OK
    contactgroups.cfg - movement OK
    contacts.cfg - movement OK
    dependencies.cfg - movement OK
    escalations.cfg - movement OK
    hostextinfo.cfg - movement OK
    hostgroups.cfg - movement OK
    hosts.cfg - movement OK
    misccommands.cfg - movement OK
    nagios.cfg - movement OK
    resource.cfg - movement OK
    serviceextinfo.cfg - movement OK
    servicegroups.cfg - movement OK
    services.cfg - movement OK
    timeperiods.cfg - movement OK
    
    Running configuration check... FAILED! Restart aborted. Check your Nagios configuration.

    As you can see, it's adding the "jetdirect" check on the host "link_internet". This the second time stuff like this happens. I have to manually remove those checks from the new host of course. Why this happens? Oreon bug?

  • #2
    This just happened to me today as well:
    Reading configuration data...

    Error: Could not add duplicate serviceextinfo entry for service 'Ping' on host 'SCisco1/2_LATA228_ATM'.
    Error: Could not allocate memory for serviceextinfo list to add extended info for service 'Ping' on host 'SCisco1/2_LATA228_ATM'.
    Error: Could not register extended service information (config file '?', starting on line 1936278355)

    As a workaround, I've simply commented out the include in nagios.cfg (We don't use the extended infos for anything), but it would be nice to know if there is a real way to fix this.

    Comment


    • #3
      Has anyone found an answer for this? It seems like the default serviceextinfo.cfg syntax it generates is incorrect ( why does it generate it when I don't list any service extended infos anyways? ).
      Last edited by SeanFromIT; 23 October 2007, 22:40. Reason: update

      Comment


      • #4
        Solution is in hosts belonging to more than one host group, and then the same service being applied to more than one of the host groups that the host is in. For example, I fixed my issue (same as obmij) by removing the Ping service from host groups and applying it to hosts instead.
        Last edited by SeanFromIT; 31 October 2007, 20:50.

        Comment

        Working...
        X