Troubleshooting

The container stops or keeps restarting right after starting

CDM refuses to run with an incomplete configuration and names each missing value in its log. Read docker compose logs cdm, or docker logs cdm if you started it with docker run. The usual causes are a missing CDM_SECRET_KEY, a key shorter than 32 characters, or a missing or malformed OIDC_* value, for example an OIDC_ROLE_MAPPING that is not valid JSON.

The redirect URI does not match. It has to be exactly <CDM_PUBLIC_URL>/oidc, including the scheme and the port. See Single Sign-On.

CDM cannot read the provider's discovery document. Check that OIDC_DISCOVERY_URL is right and reachable from the CDM host. CDM verifies the provider's certificate, so a provider signed by a private CA needs that CA; see What you need.

You can log in but cannot add clusters

Your groups mapped to viewer. Add your group to OIDC_ROLE_MAPPING as admin, recreate the container, then sign out and sign in again: a session keeps the role it signed in with. If it still happens, the group claim is not arriving; see Checking what CDM received.

A cluster stays unreachable

The cluster tile shows the reason. Check that the host can reach the URL, that the scheme and port are right, and that the token or user still exists on the cluster. Self-signed certificates are accepted and are never the cause.

A number looks too low

An unreachable cluster contributes nothing rather than a zero, and CDM marks how many clusters each total covers. Look for a cluster that is not currently reachable. Reading the Dashboard explains how incomplete data is shown.

A feature is missing for one cluster

CDM shows what is unavailable and why. For plain Ceph clusters that is disks and SMART health, which CDM does not read yet, charts, which plain Ceph cannot serve, HA groups, S3 multisite, task history, past log ranges, and near-full and full forecasts.

Docker warns that the image's platform does not match

CDM is published for linux/amd64 only, so an ARM host runs it under emulation. Ask for the amd64 image explicitly to silence the warning; see Running on an ARM machine.

Getting help

The version your installation runs is shown at the bottom of the navigation menu. Name it in any support request. Questions, or want CDM to do something it does not do yet? https://croit.io

Licence

Use of the CDM image is governed by the licence inside it at /LICENSE.md.

On this Page: