Results 1 to 9 of 9

Thread: [RESOLVED] centreon_status: centengine OK shinken KO

  1. #1
    Junior Member
    Join Date
    Mar 2013
    Posts
    6

    [RESOLVED] centreon_status: centengine OK shinken KO

    I have been tasked to install Centreon: to take advantage of SNMPBooster, I am trying to swap the Merethis engine with Shinken.

    Centreon is ok with its native (cent)engine but doesn't acknowledge the data that Shinken places in the NDO database centreon_status and in the perfdata file var/service-perfdata

    Shinken 1.2.4
    Centreon (2.4.0 and 2.4.3 -on different machines-)
    Centos 6.3

    Shinken, Skonf/WebUI works fine: it takes the config files from Centreon happily, hosts and services. It displays them as expected

    NDO seems ok as the tables nagios_servicestatus and nagios_hoststatus are updated.

    ToNdodb_Mysql
    host localhost
    port 3306
    database centreon_status
    prefix nagios_
    user centreon
    password pwd

    Service-Perfdata also populates the file in var/service-perfdata without a hitch.

    It's the last leg - Centreon picking up the data from NDO DB and perdata file - that is not OK for Shinken.

    Would those who know suggest a way to debug this?

    Thanks in advance

    PS1: where did the "-z centreon" option go?

    PS2: As part of the work requirements, I prepared a document with screenshots to install Centreon from RPM packages with SSL, LDAP in some cut-and-pastes. We tested successfully the procedure described at the shop. I'll update with Shinken integration when done.

  2. #2
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: centreon_status: centengine OK shinken KO

    Launch the broker daemon in debug mode, you will have far more debug logs, especially for this NDO module

    For the -z, Shinken and Centreon are less and less compatible, and the centreon-broker change from Centreon will not help this. I think this mix won't be possible in the next years
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3
    Junior Member
    Join Date
    Mar 2013
    Posts
    6

    Re: centreon_status: centengine OK shinken KO

    The debug of the Centreon broker seems to show that using central-broker-sql-master-failover fails for shinken, (1st paragraph) but succeeds for centengine (2nd paragraph).

    Are there further levels or directions of debugging I could use? ???

    central-broker-sql-master-failover has the vanilla definition under Configuration > Centreon > Configuration > central-broker-master > Outputs

    ----
    Output 4 - File
    Name* central-broker-sql-master-failover
    File path* /var/lib/centreon-broker/central-broker-sql-master.retention
    Retry interval
    Failover name
    Serialization protocol NDO Protocol
    Buffering timeout
    Maximum size of file
    Compression (zlib) [x] No [] Yes
    Compression level
    Compression buffer size

    shinken: NDO fails
    ------------
    debug: NDO: reading event
    info: file: end of last file '/var/lib/centreon-broker/central-broker-sql-master.retention' reached, closing and erasing file
    debug: failover: could not get event from failover thread central-broker-sql-master-failover (0x1e36690)
    info: failover: requesting failover thread central-broker-sql-master-failover termination
    info: failover: central-broker-sql-master-failover is performing an immediate shutdown
    debug: multiplexing: subscriber processing request in=false, out=true
    debug: multiplexing: 3 subscribers are registered after deletion
    info: failover: central-broker-sql-master-failover is exiting
    debug: failover: thread central-broker-sql-master-failover(0x1e36690) terminated
    info: failover: central-broker-sql-master-failover is restoring processing
    debug: multiplexing: subscriber processing request in=true, out=true
    debug: multiplexing: 3 subscribers are registered after reregistration
    info: failover: central-broker-sql-master-failover is buffering data before recursive read (0s)
    debug: failover: got event from normal source
    debug: storage: current transaction has 0 pending queries
    info: storage: committing transaction
    debug: failover: got event from normal source

    centengine: NDO succeeds
    -------------
    debug: NDO: reading event
    info: file: end of last file '/var/lib/centreon-broker/central-broker-sql-master.retention' reached, closing and erasing file
    debug: failover: could not get event from failover thread central-broker-sql-master-failover (0x15997d0)
    info: failover: requesting failover thread central-broker-sql-master-failover termination
    info: failover: central-broker-sql-master-failover is performing an immediate shutdown
    debug: multiplexing: subscriber processing request in=false, out=true
    debug: multiplexing: 3 subscribers are registered after deletion
    info: failover: central-broker-sql-master-failover is exiting
    debug: failover: thread central-broker-sql-master-failover(0x15997d0) terminated
    info: failover: central-broker-sql-master-failover is restoring processing
    debug: multiplexing: subscriber processing request in=true, out=true
    debug: multiplexing: 3 subscribers are registered after reregistration
    info: failover: central-broker-sql-master-failover is buffering data before recursive read (0s)
    debug: NDO: new event successfully generated
    debug: NDO: reading event
    debug: NDO: new event successfully generated
    debug: NDO: reading event

  4. #4
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: centreon_status: centengine OK shinken KO

    Sorry I don't understand: where does this logs came from? They are not from shinken broker.
    No direct support by personal message. Please open a thread so everyone can see the solution

  5. #5
    Junior Member
    Join Date
    Mar 2013
    Posts
    6

    Re: centreon_status: centengine OK shinken KO

    The are the logs of the Centreon broker process which live by default in

    /var/lib/centreon-broker/central-broker-master.log

    It shows the (non-)start of the NDO data pickup in each case.

    But I don't get it either: the process reading (the Centreon broker) and its configuration are the same. The database is the same (centreon_status: not sure about all the content at that instant).

    Is there an external trigger? A file, a pipe or a lock?

  6. #6
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: centreon_status: centengine OK shinken KO

    But centreon broker and shinken are just not compatible at all. Shinken got a ndo backend available, not a centreon-broker one (database is not the same). Sorry.
    No direct support by personal message. Please open a thread so everyone can see the solution

  7. #7
    Junior Member
    Join Date
    Mar 2013
    Posts
    6

    Re: centreon_status: centengine OK shinken KO

    I see my mistake: yes, I had installed in error centreon-broker.

    Now that it is gone, shinken is working perfectly well.

    On to SNMPBooster

    Thanks, Naparuba

  8. #8
    Administrator
    Join Date
    Dec 2011
    Posts
    278

    Re: centreon_status: centengine OK shinken KO

    For SnmpBooster the documentation and software should be all ready to go. No outstanding issues that I know of.

    Good luck and let me know how it goes.

    xkilian

  9. #9
    Junior Member
    Join Date
    Mar 2013
    Posts
    6

    [RESOLVED] Re: centreon_status: centengine OK shinken KO

    What is the forum to talk about issues like this one? Installation or some genDevConfig forums (which one)?
    ------------

    with genDevConfig, I get this error:

    # cd /usr/local/nagios/genDevConfig/util
    # ./genDevConfig -C public myserver
    Can't locate object method "parse_flags" via package "self" (perhaps you forgot to load "self"?) at ././../plugins/genConfig/NetSNMP.pm line 218.
    #

    until line 218 in ../plugins/genConfig/NetSNMP.pm is changed from
    self->parse_flags($opts->{pluginflags});
    to
    $self->parse_flags($opts->{pluginflags});

    ==================
    ObShinkenOnCentreon question:

    How to generate the hosts/services config filies via genDevConfig through Centreon

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •