Hi,

I would like to use realm to monitoring different client. I tried to configure the realm and it works few second (i can see them in the webui) but now i can't see anything.

The check seems work, my slave scheduler/poller receive command.

How can i get back my realm on my webui ?

Arbiter conf :
root@shinken-master /etc/shinken # cat arbiters/arbiter-master.cfg
#================================================= ==============================
# ARBITER
#================================================= ==============================
# Description: The Arbiter is responsible for:
# - Loading, manipulating and dispatching the configuration
# - Validating the health of all other Shinken daemons
# - Issuing global directives to Shinken daemons (kill, activate-spare, etc.)
# http://www.shinken-monitoring.org/wi...bjects/arbiter
#================================================= ==============================
# IMPORTANT: If you use several arbiters you MUST set the host_name on each
# servers to its real DNS name ('hostname' command).
#================================================= ==============================
define arbiter {
arbiter_name arbiter-master
#host_name node1 ; CHANGE THIS if you have several Arbiters
address 192.168.11.181 ; DNS name or IP
port 7770
spare 0 ; 1 = is a spare, 0 = is not a spare

## Interesting modules:
# - CommandFile = Open the named pipe nagios.cmd
# - Mongodb = Load hosts from a mongodb database
# - PickleRetentionArbiter = Save data before exiting
# - NSCA = NSCA server
# - VMWare_auto_linking = Lookup at Vphere server for dependencies
# - GLPI = Import hosts from GLPI
# - import-glpi = Import configuration from GLPI (need plugin monitoring for GLPI in server side)
# - TSCA = TSCA server
# - MySQLImport = Load configuration from a MySQL database
# - WS_Arbiter = WebService for pushing results to the arbiter
# - Collectd = Receive collectd perfdata
# - SnmpBooster = Snmp bulk polling module, configuration linker
# - Landscape = Import hosts from Landscape (Ubuntu/Canonical management tool)
# - AWS = Import hosts from Amazon AWS (here EC2)
# - IpTag = Tag an host based on it's IP range
# - FileTag = Tag an host if it's on a flat file
# - CSVTag = Tag an host from the content of a CSV file

modules CommandFile
#modules CommandFile, Mongodb, NSCA, VMWare_auto_linking, WS_Arbiter, Collectd, Landscape, SnmpBooster, AWS

# Enable https or not
use_ssl 0
# enable certificate/hostname check, will avoid man in the middle attacks
hard_ssl_name_check 0

## Uncomment these lines in a HA architecture so the master and slaves know
## how long they may wait for each other.
#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
}

the scheduler conf :
root@shinken-master /etc/shinken # cat schedulers/scheduler-master.cfg
#================================================= =============================
# SCHEDULER (S1_Scheduler)
#================================================= ==============================
# The scheduler is a "Host manager". It gets the hosts and their services,
# schedules the checks and transmit them to the pollers.
# Description: The scheduler is responsible for:
# - Creating the dependancy tree
# - Scheduling checks
# - Calculating states
# - Requesting actions from a reactionner
# - Buffering and forwarding results its associated broker
# http://www.shinken-monitoring.org/wi...ects/scheduler
#================================================= ==============================
define scheduler {
scheduler_name scheduler-master ; Just the name
address 192.168.11.181 ; IP or DNS address of the daemon
port 7768 ; TCP port of the daemon
## Optional
spare 0 ; 1 = is a spare, 0 = is not a spare
weight 1 ; Some schedulers can manage more hosts than others
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

## Interesting modules that can be used:
# - PickleRetention = Save data before exiting in flat-file
# - MemcacheRetention = Same, but in a MemCache server
# - RedisRetention = Same, but in a Redis server
# - MongodbRetention = Same, but in a MongoDB server
# - NagiosRetention = Read retention info from a Nagios retention file
# (does not save, only read)
# - SnmpBooster = Snmp bulk polling module
#modules PickleRetention
modules

## Advanced Features
# Realm is for multi-datacenters
realm All

# Skip initial broks creation. Boot fast, but some broker modules won't
# work with it!
skip_initial_broks 0

# In NATted environments, you declare each satellite ip[ort] as seen by
# *this* scheduler (if port not set, the port declared by satellite itself
# is used)
#satellitemap poller-1=1.2.3.4:1772, reactionner-1=1.2.3.5:1773, ...

# Enable https or not
use_ssl 0
# enable certificate/hostname check, will avoid man in the middle attacks
hard_ssl_name_check 0
}


define scheduler{

scheduler_name scheduler-slave
address 192.168.11.120
port 7768
realm sys
spare 0
}
the poller conf :

