Forum GLPI-Project

amine.boutarfa

Member

Registered: 2015-04-15

Posts: 10

Problème de gpli couplé à shinken "Shinken semble arrêté!"

En effet glpi m'affiche l'erreur" Pas d’événements trouvés dans les dernières minutes, donc Shinken semble arrêté! "  je l'ai redémarré pas mal de fois mais le message s'affiche toujours et toujours mon localhost sur debian en statut WARNING.

tail /var/log/shinken/arbiterd.log
[1429799517] INFO: [Shinken] [All] Trying to send configuration to receiver receiver-master
[1429799517] INFO: [Shinken] [All] Dispatch OK of configuration 0 to receiver receiver-master
[1429799517] INFO: [Shinken]  (http://localhost:7773/)
[1429799517] INFO: [Shinken] [All] OK, no more receiver sent need
[1429799517] INFO: [Shinken] [All] Trying to send configuration to receiver receiver-master
[1429799517] INFO: [Shinken] [All] Dispatch OK of configuration to receiver receiver-master
[1429799518] TIMEPERIOD TRANSITION: 24x7;-1;1
[1429799518] TIMEPERIOD TRANSITION: workhours;-1;1
[1429799518] TIMEPERIOD TRANSITION: none;-1;0
[1429799518] TIMEPERIOD TRANSITION: us-holidays;-1;0

amine.boutarfa

Member

Registered: 2015-04-15

Posts: 10

Re: Problème de gpli couplé à shinken "Shinken semble arrêté!"

tail -f /var/log/shinken/brokerd.log
[1429799518] INFO: [broker-master] Trying to init module: auth-cfg-password
[1429799518] INFO: [broker-master] [Cfg Password UI] Trying to initialize the CFG/Password auth
[1429799518] INFO: [broker-master] Trying to init module: SQLitedb
[1429799518] INFO: [broker-master] Try to open SQLite database at /var/lib/shinken/webui.db
[1429799518] INFO: [broker-master] Opened connection to SQLite database OK
[1429799518] INFO: [broker-master] I correctly loaded the modules: [auth-cfg-password,SQLitedb]
[1429799518] INFO: [broker-master] Connection OK to the receiver receiver-master
[1429799518] WARNING: [broker-master] Loading plugins: No module named helper
[1429799518] WARNING: [broker-master] Loading plugins: No module named bottle
[1429799518] WARNING: [broker-master] Loading plugins: No module named helper

amine.boutarfa

Member

Registered: 2015-04-15

Posts: 10

Re: Problème de gpli couplé à shinken "Shinken semble arrêté!"

 cat /etc/shinken/modules/ws_arbiter.cfg 

define module {
    module_name     ws-arbiter
    module_type     ws_arbiter
    host            0.0.0.0
    port            7760
    username        anonymous  
    #password        secret
}

cat /etc/shinken/modules/import-glpi.cfg 

define module {
    module_name     import-glpi
    module_type     import-glpi
    uri             http://localhost/glpi/plugins/webservices/xmlrpc.php
    login_name      glpi
    login_password  glpi
    tag             
}
cat /etc/shinken/modules/glpidb.cfg 

define module {
    module_name     glpidb
    module_type     glpidb
    host            localhost   
   database        glpi        
    user            shinkenbroker      
    password        ****
}

amine.boutarfa

Member

Registered: 2015-04-15

Posts: 10

Re: Problème de gpli couplé à shinken "Shinken semble arrêté!"

Il n'y a personne qui peut m'aider  ?

ddurieux

Plugins Dev

From: Propières, France

Registered: 2005-06-17

Posts: 7,521

Re: Problème de gpli couplé à shinken "Shinken semble arrêté!"

Tu n'as pas activé le module glpidb

amine.boutarfa

Member

Registered: 2015-04-15

Posts: 10

Re: Problème de gpli couplé à shinken "Shinken semble arrêté!"

Je l'ai dèja activé

 cat /etc/shinken/arbiters/arbiter-master.cfg 
define arbiter {
    arbiter_name    arbiter-master
    #host_name       node1       ; CHANGE THIS if you have several Arbiters
    address         localhost   ; DNS name or IP
    port            7770
    spare           0           ; 1 = is a spare, 0 = is not a spare

    modules         named-pipe,import-glpi,ws-arbiter

cat /etc/shinken/brokers/broker-master.cfg 

define broker {
    broker_name     broker-master
    address         localhost
    port            7772
    spare           0
    manage_arbiters     1   ; Take data from Arbiter. There should be only one
                            ; broker for the arbiter.
    manage_sub_realms   1   ; Does it take jobs from schedulers of sub-Realms?
    timeout             3   ; Ping timeout
    data_timeout        120 ; Data send timeout
    max_check_attempts  3   ; If ping fails N or more, then the node is dead
    check_interval      60  ; Ping node every N seconds

    modules         webui, glpidb 

Last edited by amine.boutarfa (2015-04-27 11:57:59)