Solutions

Core Servers Sync Access Keys

Modified on 2025-06-10 21:47:27 +0200

Hi Team,

Hopefully this is a simple question that I'm missing an obvious answer to. I'm adding a couple of new remote probes into my core installation. The problem I've faced is the access keys from the primary server doesn't sync over to the failover servers automatically.

Is there anyway to force a sync of these keys, or do I need to break the cluster each time to add the keys and then re-join the servers again.

Cheers.

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi Nick,

The settings of the "Setup > System Administration > Core & Probes" page are already automatically synchronized to the failover server. I just checked the configuration file of one cluster node and the keys are set properly. The issue here is, that the read only interface does not display multiple line, only the first line is displayed.

I will forward the findings to our developers, but good news, you will not need to break the cluster for every new remote probe.

Best regards, Felix

Jan, 2017 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

Core Servers Sync Access Keys

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.