Forum GLPI-Project

caponcet

Member

Registered: 2015-07-13

Posts: 19

[résolu]Monitoring : page vierge

Bonjour et merci à toute l'équipe qui développe glpi et les plugins !

Voici ma config :

- debian 8.1
- apache 2.4
- php 5.6
- mysql-server 5.5
- glpi 0.85.4
- monitoring (0.85+1.3 prise sur le git et testé aussi avec la dernière version stable 0.85+1.0)
- webservices 1.5.0
- fusioninventory 0.85+1.1
- shinken 2.4 installé avec python-setuptools

Lors de l'installation de monitoring depuis le menu plugins, je n'ai pas de message d'erreur sur l'interface.

Quand je vais plugins/monitoring, j'ai une page vide (en me basant sur les anciennes versions, je devrais avoir la page avec le raccourci dashboard et le menu pour configurer les templates).

Les seuls logs que je trouve semblent concerner l'installation : (php-errors.log) :

2015-07-13 10:19:34 [2@debianglpi]
  *** PHP Warning(2): Invalid argument supplied for foreach()
  Backtrace :
  plugins/monitoring/inc/profile.class.php:398
  plugins/monitoring/install/install.php:58          PluginMonitoringProfile::initProfile()
  plugins/monitoring/hook.php:124                    pluginMonitoringInstall()
  inc/plugin.class.php:639                           plugin_monitoring_install()
  front/plugin.form.php:45                           Plugin->install()

Ce message d'erreur apparaît 17 fois dans le log lors de l'installation.

Pour info, je suivais la documentation de monsieur Durieux pour la version 0.84 de glpi et shinken 1.4, mais monitoring ne récupérait pas la gravité des sondes (qui restaient tout le temps en warning "connexion"), j'ai donc décidé d'installer la dernière version sans documentation.

Last edited by caponcet (2015-07-28 17:10:44)

caponcet

Member

Registered: 2015-07-13

Posts: 19

Re: [résolu]Monitoring : page vierge

J'ai finalement réussi à installer :
- debian 7.8
- glpi 0.84
- shinken 1.4

Maintenant je ré-essaie :
- debian 7.8
- glpi 0.85.4 + monitoring 0.85+1.3
- shinken 2.4

Ma page dashboard.php est toujours aussi vide et je ne trouve pas de message d'erreur.
J'ai du mal à trouver de la documentation (celle de la version 0.84 de glpi de David Durieux était bien)

J'ai installé 3 modules shinken : ws-arbiter , import-glpi, et glpidb.

Quelqu'un pour me mettre sur la piste ?

J'ai un message dans component.php : vous n'avez pas les droits pour réaliser cette action.

caponcet

Member

Registered: 2015-07-13

Posts: 19

Re: [résolu]Monitoring : page vierge

Voici mon log de démarrage de shinken (j'ai remplacé http par xxx pour pouvoir poster les logs)

==> /var/log/shinken/schedulerd.log <==
[1438007184] INFO: [Shinken] Trying to initialize additional groups for the daemon
[1438007184] INFO: [Shinken] Stale pidfile exists at invalid literal for int() with base 10: '' (/var/run/shinken/schedulerd.pid). Reusing it.
[1438007184] INFO: [Shinken] Opening xxx socket at xxx://0.0.0.0:7768
[1438007184] INFO: [Shinken] Initializing a CherryPy backend with 8 threads
[1438007184] INFO: [Shinken] Using the local log file '/var/log/shinken/schedulerd.log'
[1438007184] INFO: [Shinken] Printing stored debug messages prior to our daemonization
[1438007184] INFO: [Shinken] Successfully changed to workdir: /var/run/shinken
[1438007184] INFO: [Shinken] Opening pid file: /var/run/shinken/schedulerd.pid
[1438007184] INFO: [Shinken] Redirecting stdout and stderr as necessary..
[1438007184] INFO: [Shinken] We are now fully daemonized pid=6568
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] [scheduler] General interface is at: xxx://0.0.0.0:7768
[1438007184] INFO: [Shinken] Waiting for initial configuration
[1438007184] INFO: [Shinken] Starting xxx daemon

