install.sh prints them with --plain. The terminal UI shows the same text without the [falkordb-enterprise] prefix.
Find the installer log
In the interactive terminal UI, Helm’s andkubectl’s own output goes to a log file, not to the screen. When a step fails, the installer shows the end of the log and its path:
$TMPDIR, or /tmp when that is unset. To see every line on the terminal instead, run the installer with --plain. Attach the log to a support ticket together with a support package if the Admin Server is running.
A required tool is missing
The cluster can’t be reached
get-credentials command:
--kube-context to target a context other than the current one.
The permission check fails
- Run the installer as a user with those permissions, usually
cluster-admin. See Kubernetes permissions. - If your platform refuses
SelfSubjectAccessReviewrequests, but your user has the permissions, pass--skip-auth-check.
Registry credentials are rejected
In the interactive UI, the installer checks the credentials withhelm registry login and gives you three tries:
--registry-username and --registry-password, Helm reports the failed login when the chart is pulled, for example 401 Unauthorized. In both cases, copy the username and access token again from the cluster’s install guide in the Enterprise Portal. The token is visible only to the developer and org-admin portal roles.
If you run without credentials, the installer warns:
ImagePullBackOff. Confirm the cause in the pod’s events:
unauthorized or 401 in the events means the pull Secret is missing, wrong or expired. Run the installer again with --registry-username and --registry-password, or point it at your own Secret with --image-pull-secret. See Private registries.
The Admin Server volume stays Pending
The Admin Server stores its database on a PersistentVolumeClaim. Without a defaultStorageClass, or with a class that can’t provision a volume, the claim stays Pending and so does the Admin Server pod.
No default or uniquely detectable CSI StorageClass found; disabling chart-managed VolumeSnapshotClass doesn’t stop the install, but it means volume-snapshot backups are unavailable until you set volumeSnapshotClass.driver. See Storage.
KubeBlocks doesn’t become available
registry.falkordb.cloud. Check that the cluster can reach the hosts in Installer downloads, or mirror the images as described in Private registries.
The Helm release times out
While Helm waits, the installer logsStill waiting for FalkorDB Enterprise Helm release falkordb-enterprise and prints the release’s pods, claims, jobs and recent events. Read those events for the pod that isn’t ready: a pending claim, an image pull error or a failed hook job.
The default wait is 15m. A slow cluster, for example one that provisions nodes on demand, may need more: pass --timeout 30m.
The Helm release is stuck
An interrupted install or upgrade can leave the release in a pending state. Every later run then fails with Helm’s error:1
Make sure nothing is still running
Check that no other installer,
helm command or GitOps controller is working on the release.2
Find the last good revision
pending-install, pending-upgrade or pending-rollback.3
Release the lock
For For
pending-upgrade or pending-rollback, roll back to the newest revision whose status is deployed or superseded:pending-install on a first install, there is no earlier revision. Uninstall the release, then run the installer again:4
Run the installer again
Run the same installer command as before. It upgrades from the revision you rolled back to.
Related pages
Troubleshoot deployments
Deployments stuck in updating, and pods that can’t reach the API server.
Troubleshoot licensing
Read-only mode, expired licenses and cluster binding errors.