How to add a satellite to an icinga master with an existing client?

Icinga 2
21

This is a grep on the satellite’s name. i didin’t put all the output but if you want more tell me or if its too much tell me too.
I can refine the search, and I can do it with an other name. (i replaced satellite.FQDN by SATELLITE)

[root@satellite]# cat /var/log/icinga2/debug.log | grep “SATELLITE”
[2019-04-29 08:45:15 +0000] notice/ApiListener: Creating config update for file ‘/etc/icinga2/zones.d/satellite/SATELLITE.conf’.
[2019-04-29 08:45:15 +0000] notice/ApiListener: Creating config update for file ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’.
[2019-04-29 08:50:45 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:50:55 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:51:02 +0000] information/ApiListener: New client connection for identity ‘SATELLITE’ from [34.254.195.47]:47606
[2019-04-29 08:51:02 +0000] debug/EndpointDbObject: update is_connected=1 for endpoint ‘SATELLITE’
[2019-04-29 08:51:02 +0000] information/ApiListener: Sending config updates for endpoint ‘SATELLITE’ in zone ‘satellite’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Syncing configuration files for zone ‘satellite’ to endpoint ‘SATELLITE’.
[2019-04-29 08:51:02 +0000] notice/ApiListener: Creating config update for file ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Finished sending config file updates for endpoint ‘SATELLITE’ in zone ‘satellite’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Syncing runtime objects to endpoint ‘SATELLITE’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Finished syncing runtime objects to endpoint ‘SATELLITE’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Finished sending runtime config updates for endpoint ‘SATELLITE’ in zone ‘satellite’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Sending replay log for endpoint ‘SATELLITE’ in zone ‘satellite’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Finished sending replay log for endpoint ‘SATELLITE’ in zone ‘satellite’.
[2019-04-29 08:51:02 +0000] information/ApiListener: Finished syncing endpoint ‘SATELLITE’ in zone ‘satellite’.
[2019-04-29 08:51:02 +0000] notice/JsonRpcConnection: Received ‘icinga::Hello’ message from ‘SATELLITE’
[2019-04-29 08:51:02 +0000] notice/JsonRpcConnection: Received ‘pki::RequestCertificate’ message from ‘SATELLITE’
[2019-04-29 08:51:02 +0000] information/JsonRpcConnection: Received certificate request for CN ‘SATELLITE’ signed by our CA.
[2019-04-29 08:51:02 +0000] information/JsonRpcConnection: The certificate for CN ‘SATELLITE’ is valid and uptodate. Skipping automated renewal.
[2019-04-29 08:51:02 +0000] notice/JsonRpcConnection: Received ‘event::SetNextCheck’ message from ‘SATELLITE’
[2019-04-29 08:51:02 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:05 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:05 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:51:05 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:51:07 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:10 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:12 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:12 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:51:15 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:15 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:51:15 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:51:17 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:20 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:22 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:22 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:51:25 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:25 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:51:25 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:51:27 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:30 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:32 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:32 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:51:35 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:35 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:51:35 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:51:37 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:40 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:42 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:42 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:51:45 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:45 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:51:45 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:51:47 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:50 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:02
[2019-04-29 08:51:52 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:51:52 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:51:52 +0000] notice/JsonRpcConnection: Received ‘event::SetForceNextCheck’ message from ‘SATELLITE’
[2019-04-29 08:51:52 +0000] notice/JsonRpcConnection: Received ‘event::SetNextCheck’ message from ‘SATELLITE’
[2019-04-29 08:51:55 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:52
[2019-04-29 08:51:55 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:51:55 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:51:57 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:00 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:51:52
[2019-04-29 08:52:02 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:02 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:52:03 +0000] notice/JsonRpcConnection: Received ‘event::SetNextCheck’ message from ‘SATELLITE’
[2019-04-29 08:52:03 +0000] notice/JsonRpcConnection: Received ‘event::CheckResult’ message from ‘SATELLITE’
[2019-04-29 08:52:03 +0000] debug/Checkable: Update checkable ‘SATELLITE’ with check interval ‘300’ from last check time at 2019-04-29 08:52:03 +0000 (1.55653e+09) to next check time at 2019-04-29 08:56:49 +0000(1.55653e+09).
[2019-04-29 08:52:03 +0000] debug/DbEvents: add checkable check history for ‘SATELLITE’
[2019-04-29 08:52:04 +0000] debug/IdoMysqlConnection: Query: UPDATE icinga_hoststatus SET acknowledgement_type = ‘0’, active_checks_enabled = ‘1’, check_command = ‘ping4’, check_source = ‘SATELLITE’, check_type = ‘0’, current_check_attempt = ‘1’, current_notification_number = ‘0’, current_state = ‘1’, endpoint_object_id = 217, event_handler_enabled = ‘1’, execution_time = ‘11.009032’, flap_detection_enabled = ‘0’, has_been_checked = ‘1’, host_object_id = 269, instance_id = 1, is_flapping = ‘0’, is_reachable = ‘1’, last_check = FROM_UNIXTIME(1556527923), last_hard_state = ‘1’, last_hard_state_change = FROM_UNIXTIME(1556287325), last_state_change = FROM_UNIXTIME(1556286920), last_time_down = FROM_UNIXTIME(1556527923), last_time_up = FROM_UNIXTIME(1556286627), latency = ‘0.000480’, long_output = ‘’, max_check_attempts = ‘3’, next_check = FROM_UNIXTIME(1556528209), normal_check_interval = ‘5’, notifications_enabled = ‘1’, original_attributes = ‘null’, output = ‘CRITICAL - Plugin timed out’, passive_checks_enabled = ‘1’, percent_state_change = ‘0’, perfdata = ‘’, problem_has_been_acknowledged = ‘0’, process_performance_data = ‘1’, retry_check_interval = ‘1’, scheduled_downtime_depth = ‘0’, should_be_scheduled = ‘1’, state_type = ‘1’, status_update_time = FROM_UNIXTIME(1556527923) WHERE host_object_id = 269
[2019-04-29 08:52:05 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:52:03
[2019-04-29 08:52:05 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:52:05 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:52:07 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:10 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:52:03
[2019-04-29 08:52:12 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:12 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:52:15 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:52:03
[2019-04-29 08:52:15 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:52:15 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:52:17 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:20 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:52:03
[2019-04-29 08:52:22 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:22 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:52:25 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:52:03
[2019-04-29 08:52:25 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:52:25 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:52:27 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:30 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:52:03
[2019-04-29 08:52:32 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:32 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 08:52:35 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 08:52:03
[2019-04-29 08:52:35 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 08:52:35 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 08:52:37 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 08:52:38 +0000] notice/ApiListener: Creating config update for file ‘/etc/icinga2/zones.d/satellite/SATELLITE.conf’.
[2019-04-29 08:52:38 +0000] notice/ApiListener: Creating config update for file ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’.
[2019-04-29 08:52:38 +0000] information/ApiListener: Updating configuration file: /var/lib/icinga2/api/zones/satellite//_etc/SATELLITE.conf
[2019-04-29 08:52:38 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.

Thanks,
Louis,

22

What’s the content of /etc/icinga2/zones.d/satellite/SATELLITE.conf? Is that host object visible on the satellite, e.g. via icinga2 object list --type Host --name SATELLITE?

When you force a re-check via Icinga Web 2, trace it via the debug log on the master (receiving a command, forwarding it via cluster event ForceNextCheck, etc.) and the satellite’s debug log which receives the event, schedules a check, etc.

23

This is my SATELLITE.conf :

// Host Objects
object Host “SATELLITE” {
check_command = “ping4”
address = “IP PUBLIC SATELLITE”
vars.client_endpoint = “SATELLITE” //follows the convention that host name == endpoint
}

from the satellite :

icinga2 object list --type Host --name SATELLITE

root@]# icinga2 object list --type Host --name SATELLITE
Object ‘SATELLITE’ of type ‘Host’:
% declared in ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’, lines 2:1-2:55

  • __name = “SATELLITE”
  • action_url = “”
  • address = “IP PUBLIC SATELLITE”
    % = modified in ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’, lines 4:5-4:29
  • address6 = “”
  • check_command = “ping4”
    % = modified in ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’, lines 3:5-3:27
  • check_interval = 300
  • check_period = “”
  • check_timeout = null
  • command_endpoint = “”
  • display_name = “SATELLITE”
  • enable_active_checks = true
  • enable_event_handler = true
  • enable_flapping = false
  • enable_notifications = true
  • enable_passive_checks = true
  • enable_perfdata = true
  • event_command = “”
  • flapping_threshold = 0
  • flapping_threshold_high = 30
  • flapping_threshold_low = 25
  • groups =
  • icon_image = “”
  • icon_image_alt = “”
  • max_check_attempts = 3
  • name = “SATELLITE”
  • notes = “”
  • notes_url = “”
  • package = “_cluster”
  • retry_interval = 60
  • source_location
    • first_column = 1
    • first_line = 2
    • last_column = 55
    • last_line = 2
    • path = “/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf”
  • templates = [ “SATELLITE” ]
    % = modified in ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’, lines 2:1-2:55
  • type = “Host”
  • vars
    • client_endpoint = “SATELLITE”
      % = modified in ‘/var/lib/icinga2/api/zones/satellite/_etc/SATELLITE.conf’, lines 5:5-5:70
  • volatile = false
  • zone = “satellite”

From the Master :

icinga2 object list --type Host --name SATELLITE

root@# icinga2 object list --type Host --name SATELLITE
Object ‘SATELLITE’ of type ‘Host’:
% declared in ‘/etc/icinga2/zones.d/satellite/SATELLITE.conf’, lines 2:1-2:55

  • __name = “SATELLITE”
  • action_url = “”
  • address = “IP PUBLIC SATELLITE”
    % = modified in ‘/etc/icinga2/zones.d/satellite/SATELLITE.conf’, lines 4:5-4:29
  • address6 = “”
  • check_command = “ping4”
    % = modified in ‘/etc/icinga2/zones.d/satellite/SATELLITE.conf’, lines 3:5-3:27
  • check_interval = 300
  • check_period = “”
  • check_timeout = null
  • command_endpoint = “”
  • display_name = “SATELLITE”
  • enable_active_checks = true
  • enable_event_handler = true
  • enable_flapping = false
  • enable_notifications = true
  • enable_passive_checks = true
  • enable_perfdata = true
  • event_command = “”
  • flapping_threshold = 0
  • flapping_threshold_high = 30
  • flapping_threshold_low = 25
  • groups =
  • icon_image = “”
  • icon_image_alt = “”
  • max_check_attempts = 3
  • name = “SATELLITE”
  • notes = “”
  • notes_url = “”
  • package = “_etc”
  • retry_interval = 60
  • source_location
    • first_column = 1
    • first_line = 2
    • last_column = 55
    • last_line = 2
    • path = “/etc/icinga2/zones.d/satellite/SATELLITE.conf”
  • templates = [ “SATELLITE” ]
    % = modified in ‘/etc/icinga2/zones.d/satellite/SATELLITE.conf’, lines 2:1-2:55
  • type = “Host”
  • vars
    • client_endpoint = “SATELLITE”
      % = modified in ‘/etc/icinga2/zones.d/satellite/SATELLITE.conf’, lines 5:5-5:70
  • volatile = false
  • zone = “satellite”

When you force a re-check via Icinga Web 2, trace it via the debug log on the master (receiving a command, forwarding it via cluster event ForceNextCheck, etc.) and the satellite’s debug log which receives the event, schedules a check, etc.

this output is ok for you ? this what happened when i force a check.

[2019-04-29 12:34:20 +0000] debug/Checkable: Update checkable ‘SATELLITE’ with check interval ‘300’ from last check time at 2019-04-29 12:34:20 +0000 (1.55654e+09) to next check time at 2019-04-29 12:39:14 +0000(1.55654e+09).
[2019-04-29 12:34:20 +0000] debug/DbEvents: add checkable check history for ‘SATELLITE’
[2019-04-29 12:34:20 +0000] debug/IdoMysqlConnection: Query: UPDATE icinga_hoststatus SET acknowledgement_type = ‘0’, active_checks_enabled = ‘1’, check_command = ‘ping4’, check_source = ‘SATELLITE’, check_type = ‘0’, current_check_attempt = ‘1’, current_notification_number = ‘0’, current_state = ‘1’, endpoint_object_id = 217, event_handler_enabled = ‘1’, execution_time = ‘11.002213’, flap_detection_enabled = ‘0’, has_been_checked = ‘1’, host_object_id = 269, instance_id = 1, is_flapping = ‘0’, is_reachable = ‘1’, last_check = FROM_UNIXTIME(1556541260), last_hard_state = ‘1’, last_hard_state_change = FROM_UNIXTIME(1556287325), last_state_change = FROM_UNIXTIME(1556286920), last_time_down = FROM_UNIXTIME(1556541260), last_time_up = FROM_UNIXTIME(1556286627), latency = ‘0.000298’, long_output = ‘’, max_check_attempts = ‘3’, next_check = FROM_UNIXTIME(1556541554), normal_check_interval = ‘5’, notifications_enabled = ‘1’, original_attributes = ‘null’, output = ‘CRITICAL - Plugin timed out’, passive_checks_enabled = ‘1’, percent_state_change = ‘0’, perfdata = ‘’, problem_has_been_acknowledged = ‘0’, process_performance_data = ‘1’, retry_check_interval = ‘1’, scheduled_downtime_depth = ‘0’, should_be_scheduled = ‘1’, state_type = ‘1’, status_update_time = FROM_UNIXTIME(1556541260) WHERE host_object_id = 269
[2019-04-29 12:34:23 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 12:34:23 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’
[2019-04-29 12:34:24 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 12:34:20
[2019-04-29 12:34:24 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 12:34:24 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)
[2019-04-29 12:34:28 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 12:34:29 +0000] notice/ApiListener: Setting log position for identity ‘SATELLITE’: 2019/04/29 12:34:20
[2019-04-29 12:34:33 +0000] notice/JsonRpcConnection: Received ‘log::SetLogPosition’ message from ‘SATELLITE’
[2019-04-29 12:34:33 +0000] notice/JsonRpcConnection: Received ‘event::Heartbeat’ message from ‘SATELLITE’

[2019-04-29 12:34:44 +0000] debug/ApiListener: Not connecting to Endpoint ‘SATELLITE’ because the host/port attributes are missing.
[2019-04-29 12:34:44 +0000] notice/ApiListener: Connected endpoints: SATELLITE (1)

Thanks,
Louis

24

Ok. So you’re syncing the satellite host object to the satellite itself, and letting it run local checks (memory, disk, etc.). In terms of the ping service, this doesn’t make sense, you should remove that specific service apply from the global/satellite zone.

Still, I’m wondering why you don’t sync a client host object to the satellite, the previous one which was defined in your master zone. This is the one which doesn’t work til now, right?

Cheers,
Michael

25

Hmm, I just wanted to be able to monitor a cluster that is not reachable directly from my master, it is not only through a machine “bridge” (satellite). That’s why I chosed this architecture. But if you tell me that there is more simple way I am not against.

Cheers,

Louis