==> /var/log/shinken/pollerd.log <==
[1438007184] INFO: [Shinken] Shinken 2.4
[1438007184] INFO: [Shinken] Copyright (c) 2009-2014:
[1438007184] INFO: [Shinken] Gabes Jean (naparuba@gmail.com)
[1438007184] INFO: [Shinken] Gerhard Lausser, Gerhard.Lausser@consol.de
[1438007184] INFO: [Shinken] Gregory Starck, g.starck@gmail.com
[1438007184] INFO: [Shinken] Hartmut Goebel, h.goebel@goebel-consult.de
[1438007184] INFO: [Shinken] License: AGPL
[1438007184] INFO: [Shinken] Trying to initialize additional groups for the daemon
[1438007184] INFO: [Shinken] Stale pidfile exists at invalid literal for int() with base 10: '' (/var/run/shinken/pollerd.pid). Reusing it.
[1438007184] INFO: [Shinken] Opening xxx socket at xxx://0.0.0.0:7771
[1438007184] INFO: [Shinken] Initializing a CherryPy backend with 8 threads
[1438007184] INFO: [Shinken] Using the local log file '/var/log/shinken/pollerd.log'
[1438007184] INFO: [Shinken] Printing stored debug messages prior to our daemonization
[1438007184] INFO: [Shinken] Successfully changed to workdir: /var/run/shinken
[1438007184] INFO: [Shinken] Opening pid file: /var/run/shinken/pollerd.pid
[1438007184] INFO: [Shinken] Redirecting stdout and stderr as necessary..
[1438007184] INFO: [Shinken] We are now fully daemonized pid=6611
[1438007184] INFO: [Shinken] Starting xxx daemon

==> /var/log/shinken/reactionnerd.log <==
[1438007184] INFO: [Shinken] Shinken 2.4
[1438007184] INFO: [Shinken] Copyright (c) 2009-2014:
[1438007184] INFO: [Shinken] Gabes Jean (naparuba@gmail.com)
[1438007184] INFO: [Shinken] Gerhard Lausser, Gerhard.Lausser@consol.de
[1438007184] INFO: [Shinken] Gregory Starck, g.starck@gmail.com
[1438007184] INFO: [Shinken] Hartmut Goebel, h.goebel@goebel-consult.de
[1438007184] INFO: [Shinken] License: AGPL
[1438007184] INFO: [Shinken] Trying to initialize additional groups for the daemon
[1438007184] INFO: [Shinken] Stale pidfile exists at invalid literal for int() with base 10: '' (/var/run/shinken/reactionnerd.pid). Reusing it.
[1438007184] INFO: [Shinken] Opening xxx socket at xxx://0.0.0.0:7769
[1438007184] INFO: [Shinken] Initializing a CherryPy backend with 8 threads
[1438007184] INFO: [Shinken] Using the local log file '/var/log/shinken/reactionnerd.log'
[1438007184] INFO: [Shinken] Printing stored debug messages prior to our daemonization
[1438007184] INFO: [Shinken] Successfully changed to workdir: /var/run/shinken
[1438007184] INFO: [Shinken] Opening pid file: /var/run/shinken/reactionnerd.pid
[1438007184] INFO: [Shinken] Redirecting stdout and stderr as necessary..
[1438007184] INFO: [Shinken] We are now fully daemonized pid=6657

==> /var/log/shinken/pollerd.log <==
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Waiting for initial configuration

==> /var/log/shinken/reactionnerd.log <==
[1438007184] INFO: [Shinken] Starting xxx daemon

==> /var/log/shinken/brokerd.log <==
[1438007184] INFO: [Shinken] Shinken 2.4
[1438007184] INFO: [Shinken] Copyright (c) 2009-2014:
[1438007184] INFO: [Shinken] Gabes Jean (naparuba@gmail.com)
[1438007184] INFO: [Shinken] Gerhard Lausser, Gerhard.Lausser@consol.de
[1438007184] INFO: [Shinken] Gregory Starck, g.starck@gmail.com
[1438007184] INFO: [Shinken] Hartmut Goebel, h.goebel@goebel-consult.de
[1438007184] INFO: [Shinken] License: AGPL
[1438007184] INFO: [Shinken] [Broker] Using working directory: /var/run/shinken
[1438007184] INFO: [Shinken] Trying to initialize additional groups for the daemon
[1438007184] INFO: [Shinken] Stale pidfile exists at invalid literal for int() with base 10: '' (/var/run/shinken/brokerd.pid). Reusing it.
[1438007184] INFO: [Shinken] Opening xxx socket at xxx://0.0.0.0:7772
[1438007184] INFO: [Shinken] Initializing a CherryPy backend with 8 threads
[1438007184] INFO: [Shinken] Using the local log file '/var/log/shinken/brokerd.log'

==> /var/log/shinken/reactionnerd.log <==
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Waiting for initial configuration

