A Multi-Server Installation Reports a Server or Service Fault

Diagnosis

Scenario

A server or service in a commissioned multi-server installation reports an unhealthy or unavailable state.

Observed Behavior

System > System Settings shows a Services state other than Services are online, a server or service state outside the accepted installation baseline, or clients lose an expected function.

Possible Causes

The displayed state alone does not establish the cause. Recovery depends on the commissioned Kubernetes infrastructure, including service placement, database topology, storage, networking, and client-access design.

Cluster maintenance and infrastructure recovery normally require specialist support and are not routine customer administration tasks.

Warning

Cluster failures can critically affect system availability and database integrity, with a risk of data loss. Contact Riedel Customer Success before intervening. Uncoordinated restarts, scaling changes, database operations, or recovery attempts can compound the fault. Do not assume that an operator or system administrator can recover the infrastructure without support guidance.

Prerequisites

Customer checks are limited to status and diagnostic information available through normal authorized access.
Have the affected server or service identity, displayed state, event time, and operational impact available.
Infrastructure recovery requires Riedel Customer Success guidance and the procedure supplied for the installation.

Resolution

Operator or system administrator: Record the affected server or service, complete displayed state, timestamp, and impact on operations. Use only normal authorized access.
Contact Riedel Customer Success through Customer Support before any infrastructure intervention. Follow its Backup and log collection guidance; if collection is unavailable, report the fault promptly and request help obtaining the files.
Leave cluster, storage, and database settings unchanged while Riedel Customer Success assesses the fault. Do not run generic reboot, service-restart, database-repair, or Kubernetes commands.
Perform recovery actions only with Riedel Customer Success guidance and the recovery procedure supplied for the installation. Preserve status and logs before changes when they confirm that collection is safe.

Verify the Result

With Riedel Customer Success, confirm that the affected services are available and verify the affected workflows against the recovery procedure and installation acceptance plan. Obtain their confirmation of any required database-integrity checks. If the installation-specific checks are unavailable or any check fails, request further guidance before returning to service. A green status indicator alone does not establish that services or data have recovered.

See High Availability.