Troubleshooting the Multi-Cluster Manager server

Troubleshoot access, service status, and log collection on the Multi-Cluster Manager server.

Problem

You cannot determine whether the Multi-Cluster Manager server is operational or access logs required to diagnose issues.

Explanation

The Multi-Cluster Manager runs multiple systemd services. If core services are stopped or fail to start, UI access, APIs, and monitoring capabilities are unavailable.

Resolution

  1. Verify that all Multi-Cluster Manager services are running.
    systemctl status
    Note: Run this command for each service.

    The source documentation checks the following services:

    • bootstrap.service
    • ui.service
    • api.service
    • alertmanager.service
    • prometheus.service
  2. If services are not running as expected, check the bootstrap service. The bootstrap starts the remaining services.
    systemctl status bootstrap.service

    Expected output indicates the service status as active (running).

  3. Review the service logs to identify startup failures.

    Service logs are stored under the /var/logs/mcm directory in subdirectories for each service. Change to the directory for the service that you want to investigate, and then review the log files.

    cd /var/logs/mcm
    cd <service-directory>
    tail *.log
    The following example shows how to review UI service logs.
    cd /var/logs/mcm
    cd ui
    tail *.log