==> /var/log/shinken/brokerd.log <==
[1438007184] INFO: [Shinken] Printing stored debug messages prior to our daemonization
[1438007184] INFO: [Shinken] Successfully changed to workdir: /var/run/shinken
[1438007184] INFO: [Shinken] Opening pid file: /var/run/shinken/brokerd.pid
[1438007184] INFO: [Shinken] Redirecting stdout and stderr as necessary..
[1438007184] INFO: [Shinken] We are now fully daemonized pid=6703
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Waiting for initial configuration
[1438007184] INFO: [Shinken] Starting xxx daemon

==> /var/log/shinken/receiverd.log <==
[1438007184] INFO: [Shinken] Shinken 2.4
[1438007184] INFO: [Shinken] Copyright (c) 2009-2014:
[1438007184] INFO: [Shinken] Gabes Jean (naparuba@gmail.com)
[1438007184] INFO: [Shinken] Gerhard Lausser, Gerhard.Lausser@consol.de
[1438007184] INFO: [Shinken] Gregory Starck, g.starck@gmail.com
[1438007184] INFO: [Shinken] Hartmut Goebel, h.goebel@goebel-consult.de
[1438007184] INFO: [Shinken] License: AGPL
[1438007184] INFO: [Shinken] [Receiver] Using working directory: /var/run/shinken
[1438007184] INFO: [Shinken] Trying to initialize additional groups for the daemon
[1438007184] INFO: [Shinken] Stale pidfile exists at invalid literal for int() with base 10: '' (/var/run/shinken/receiverd.pid). Reusing it.
[1438007184] INFO: [Shinken] Opening xxx socket at xxx://0.0.0.0:7773
[1438007184] INFO: [Shinken] Initializing a CherryPy backend with 8 threads
[1438007184] INFO: [Shinken] Using the local log file '/var/log/shinken/receiverd.log'
[1438007184] INFO: [Shinken] Printing stored debug messages prior to our daemonization
[1438007184] INFO: [Shinken] Successfully changed to workdir: /var/run/shinken
[1438007184] INFO: [Shinken] Opening pid file: /var/run/shinken/receiverd.pid
[1438007184] INFO: [Shinken] Redirecting stdout and stderr as necessary..
[1438007184] INFO: [Shinken] We are now fully daemonized pid=6746
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007184] INFO: [Shinken] Waiting for initial configuration
[1438007184] INFO: [Shinken] Starting xxx daemon

