Synology DS1621xs Synology High Availability SHA Troubleshooting Guide for DSM - Page 43

Warning: No passive server in the high-availability cluster, Contact Customer Service

Page 43 highlights

Chapter 2: SHA Troubleshooting 2.2.47 Warning: No passive server in the high-availability cluster Warning No passive server in the high-availability cluster. Suggestion: Click Manage to add a passive server. Description Only the active server remains in the cluster and services are still running as normal. However, your cluster is not protected by the passive server. Cause • Manually triggered by users: • From replacing the passive server • From resolving a split-brain error and choosing to keep all server data • Automatically triggered by DSM or package update errors: If one of the servers has any unresolved errors an update, Synology High Availability may remove it from the cluster to prevent service interference. Resolution Add the passive server back to the cluster as soon as possible, so that the system can continue to provide high-availability. 1. Make sure the removed server is powered on and you can sign in to it. If you cannot sign in, refer to Chapter 3: Contact Customer Service to contact Synology Technical Support for further assistance. 2. Refer to Chapter 3.2: Create a cluster of the Synology High Availability (SHA) User Guide for instructions on how to add a passive server to an existing cluster. Related Notifications • The system is removing host [My_Passive_Hostname] from the highavailability cluster [My_SHA_Hostname] Possible Logs • [info] Started to remove My_Passive_Hostname (passive server) from the cluster (My_SHA_Hostname). • [info] My_Passive_Hostname (passive server) was removed from the cluster (My_SHA_Hostname). • [info] Split-brain error manually resolved. My_Active_Hostname is now the active server and My_Passive_Hostname was removed from the cluster. • [warning] Failed to add My_Passive_Hostname (passive server) to the cluster (My_SHA_Hostname). • [warning] Host My_Passive_Hostname was removed from the cluster (My_ SHA_Hostname): Update failure. 41

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55

41
Chapter 2: SHA Troubleshooting
2.2.47 Warning: No passive server in the high-availability cluster
Warning
No passive server in the high-availability cluster.
Suggestion
: Click
Manage
to
add a passive server
.
Description
Only the active server remains in the cluster and services are still running as
normal. However, your cluster is not protected by the passive server.
Cause
• Manually triggered by users:
• From replacing the passive server
• From resolving a split-brain error and choosing to keep all server data
• Automatically triggered by DSM or package update errors: If one of the
servers has any unresolved errors an update, Synology High Availability
may remove it from the cluster to prevent service interference.
Resolution
Add the passive server back to the cluster as soon as possible, so that the
system can continue to provide high-availability.
1. Make sure the removed server is powered on and you can sign in to it.
If you cannot sign in, refer to
Chapter 3: Contact Customer Service
to
contact Synology Technical Support for further assistance.
2. Refer to
Chapter 3.2: Create a cluster
of the
Synology High Availability
(SHA) User Guide
for instructions on how to add a passive server to an
existing cluster.
Related
Notifications
• The system is removing host [My_Passive_Hostname] from the high-
availability cluster [My_SHA_Hostname]
Possible Logs
• [info] Started to remove My_Passive_Hostname (passive server) from the
cluster (My_SHA_Hostname).
• [info] My_Passive_Hostname (passive server) was removed from the
cluster (My_SHA_Hostname).
• [info] Split-brain error manually resolved. My_Active_Hostname is now
the active server and My_Passive_Hostname was removed from the
cluster.
• [warning] Failed to add My_Passive_Hostname (passive server) to the
cluster (My_SHA_Hostname).
• [warning] Host My_Passive_Hostname was removed from the cluster (My_
SHA_Hostname): Update failure.