Page History

ERROR: [Shinken] A scheduler push me actions but it is not in my configuration so I drop these actions
ERROR: [Shinken] Maybe I'm not ready or there is a rogue scheduler
ERROR: [Shinken] Unknown Scheduler detected with host name:[master1] and sched_id[1]

Le protocole est HTTP par défaut, et HTTPS si le paramètre SSL a été mis à 1.

Le protocole est HTTP par défaut, et HTTPS si le paramètre SSL a été mis à 1.

#===============================================================================
# POLLER
#===============================================================================
# Description: The poller is responsible for:
# - Execute checks
#===============================================================================

define poller {


    #======== Daemon name and address =========
    # Daemon name. Must be unique
    poller_name         Europe-poller

    # IP/fqdn of this daemon (note: you MUST change it by the real ip/fqdn of this server)
    address Shinken Enterprise. Lines added by import core. Do not remove it, it's used by Shinken Enterprise to update your objects if you re-import them.
    _SE_UUID            core-poller-d571cb8c5add11e5846f080027f08538
    _SE_UUID_HASH       e04b7dc95665955df040e3e2e6767b29
# End of Shinken   node1.mydomainEnterprise part


    # Port (HTTP/HTTPS) exposed by this daemon
    port       ======== Daemon name and address =========
    # Daemon name. Must be unique
    poller_name         7771poller-master

    # 0IP/fqdn =of usethis HTTP, 1 = use HTTPS
    use_ssldaemon (note: you MUST change it by the real ip/fqdn of this server)
    address             0localhost

    # Duration in which we will keep the timeout.
Port (HTTP/HTTPS) exposed by this daemon
    port             keep_timeout_time   1200
7771

    #======== Daemon performance sizing =========
    # Number of worker process to launch. 0 = 1 per CPU
    min_workers               0

    # Number of maximum commands a worker is allowed to launch in the same time
    processes_by_worker       256

    # How many seconds to wait between the poller to get jobs from the scheduler
    polling_interval          1

    # Ranges for the check : poller statistics
    #exec_stat_range    50, 100, 200, 300, 400, 1000, 5000, 15000

	# Percentage of used physical RAM beyond which the poller will not launch any new check
	max_ram_percent 0 = use HTTP, 1 = use HTTPS
    use_ssl	            0

    # Duration in which we will keep the timeout.
    keep_timeout_time   1200


    #======== Daemon performance sizing =========
    # Number of worker process to launch. 0 = 1 per CPU
    min_workers               0

    # Number of maximum commands a worker is allowed to launch in the same time
    processes_by_worker       256

    # Specify the number of seconds the Poller should wait before retrieving jobs from the Scheduler
    polling_interval           951

    # NumberRanges offor maximumthe runningscheck processes: inpoller thestatistics
 CPU Queue per CPU. Default value is 4.
    #max_cpu_queue_per_cpu    4 #exec_stat_range    50, 100, 200, 300, 400, 1000, 5000, 15000

    #======== Daemon connection timeout and down state limit =========
    # timeout: how many seconds to consider a node don't answer
    timeout Time (in ms): if the time to compute stats (for shinken checks) is higher
    #               than this time, then the log will be in INFO   3
level
    # data_timeout: how many second to consider a configuration transfert to be failedDefault: 100  (ms)
    # display_statistics_compute_time_if_higher    100

    # becausePercentage theof networkused brandwithphysical isRAM toobeyond small.
which the poller will data_timeoutnot launch any new check
    max_ram_percent      120     95

    # max_check_attempts: how many fail check to consider this daemon as DEAD
    max_check_attempts        3Number of maximum runnings processes in the CPU Queue per CPU. Default value is 4.
    #max_cpu_queue_per_cpu    4

    # Check this daemon every X seconds======== Daemon connection timeout and down state limit =========
    check_interval# timeout: how many seconds to consider a node don't answer
   60


 timeout    #======== Modules to enable for this daemon =========
      # Available:  None3

 for this daemon
 # data_timeout: how modules


many second to  #======== Realm and architecture settings =========consider a configuration transfert to be failed
    # Realmbecause tothe setnetwork thisbrandwith is daemontoo intosmall.
    realmdata_timeout                    All120

    # managemax_sub_realms 1 = take data from thecheck_attempts: how many fail check to consider this daemon realmas andDEAD
 its sub realms
 max_check_attempts   #     3

    # Check this daemon every X seconds
    0 = take data only from the daemon realmcheck_interval            60



    manage_sub_realms        0

#======== Modules to enable for this daemon =========
    # Available: Poller tagsNone arefor managedthis tags.daemon
 The hosts, checks andmodules


 commands can have specific tags, and #======== Realm and architecture settings =========
    # thisRealm pollerto willset onlythis takedaemon theminto
 if the element tagrealm is list in the poller
    # Reserved tag name:  None  =  untaggued element (default value)
All

    # #pollermanage_sub_tagsrealms 1 = (default) take data from the daemon realm and its sub Nonerealms

    # passive:  0 = poller will connect to the scheduler to take/returs jobs
    #  0 = take data only from the daemon realm
 1 = scheduler willmanage_sub_realms connect to this poller to push/take back jobs1

    passive# In NATted environments, you declare each satellite ip[:port] as seen by
    # *this* daemon 0

(if port not set, # spare: 0 = this poller is always active
    #        1 = this poller will be activated by the arbiter is another poller is dead
    spare                    0



    #======== Enable or not this daemon =========
    # 1 = is enabled, o = is disabled
    enabledthe port declared by satellite itself
    # is used)
    #satellitemap    scheduler-1=1.2.3.4:7768, scheduler-2=1.2.3.5:7771

    # Poller tags are managed tags. The hosts, checks and commands can have specific tags, and
    # this poller will only take them if the element tag is list in the poller
    # Reserved tag name:  None  =  untaggued element (default value)
    #poller_tags             None

    # passive:  0 = poller will connect to the scheduler to take/returs jobs
    #           1 = scheduler will connect to this  1

}




poller to push/take back jobs
    passive                  0

    # spare: 0 = this poller is always active
    #        1 = this poller will be activated by the arbiter is another poller is dead
    spare                    0


    #======== VMWare / ESXi ==========
    # 1 (default) = if vmware get the ESXi CPU stats value, 0 = do not get value
    vmware__statistics_compute_enable     1


    #======== Enable or not this daemon =========
    # 1 = is enabled, 0 = is disabled
    enabled                  1

}