==> /var/log/shinken/arbiterd.log <==
[1438007185] INFO: [Shinken] Shinken 2.4
[1438007185] INFO: [Shinken] Copyright (c) 2009-2014:
[1438007185] INFO: [Shinken] Gabes Jean (naparuba@gmail.com)
[1438007185] INFO: [Shinken] Gerhard Lausser, Gerhard.Lausser@consol.de
[1438007185] INFO: [Shinken] Gregory Starck, g.starck@gmail.com
[1438007185] INFO: [Shinken] Hartmut Goebel, h.goebel@goebel-consult.de
[1438007185] INFO: [Shinken] License: AGPL
[1438007185] INFO: [Shinken] Loading configuration
[1438007185] INFO: [Shinken] [config] opening '/etc/shinken/shinken.cfg' configuration file
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/modules/ws_arbiter.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/modules/sample.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/modules/glpidb.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/modules/glpi.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/modules/import-glpi.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/arbiters/arbiter-master.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/schedulers/scheduler-master.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/pollers/poller-master.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/reactionners/reactionner-android-sms.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/reactionners/reactionner-master.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/brokers/broker-master.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/receivers/receiver-master.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/realms/all.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/paths.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/active-directory.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/nmap.cfg'
[1438007185] INFO: [Shinken] Processing object config file '/etc/shinken/resource.d/snmp.cfg'
[1438007185] INFO: [Shinken] And arbiter is launched with the hostname:debian7glpi from an arbiter point of view of addr:debian7glpi
[1438007185] INFO: [Shinken] I am the master Arbiter: arbiter-master
[1438007185] INFO: [Shinken] My own modules: GLPI,ws-arbiter
[1438007185] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007185] INFO: [Shinken] Modules directory: /var/lib/shinken/modules
[1438007185] INFO: [Shinken] Correctly loaded glpidb as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded import-glpi as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_arbiter as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_poller as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_scheduler as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker_external as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded ws-arbiter as an old-new-style shinken module
[1438007185] WARNING: [Shinken] The module type glpi for GLPI was not found in modules!
[1438007185] INFO: [Shinken] [WS_Arbiter] Configuration done, host: 0.0.0.0(7760), username: anonymous)
[1438007185] INFO: [Shinken] I correctly loaded the modules: [ws-arbiter]
[1438007185] INFO: [Shinken] All: (in/potential) (schedulers:1) (pollers:1/1) (reactionners:1/1) (brokers:1/1) (receivers:1/1)
[1438007185] INFO: [Shinken] Running pre-flight check on configuration data...
[1438007185] INFO: [Shinken] Checking global parameters...
[1438007185] INFO: [Shinken] Checking hosts...
[1438007185] INFO: [Shinken]    Checked 0 hosts
[1438007185] INFO: [Shinken] Checking hostgroups...
[1438007185] INFO: [Shinken]    Checked 0 hostgroups
[1438007185] INFO: [Shinken] Checking contacts...
[1438007185] INFO: [Shinken]    Checked 0 contacts
[1438007185] INFO: [Shinken] Checking contactgroups...
[1438007185] INFO: [Shinken]    Checked 0 contactgroups
[1438007185] INFO: [Shinken] Checking notificationways...
[1438007185] INFO: [Shinken]    Checked 0 notificationways
[1438007185] INFO: [Shinken] Checking escalations...
[1438007185] INFO: [Shinken]    Checked 0 escalations
[1438007185] INFO: [Shinken] Checking services...
[1438007185] INFO: [Shinken]    Checked 0 services
[1438007185] INFO: [Shinken] Checking servicegroups...
[1438007185] INFO: [Shinken]    Checked 0 servicegroups
[1438007185] INFO: [Shinken] Checking timeperiods...
[1438007185] INFO: [Shinken]    Checked 0 timeperiods
[1438007185] INFO: [Shinken] Checking commands...
[1438007185] INFO: [Shinken]    Checked 3 commands
[1438007185] INFO: [Shinken] Checking hostsextinfo...
[1438007185] INFO: [Shinken]    Checked 0 hostsextinfo
[1438007185] INFO: [Shinken] Checking servicesextinfo...
[1438007185] INFO: [Shinken]    Checked 0 servicesextinfo
[1438007185] INFO: [Shinken] Checking checkmodulations...
[1438007185] INFO: [Shinken]    Checked 0 checkmodulations
[1438007185] INFO: [Shinken] Checking macromodulations...
[1438007185] INFO: [Shinken]    Checked 0 macromodulations
[1438007185] INFO: [Shinken] Checking servicedependencies...
[1438007185] INFO: [Shinken]    Checked 0 servicedependencies
[1438007185] INFO: [Shinken] Checking hostdependencies...
[1438007185] INFO: [Shinken]    Checked 0 hostdependencies
[1438007185] INFO: [Shinken] Checking arbiters...
[1438007185] INFO: [Shinken]    Checked 1 arbiters
[1438007185] INFO: [Shinken] Checking schedulers...
[1438007185] INFO: [Shinken]    Checked 1 schedulers
[1438007185] INFO: [Shinken] Checking reactionners...
[1438007185] INFO: [Shinken]    Checked 1 reactionners
[1438007185] INFO: [Shinken] Checking pollers...
[1438007185] INFO: [Shinken]    Checked 1 pollers
[1438007185] INFO: [Shinken] Checking brokers...
[1438007185] INFO: [Shinken]    Checked 1 brokers
[1438007185] INFO: [Shinken] Checking receivers...
[1438007185] INFO: [Shinken]    Checked 1 receivers
[1438007185] INFO: [Shinken] Checking resultmodulations...
[1438007185] INFO: [Shinken]    Checked 0 resultmodulations
[1438007185] INFO: [Shinken] Checking discoveryrules...
[1438007185] INFO: [Shinken]    Checked 0 discoveryrules
[1438007185] INFO: [Shinken] Checking discoveryruns...
[1438007185] INFO: [Shinken]    Checked 0 discoveryruns
[1438007185] INFO: [Shinken] Checking businessimpactmodulations...
[1438007185] INFO: [Shinken]    Checked 0 businessimpactmodulations
[1438007185] INFO: [Shinken] Cutting the hosts and services into parts
[1438007185] INFO: [Shinken] Creating packs for realms
[1438007185] INFO: [Shinken] Number of hosts in the realm All: 0 (distributed in 0 linked packs)
[1438007185] INFO: [Shinken] Total number of hosts : 0
[1438007185] INFO: [Shinken] Things look okay - No serious problems were detected during the pre-flight check
[1438007185] INFO: [Shinken] [Arbiter] Serializing the configurations...
[1438007185] INFO: [Shinken] Using the default serialization pass
[1438007185] INFO: [Shinken] Configuration Loaded
[1438007185] INFO: [Shinken] Trying to initialize additional groups for the daemon
[1438007185] INFO: [Shinken] Stale pidfile exists at invalid literal for int() with base 10: '' (/var/run/shinken/arbiterd.pid). Reusing it.
[1438007185] INFO: [Shinken] Opening xxx socket at xxx://localhost:7770
[1438007185] INFO: [Shinken] Initializing a CherryPy backend with 8 threads
[1438007185] INFO: [Shinken] Using the local log file '/var/log/shinken/arbiterd.log'
[1438007185] INFO: [Shinken] Printing stored debug messages prior to our daemonization
[1438007185] INFO: [Shinken] Successfully changed to workdir: /var/lib/shinken
[1438007185] INFO: [Shinken] Opening pid file: /var/run/shinken/arbiterd.pid
[1438007185] INFO: [Shinken] Redirecting stdout and stderr as necessary..
[1438007185] INFO: [Shinken] We are now fully daemonized pid=6785
[1438007185] INFO: [Shinken] Trying to init module: ws-arbiter
[1438007185] INFO: [Shinken] Starting external module ws-arbiter
[1438007185] INFO: [Shinken] Starting xxx daemon
[1438007185] INFO: [Shinken] Starting external process for instance ws-arbiter
[1438007185] INFO: [Shinken] ws-arbiter is now started ; pid=6796
[1438007185] INFO: [Shinken] And arbiter is launched with the hostname:debian7glpi from an arbiter point of view of addr:debian7glpi
[1438007185] INFO: [Shinken] Begin to dispatch configurations to satellites
[1438007185] INFO: [Shinken] [ws-arbiter[6796]]: Now running..
[1438007185] INFO: [Shinken] [WS_Arbiter] Starting WS arbiter xxx socket
[1438007185] INFO: [Shinken] [WS_Arbiter] Server started
[1438007185] INFO: [Shinken] Dispatching Realm All
[1438007185] INFO: [Shinken] [All] Dispatching 1/1 configurations
[1438007185] INFO: [Shinken] [All] Schedulers order: scheduler-master
[1438007185] INFO: [Shinken] [All] Dispatching configuration 0
[1438007185] INFO: [Shinken] [All] Trying to send conf 0 to scheduler scheduler-master
[1438007185] INFO: [Shinken] [All] Dispatch OK of conf in scheduler scheduler-master
[1438007185] INFO: [Shinken] OK, all schedulers configurations are dispatched
[1438007185] INFO: [Shinken] [All] Dispatching reactionner satellite with order: reactionner-master (spare:False),
[1438007185] INFO: [Shinken] [All] Trying to send configuration to reactionner reactionner-master
[1438007185] INFO: [Shinken] [All] Dispatch OK of configuration 0 to reactionner reactionner-master
[1438007185] INFO: [Shinken] [All] OK, no more reactionner sent need
[1438007185] INFO: [Shinken] [All] Dispatching poller satellite with order: poller-master (spare:False),
[1438007185] INFO: [Shinken] [All] Trying to send configuration to poller poller-master
[1438007185] INFO: [Shinken] [All] Dispatch OK of configuration 0 to poller poller-master
[1438007185] INFO: [Shinken] [All] OK, no more poller sent need
[1438007185] INFO: [Shinken] [All] Dispatching broker satellite with order: broker-master (spare:False),
[1438007185] INFO: [Shinken] [All] Trying to send configuration to broker broker-master
[1438007185] INFO: [Shinken] [All] Dispatch OK of configuration 0 to broker broker-master
[1438007185] INFO: [Shinken] [All] OK, no more broker sent need
[1438007185] INFO: [Shinken] [All] Dispatching receiver satellite with order: receiver-master (spare:False),
[1438007185] INFO: [Shinken] [All] Trying to send configuration to receiver receiver-master

