Synology FS3600 Synology High Availability SHA Troubleshooting Guide for DSM 7 - Page 17

Critical: Unable to load cluster status

Page 17 highlights

Chapter 2: SHA Troubleshooting Related Notifications Possible Logs • High-availability cluster My_SHA_Hostname stopped functioning [Details: Split-brain error] • [err] A split-brain error occurred and services are suspended. • [info] Split-brain error manually resolved. My_Active_Hostname is now the active server and My_Passive_Hostname was removed from the cluster. 2.1.14 Critical: Unable to load cluster status Critical Unable to load cluster status. Details: The status of Synology High Availability is currently unavailable. Suggestion: If the problem persists, please contact Synology Technical Support for further assistance. Description Synology High Availability cluster status information cannot be displayed. Cause This is often due to a software issue. Users cannot see the cluster status in the Synology High Availability package due to missing data or system issues. Resolution Make sure that the servers are functioning and follow the steps below to refresh the cluster status: 1. Restart your web browser. 2. Go to Synology High Availability > Cluster and restart the cluster. 3. If the issue persists, refer to Chapter 3: Contact Customer Service to contact Synology Technical Support for further assistance. 2.1.15 Critical: Unexpected errors detected on the active server Critical Unexpected errors detected on active server My_Active_Hostname. Suggestion: Restart active server My_Active_Hostname. If the problem persists, please contact Synology Technical Support for further assistance. Description • The active server cannot distinguish its status or role. • The system will not perform an auto-failover in order to prevent any further errors from occurring. Cause This is often caused by a software issue. This usually occurs when the system is unstable, such as when powering on the cluster. Resolution Check the cluster status again once the system is stable. If the issue persists, refer to Chapter 3: Contact Customer Service to contact Synology Technical Support for further assistance. 15

  • 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

15
Chapter 2: SHA Troubleshooting
Related
Notifications
• High-availability cluster My_SHA_Hostname stopped functioning [Details:
Split-brain error]
Possible Logs
• [err] A split-brain error occurred and services are suspended.
• [info] Split-brain error manually resolved. My_Active_Hostname is now
the active server and My_Passive_Hostname was removed from the
cluster.
2.1.14 Critical: Unable to load cluster status
Critical
Unable to load cluster status.
Details
: The status of Synology High Availability is currently unavailable.
Suggestion
: If the problem persists, please contact Synology Technical Support for further
assistance.
Description
Synology High Availability cluster status information cannot be displayed.
Cause
This is often due to a software issue. Users cannot see the cluster status in
the Synology High Availability package due to missing data or system issues.
Resolution
Make sure that the servers are functioning and follow the steps below to
refresh the cluster status:
1. Restart your web browser.
2. Go to
Synology High Availability
>
Cluster
and restart the cluster.
3. If the issue persists, refer to
Chapter 3: Contact Customer Service
to
contact Synology Technical Support for further assistance.
2.1.15 Critical: Unexpected errors detected on the active server
Critical
Unexpected errors detected on active server My_Active_Hostname.
Suggestion
: Restart active server My_Active_Hostname. If the problem persists, please
contact Synology Technical Support for further assistance.
Description
• The active server cannot distinguish its status or role.
• The system will not perform an auto-failover in order to prevent any
further errors from occurring.
Cause
This is often caused by a software issue. This usually occurs when the
system is unstable, such as when powering on the cluster.
Resolution
Check the cluster status again once the system is stable. If the issue
persists, refer to
Chapter 3: Contact Customer Service
to contact
Synology Technical Support for further assistance.