root@shinken-master /etc/shinken # cat pollers/poller-master.cfg
#================================================= ==============================
# POLLER (S1_Poller)
#================================================= ==============================
# Description: The poller is responsible for:
# - Active data acquisition
# - Local passive data acquisition
# http://www.shinken-monitoring.org/wi...objects/poller
#================================================= ==============================
define poller {
poller_name poller-master
address 192.168.11.181
port 7771

## Optional
spare 0 ; 1 = is a spare, 0 = is not a spare
manage_sub_realms 0 ; Does it take jobs from schedulers of sub-Realms?
min_workers 0 ; Starts with N processes (0 = 1 per CPU)
max_workers 0 ; No more than N processes (0 = 1 per CPU)
processes_by_worker 256 ; Each worker manages N checks
polling_interval 1 ; Get jobs from schedulers each N seconds
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

## Interesting modules that can be used:
# - NrpeBooster = Replaces the check_nrpe binary. Therefore it
# enhances performances when there are lot of NRPE
# calls.
# - CommandFile = Allow the poller to read a nagios.cmd named pipe.
# This permits the use of distributed check_mk checks
# should you desire it.
# - SnmpBooster = Snmp bulk polling module
modules

## Advanced Features
#passive 0 ; For DMZ monitoring, set to 1 so the connections
; will be from scheduler -> poller.

# Poller tags are the tag that the poller will manage. Use None as tag name to manage
# untaggued checks
#poller_tags None

# Enable https or not
use_ssl 0
# enable certificate/hostname check, will avoid man in the middle attacks
hard_ssl_name_check 0


realm All
}
#Pollers launch checks
define poller{
poller_name poller-slave
address 192.168.11.120
port 7771
realm sys
}
and the broker conf :

root@shinken-master /etc/shinken # cat brokers/broker-master.cfg
#================================================= ==============================
# BROKER (S1_Broker)
#================================================= ==============================
# Description: The broker is responsible for:
# - Exporting centralized logs of all Shinken daemon processes
# - Exporting status data
# - Exporting performance data
# - Exposing Shinken APIs:
# - Status data
# - Performance data
# - Configuration data
# - Command interface
# http://www.shinken-monitoring.org/wi...objects/broker
#================================================= ==============================
define broker {
broker_name broker-master
address 192.168.11.181
port 7772
spare 0

## Optional
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
# Default: None
# Interesting modules that can be used:
# - simple-log = just all logs into one file
# - livestatus = livestatus listener
# - ToNdodb_Mysql = NDO DB support
# - npcdmod = Use the PNP addon
# - graphite = Use a Graphite time series DB for perfdata
# - webui = Shinken Web interface
# - glpidb = Save data in GLPI MySQL database
modules webui

# Enable https or not
use_ssl 0
# enable certificate/hostname check, will avoid man in the middle attacks
hard_ssl_name_check 0

## Advanced
realm All
}

define broker {
broker_name broker-slave
address 192.168.11.120
port 7772
spare 0
realm sys
}

On my shinken slave i have this on the log :

root@shinken-slave /etc/shinken/hosts # cat /var/log/shinken/schedulerd.log
2014-06-04 15:42:49,049 [1401889369] Warning : Received a SIGNAL 15
2014-06-04 15:48:21,779 [1401889701] Warning : Printing stored debug messages prior to our daemonization
2014-06-04 15:49:52,912 [1401889792] HOST ALERT: shinken-slave;DOWN;SOFT;1;[Errno 2] No such file or directory
2014-06-04 15:54:53,283 [1401890093] HOST ALERT: shinken-slave;DOWN;HARD;2;[Errno 2] No such file or directory
2014-06-04 15:54:53,285 [1401890093] HOST NOTIFICATION: admin;shinken-slave;DOWN;notify-host-by-email;[Errno 2] No such file or directory
2014-06-04 16:00:47,735 [1401890447] SERVICE ALERT: shinken-slave;SSH Connexion;CRITICAL;SOFT;1;/bin/sh: 1: /var/lib/shinken/libexec/check_ssh_connexion.py: not found
2014-06-04 16:00:49,739 [1401890449] HOST ALERT: shinken-slave;DOWN;SOFT;1;[Errno 2] No such file or directory
2014-06-04 16:01:10,768 [1401890470] SERVICE ALERT: shinken-slave;CPU Stats;CRITICAL;SOFT;1;/bin/sh: 1: /var/lib/shinken/libexec/check_cpu_stats_by_ssh.py: not found
2014-06-04 16:01:10,768 [1401890470] SERVICE ALERT: shinken-slave;Reboot;CRITICAL;SOFT;1;/bin/sh: 1: /var/lib/shinken/libexec/check_uptime_by_ssh.py: not found
2014-06-04 16:01:12,773 [1401890472] HOST ALERT: shinken-slave;DOWN;SOFT;1;[Errno 2] No such file or directory
2014-06-04 16:01:12,773 [1401890472] HOST ALERT: shinken-slave;DOWN;SOFT;1;[Errno 2] No such file or directory
2014-06-04 16:02:10,023 [1401890530] Warning : Received a SIGNAL 15
2014-06-04 16:02:10,648 [1401890530] Warning : Printing stored debug messages prior to our daemonization
2014-06-04 16:03:28,330 [1401890608] Warning : Received a SIGNAL 15
2014-06-04 16:03:55,245 [1401890635] Warning : Printing stored debug messages prior to our daemonization
2014-06-04 16:04:26,295 [1401890666] HOST ALERT: shinken-slave;DOWN;SOFT;1;[Errno 2] No such file or directory
2014-06-04 16:09:26,672 [1401890966] HOST ALERT: shinken-slave;DOWN;HARD;2;[Errno 2] No such file or directory
2014-06-04 16:09:26,674 [1401890966] HOST NOTIFICATION: admin;shinken-slave;DOWN;notify-host-by-email;[Errno 2] No such file or directory
2014-06-04 16:13:54,015 [1401891234] HOST ALERT: shinken-slave;DOWN;SOFT;1;[Errno 2] No such file or directory
It looks like it work :/

Thank you for your time and your help