==> /var/log/shinken/schedulerd.log <==
[1438007185] INFO: [Shinken] New configuration received

==> /var/log/shinken/arbiterd.log <==
[1438007185] INFO: [Shinken] [All] Dispatch OK of configuration 0 to receiver receiver-master
[1438007185] INFO: [Shinken]  (xxx://localhost:7773/)

==> /var/log/shinken/schedulerd.log <==
[1438007185] INFO: [Shinken] Correctly loaded glpidb as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded import-glpi as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_arbiter as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_poller as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_scheduler as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker_external as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded ws-arbiter as an old-new-style shinken module
[1438007185] INFO: [Shinken] I correctly loaded the modules: []
[1438007185] INFO: [Shinken] Loading configuration.
[1438007185] INFO: [Shinken] New configuration loaded
[1438007185] INFO: [Shinken] [scheduler-master] First scheduling launched
[1438007185] INFO: [Shinken] [scheduler-master] First scheduling done

==> /var/log/shinken/arbiterd.log <==
[1438007185] INFO: [Shinken] [All] OK, no more receiver sent need
[1438007185] INFO: [Shinken] [All] Trying to send configuration to receiver receiver-master
[1438007185] INFO: [Shinken] [All] Dispatch OK of configuration to receiver receiver-master

==> /var/log/shinken/pollerd.log <==
[1438007185] INFO: [Shinken] [poller-master] Init connection with scheduler-master at xxx://localhost:7768/ (3s,120s)
[1438007185] INFO: [Shinken] [poller-master] Connection OK with scheduler scheduler-master
[1438007185] INFO: [Shinken] [poller-master] Using max workers: 1
[1438007185] INFO: [Shinken] [poller-master] Using min workers: 1
[1438007185] INFO: [Shinken] We have our schedulers: {0: {'wait_homerun': {}, 'data_timeout': 120, 'name': u'scheduler-master', 'hard_ssl_name_check': False, 'uri': u'xxx://localhost:7768/', 'actions': {}, 'instance_id': 0, 'running_id': 1438007184.5275872, 'timeout': 3, 'address': u'localhost', 'active': True, 'use_ssl': False, 'push_flavor': 963574, 'port': 7768, 'con': <shinken.xxx_client.xxxClient object at 0x1954990>}}
[1438007185] INFO: [Shinken] Correctly loaded glpidb as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded import-glpi as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_arbiter as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_poller as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_scheduler as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker_external as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded ws-arbiter as an old-new-style shinken module
[1438007185] INFO: [Shinken] I correctly loaded the modules: []

==> /var/log/shinken/reactionnerd.log <==
[1438007185] INFO: [Shinken] [reactionner-master] Init connection with scheduler-master at xxx://localhost:7768/ (3s,120s)
[1438007185] INFO: [Shinken] [reactionner-master] Connection OK with scheduler scheduler-master
[1438007185] INFO: [Shinken] [reactionner-master] Using max workers: 15
[1438007185] INFO: [Shinken] [reactionner-master] Using min workers: 1
[1438007185] INFO: [Shinken] We have our schedulers: {0: {'wait_homerun': {}, 'data_timeout': 120, 'name': u'scheduler-master', 'hard_ssl_name_check': False, 'uri': u'xxx://localhost:7768/', 'actions': {}, 'instance_id': 0, 'running_id': 1438007184.5275872, 'timeout': 3, 'address': u'localhost', 'active': True, 'use_ssl': False, 'push_flavor': 963574, 'port': 7768, 'con': <shinken.xxx_client.xxxClient object at 0x23e8a10>}}
[1438007185] INFO: [Shinken] Correctly loaded glpidb as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded import-glpi as an old-new-style shinken module

==> /var/log/shinken/brokerd.log <==
[1438007185] INFO: [broker-master] We have our schedulers: {0: {'broks': {}, 'data_timeout': 120, 'name': u'scheduler-master', 'last_connection': 0, 'hard_ssl_name_check': False, 'uri': u'xxx://localhost:7768/', 'instance_id': 0, 'running_id': 0, 'timeout': 3, 'address': u'localhost', 'active': True, 'use_ssl': False, 'push_flavor': 963574, 'port': 7768}}
[1438007185] INFO: [broker-master] We have our arbiters: {0: {'broks': {}, 'last_connection': 0, 'name': u'arbiter-master', 'hard_ssl_name_check': False, 'uri': u'xxx://localhost:7770/', 'instance_id': 0, 'running_id': 0, 'address': u'localhost', 'use_ssl': False, 'port': 7770}}
[1438007185] INFO: [broker-master] We have our pollers: {0: {'broks': {}, 'instance_id': 0, 'last_connection': 0, 'name': u'poller-master', 'poller_tags': ['None'], 'hard_ssl_name_check': False, 'uri': u'xxx://192.168.13.101:7771/', 'passive': False, 'secret': '', 'reactionner_tags': [], 'running_id': 0, 'address': u'192.168.13.101', 'active': True, 'use_ssl': False, 'api_key': '', 'port': 7771}}
[1438007185] INFO: [broker-master] We have our reactionners: {0: {'broks': {}, 'instance_id': 0, 'last_connection': 0, 'name': u'reactionner-master', 'poller_tags': [], 'hard_ssl_name_check': False, 'uri': u'xxx://localhost:7769/', 'passive': False, 'secret': '', 'reactionner_tags': ['None'], 'running_id': 0, 'address': u'localhost', 'active': True, 'use_ssl': False, 'api_key': '', 'port': 7769}}
[1438007185] INFO: [broker-master] We received modules [<module type=glpidb name=glpidb />]
[1438007185] INFO: [broker-master] Correctly loaded glpidb as an old-new-style shinken module
[1438007185] INFO: [broker-master] Correctly loaded dummy_broker as an old-new-style shinken module
[1438007185] INFO: [broker-master] Correctly loaded import-glpi as an old-new-style shinken module
[1438007185] INFO: [broker-master] Correctly loaded dummy_arbiter as an old-new-style shinken module
[1438007185] INFO: [broker-master] Correctly loaded dummy_poller as an old-new-style shinken module
[1438007185] INFO: [broker-master] Correctly loaded dummy_scheduler as an old-new-style shinken module

==> /var/log/shinken/reactionnerd.log <==
[1438007185] INFO: [Shinken] Correctly loaded dummy_arbiter as an old-new-style shinken module

==> /var/log/shinken/brokerd.log <==
[1438007185] INFO: [broker-master] Correctly loaded dummy_broker_external as an old-new-style shinken module

==> /var/log/shinken/reactionnerd.log <==
[1438007185] INFO: [Shinken] Correctly loaded dummy_poller as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_scheduler as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded dummy_broker_external as an old-new-style shinken module
[1438007185] INFO: [Shinken] Correctly loaded ws-arbiter as an old-new-style shinken module

==> /var/log/shinken/brokerd.log <==
[1438007185] INFO: [broker-master] Correctly loaded ws-arbiter as an old-new-style shinken module
[1438007185] INFO: [broker-master] [GLPIdb broker] Get a glpidb data module for plugin glpidb
[1438007185] INFO: [broker-master] Trying to init module: glpidb

==> /var/log/shinken/reactionnerd.log <==
[1438007185] INFO: [Shinken] I correctly loaded the modules: []

==> /var/log/shinken/brokerd.log <==
[1438007185] INFO: [broker-master] [GLPIdb Broker] Creating a mysql backend : localhost (glpi)
[1438007185] INFO: [broker-master] [GLPIdb Broker] Connecting to database ...
[1438007185] INFO: [broker-master] [GLPIdb Broker] Connected
[1438007185] INFO: [broker-master] I correctly loaded the modules: [glpidb]

==> /var/log/shinken/schedulerd.log <==
[1438007185] INFO: [Shinken] A new broker just connected : broker-master
[1438007185] INFO: [Shinken] [scheduler-master] Created 6 initial Broks for broker broker-master

==> /var/log/shinken/brokerd.log <==
[1438007185] INFO: [broker-master] Connection OK to the scheduler scheduler-master
[1438007185] INFO: [broker-master] Connection OK to the poller poller-master
[1438007185] INFO: [broker-master] Connection OK to the reactionner reactionner-master
[1438007185] INFO: [broker-master] Connection OK to the receiver receiver-master

==> /var/log/shinken/receiverd.log <==
[1438007185] INFO: [receiver-master] We received modules []
[1438007185] INFO: [receiver-master] Correctly loaded glpidb as an old-new-style shinken module
[1438007185] INFO: [receiver-master] Correctly loaded dummy_broker as an old-new-style shinken module
[1438007185] INFO: [receiver-master] Correctly loaded import-glpi as an old-new-style shinken module
[1438007185] INFO: [receiver-master] Correctly loaded dummy_arbiter as an old-new-style shinken module
[1438007185] INFO: [receiver-master] Correctly loaded dummy_poller as an old-new-style shinken module
[1438007185] INFO: [receiver-master] Correctly loaded dummy_scheduler as an old-new-style shinken module
[1438007185] INFO: [receiver-master] Correctly loaded dummy_broker_external as an old-new-style shinken module
[1438007185] INFO: [receiver-master] Correctly loaded ws-arbiter as an old-new-style shinken module
[1438007185] INFO: [receiver-master] I correctly loaded the modules: []

==> /var/log/shinken/pollerd.log <==
[1438007186] INFO: [Shinken] [poller-master] Allocating new fork Worker: 0

==> /var/log/shinken/reactionnerd.log <==
[1438007187] INFO: [Shinken] [reactionner-master] Allocating new fork Worker: 0

Pour le message : [1438007185] WARNING: [Shinken] The module type glpi for GLPI was not found in modules!
j'ai dans /etc/shinken/modules/glpi.cfg :

define module{
     module_name      GLPI
     module_type      glpi
#     uri              xxx://localhost/glpi/plugins/webservices/xmlrpc.php
     uri              xxx://192.168.13.101/glpi/plugins/webse … xmlrpc.php
#     login_name       shinken
#     login_password   passshinken
     login_name       anonymous
     #login_password   xxxx
}

j'ai aussi testé avec l'utilisateur shinken/passshinken

Last edited by caponcet (2015-07-27 16:37:03)

ddurieux

Plugins Dev

From: Propières, France

Registered: 2005-06-17

Posts: 7,521

Re: [résolu]Monitoring : page vierge

t'as mis quoi en definition de modules dans le fichier de conf de l'arbiter?

caponcet

Member

Registered: 2015-07-13

Posts: 19

Re: [résolu]Monitoring : page vierge

Merci de votre réponse !

Voici mon fichier de configuration arbiter :

root@debian7glpi:~# cat /etc/shinken/arbiters/arbiter-master.cfg
#===============================================================================
# ARBITER
define arbiter {
    arbiter_name    arbiter-master
    #host_name       node1       ; CHANGE THIS if you have several Arbiters (like with a spare)
    address         localhost   ; DNS name or IP
    port            7770
    spare           0           ; 1 = is a spare, 0 = is not a spare
    modules      GLPI, ws-arbiter
    use_ssl               0
    hard_ssl_name_check   0
}

J'ai également testé avec l'adresse LAN du serveur : 192.168.13.101

J'ai commenté les modules que je mettais dans shinken-specific.cfg de la version 1.4 de shinken car visiblement le nouveau shinken utilise un système modulaire. J'ai donc importé 3 modules shinken et utilisé les conf dans /etc/shinken/modules à la place.

Le message "Vous n'avez pas les droits requis pour réaliser cette action." s'applique à apache, à debian, à shinken ? J'ai modifié le daemon de shinken pour qu'il s'exécute en tant que shinken/shinken (/etc/defaut/shinken et /etc/shinken/shinken.cfg) puis j'ai modifié les droits sur /var/run/shinken sans quoi mon démon shinken de redémarrait pas lors du boot en raison d'un problème de droits (chown -R shinken:shinken /var/run/shinken/).

PS : M.Durieux, si vous le désirez je vous enverrai ma doc PDF (qui couvre l'installation sur debian 7 et 8, l'utilisation et le déploiement de fusionventory, et shinken + monitoring) une fois le projet terminé afin que vous puissiez mettre à jour votre excellente doc de monitoring 0.84.

Last edited by caponcet (2015-07-28 11:34:29)

ddurieux

Plugins Dev

From: Propières, France

Registered: 2005-06-17

Posts: 7,521

Re: [résolu]Monitoring : page vierge

le module glpi c'est pas GLPI, mais import-glpi

caponcet

Member

Registered: 2015-07-13

Posts: 19

Re: [résolu]Monitoring : page vierge

Merci ! ça a corrigé mon dashboard, plus de page vide et le restartshinken fonctionne (en installant php5-curl) ! C'était le but de mon installation. Par contre j'ai seulement les deux lignes permettant de recharger la base de données et de redémarrer shinken, je n'ai plus l'ancien dashboard pour accéder au catalogue de composant.

Par ailleurs j'ai toujours le message "Vous n'avez pas les droits requis pour réaliser cette action." dans component.php, hostnotificationtemplate.php, servicenotificationtemplate.php, eventhandler.php, perfdata.php, notificationcommand.php, realm.php et tag.php.

Je n'ai pas de log à part apache qui répond 200 (ok) ou 304 (cache).

Du coup je ne peux configurer aucune sonde nagios avec shinken ^^

Last edited by caponcet (2015-07-28 14:35:30)

dmb77

Member

Registered: 2011-02-11

Posts: 298

Re: [résolu]Monitoring : page vierge

regarde les droits affectés au plugin dans les profils

caponcet

Member

Registered: 2015-07-13

Posts: 19

Re: [résolu]Monitoring : page vierge

Merci !
J'ai donc donné à mon utilisateur glpi tous les droits sur le plugin "monitoring" via le "profil de super-admin", j'ai maintenant un tableau de bord aux petits oignons et la possibilité d'associer des sondes (commandes) à des hôtes via le "catalogue de commandes" (composants + hôtes).

J'ai un autre problème maintenant mais ce post est résolu pour ma part ! Je posterai mon problème ailleurs si je ne trouve pas la solution dans le forum.

Merci à tous !

Last edited by caponcet (2015-07-28 17:16:26)