Run kmq license first, find your symptom, then follow its fix. Refusals, stops and warnings carry https://docs.kubemq.io/licensing/troubleshooting#<anchor>, linking to that entry.

Commands use the names from Install on Kubernetes. For Kubernetes, replace kubemq with your namespace and messaging with your cluster name (kubectl --context YOUR_KUBE_CONTEXT get kubemqclusters.next.kubemq.io -A lists them).

Replace: YOUR_KUBE_CONTEXT — your cluster's kubectl context (kubectl config current-context).

Check the license status

Terminal

kmq license

You should see one row: STATE is active (or evaluation before a license is added), PLAN is trial or your plan, and EXPIRES is the date you expect.

If it shows license status not available: <reason> (exit code 11), sign in and ask for the full record:

Terminal

kmq auth login --installation kubemq --username admin

If you installed with Docker rather than kmq:

Terminal

kmq auth login --api-address http://127.0.0.1:8080 --context-name kubemq --username admin

Then:

Terminal

kmq license --details

If the container is stopped, kmq license prints a connection error, no status row, and exits with code 5.

Read its last log lines instead:

Terminal

docker logs --tail 50 kubemq

Terminal

kmq license --kube-context YOUR_KUBE_CONTEXT

Replace: YOUR_KUBE_CONTEXT — the kubectl context of your cluster.

You should see three rows, one per server, each active with the same PLAN and EXPIRES.

If it finds no cluster (exit code 3), list them, then add --namespace and --cluster:

Terminal

kubectl --context YOUR_KUBE_CONTEXT get kubemqclusters.next.kubemq.io -A

If it shows license status not available: cluster has no license status (exit code 11), the operator is older; read the LicenseInvalid and ReplicasOverLicenseCap conditions:

Terminal

kubectl --context YOUR_KUBE_CONTEXT -n kubemq describe kubemqclusters.next.kubemq.io messaging

A server that is not running shows refused. Read its last log lines (use its name; for a pod in CrashLoopBackOff, add --previous):

Terminal

kubectl --context YOUR_KUBE_CONTEXT -n kubemq logs messaging-0 --tail 50

What each state means: How licensing works.

Exit codes

The server's exit codes. For kmq license codes, see How licensing works.

Code	Meaning	Where to look
`0`	Clean shutdown.	Nothing to do.
`1`	Any other failure, including a configuration error such as a `license` block left in an old configuration file.	The first error line in the log. For the `license` block, Will not start: no license.
`3`	A licensing refusal or stop.	The anchor at the end of the last log line.
`4`	Unsupported deployment: a pod the operator did not create, clustering on Docker, fewer than three servers on Kubernetes, or a server started outside a container.	Will not start: exit code 4

Symptoms

Will not start

What you see	Cause	Fix
`#no-license-input`, or a message that no evaluation can start: Kubernetes, existing data, incomplete files, unavailable, already used	No license is set, and no evaluation can start here	Add a license
`#invalid-signature`, or the cluster condition `LicenseInvalid`	The license cannot be read or is not genuine	Restore the license
`#fingerprint-mismatch`	The license belongs to another installation	Check the installation
`#first-boot-bad-request`	The key is malformed	Re-save the key
`#first-boot-bad-key`	KubeMQ refused the key	Check the key
`#first-boot-unreachable`, or "Signup-free evaluation must reach license.kubemq.io"	The first start could not reach KubeMQ	Open the connection
`#cluster-over-cap`, or the conditions `ReplicasOverLicenseCap` and `ReplicasFrozen`	More servers than the license allows	Match the server count
`#untrusted-kid` at first start	The server release is too old	Use the latest image
`#clock-rollback`	The clock moved back	Set the clock
`#store-not-persistent` with exit code 3, or "Cannot save evaluation files"	The data folder cannot be written	Fix the data folder
Exit code 4	Unsupported deployment	Use a supported setup
A pod in `CrashLoopBackOff`	The server exits at every start	Read the run that stopped
`kmq license` shows the old license, or `refused`, after a change	The new license was not accepted	Check the change

Stopped while running

What you see	Cause	Fix
`#lease-and-grace-exhausted`, or `STATE` `stopping`	The license could not be renewed in time	Restore renewals
`#evaluation-expired`, or "This evaluation has finished"	The evaluation ended	Add a license
`#offline-expired`	The offline license file reached its end date	Apply a new file
`#revoked`	KubeMQ revoked the license	Contact support
`#clock-rollback` or `#cluster-over-cap`	See Will not start	Set the clock · Match the server count
`#clock-skew`	The clock differs from KubeMQ's and the license could not be renewed	Synchronize the clock
`STATE` `refused` on Kubernetes	A server stopped or cannot start	Read its log

Warnings

What you see	Cause	Fix
`#grace-countdown`, or `STATE` `grace`	The server cannot reach KubeMQ	Restore the connection
`STATE` `expiring`	14 days or fewer to the license end	Renew or buy through Plans compared
`#lease-refused`	KubeMQ did not renew the license	Read the expiry
`#revocation-seen`	KubeMQ started to revoke the license	Contact support
`#over-cap`	More installations than licensed	Remove the extras
`#silent-usage`	Usage reports are not arriving	Allow usage reports
`#clock-skew`	The clock differs from KubeMQ's	Synchronize the clock
`#store-not-persistent` at start	The data folder is not on a volume	Mount a volume
`#missing-kube-system-permission`	The server cannot read the cluster identity	Grant the permission
`#both-key-and-file`	A key and an offline license file are both set	Remove one
`#untrusted-kid` on a running server	The server release is too old	Use the latest image
`#invalid-signature` on a running server	KubeMQ could not verify the license	Restore the license
"Your KubeMQ evaluation expires in"	The evaluation is about to end	Add a license

Will not start: no license

What you see: exit code 3 and one of these lines:

Server log

license: this installation has an accepted explicit license; restore its configured license input https://docs.kubemq.io/licensing/troubleshooting#no-license-input
license: Kubernetes needs a license key. Get a free 30-day trial key (choose Kubernetes, 3 servers) at https://onboarding.kubemq.io/trial. https://docs.kubemq.io/licensing/troubleshooting#no-license-input
license: A license key was expected. Set KUBEMQ_LICENSE_KEY. Get a free 30-day trial key at https://onboarding.kubemq.io/trial. https://docs.kubemq.io/licensing/troubleshooting#no-license-input
license: The evaluation files are incomplete: the saved key has no installation identity. Set KUBEMQ_LICENSE_KEY with a free 30-day trial key from https://onboarding.kubemq.io/trial to keep your data; preserve the data volume and installation identity. https://docs.kubemq.io/licensing/troubleshooting#no-license-input
license: Signup-free evaluation is unavailable. Get a free 30-day trial key at https://onboarding.kubemq.io/trial and set KUBEMQ_LICENSE_KEY. https://docs.kubemq.io/licensing/troubleshooting#no-license-input
license: This installation has already used its evaluation. Set KUBEMQ_LICENSE_KEY with a free 30-day trial key from https://onboarding.kubemq.io/trial to keep your data; preserve the data volume and installation identity. https://docs.kubemq.io/licensing/troubleshooting#no-license-input

A license block in a configuration file exits with code 1:

Server log

error on load config file: configuration validation error: config source <file> carries a license block ("<key>"), which is no longer accepted: licensing is environment-only. Remove it and set KUBEMQ_LICENSE_KEY (online key), or KUBEMQ_LICENSE_FILE / KUBEMQ_LICENSE_DATA (offline file), optionally … See https://docs.kubemq.io/licensing/troubleshooting#no-license-input

Why: no license is set, and an evaluation starts only once, on a new single Docker server.

Fix:

Add a license: Install with kmq, Install with Docker or Install on Kubernetes.
If the line names an accepted license, put that license back; an evaluation never restarts here.
For a license block, delete it, then do step 1 (Move from legacy KubeMQ).

Will not start: license not genuine or unreadable

What you see: exit code 3 and one of the first four lines; on a running server, one of the last two:

Server log

license: cannot read configured offline license file: <error> https://docs.kubemq.io/licensing/troubleshooting#invalid-signature
license: offline license file rejected: <reason> https://docs.kubemq.io/licensing/troubleshooting#invalid-signature
license: license token rejected (expected <mode>, source <source>): <reason> https://docs.kubemq.io/licensing/troubleshooting#invalid-signature
license: accepted license record is malformed; restore the record from a trusted backup https://docs.kubemq.io/licensing/troubleshooting#invalid-signature
"msg":"license refresh refused with an unsigned answer; keeping the cached lease until the grace window ends", … "status":<status>,"code":"invalid_token","run_until":"<time>", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#invalid-signature"
"msg":"license lease not adopted: older than the current lease (replay); keeping the current lease", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#invalid-signature"

Why: the license cannot be read or failed verification: a file not mounted, cut or re-wrapped, or a changed licensing record on the data volume.

Fix:

On Kubernetes, check that the Secret key in licenseFileSecretRef holds the whole file.
Use the file KubeMQ sent, unchanged, from -----BEGIN KUBEMQ LICENSE----- to -----END KUBEMQ LICENSE-----.
If the line names the accepted license record, restore the volume from a trusted backup or contact support. Never edit or delete its files.

Will not start: license issued for another installation

What you see: exit code 3 and one of these lines:

Server log

license: offline file is bound to <n> installation(s) and this installation ("<id>") is not one of them https://docs.kubemq.io/licensing/troubleshooting#fingerprint-mismatch
license: offline file is bound to <n> installation(s) and this installation ("<id>", persisted id) is not one of them; on Kubernetes grant the service account get on namespaces (resourceName kube-system) so the cluster fingerprint can be read https://docs.kubemq.io/licensing/troubleshooting#fingerprint-mismatch
license: online lease is bound to installation "<id>" but this installation is "<id>" https://docs.kubemq.io/licensing/troubleshooting#fingerprint-mismatch

Why: a license bound to another installation. A new cluster, a copied data volume, or a server that cannot read its cluster identity is another installation.

Fix:

If the log also shows #missing-kube-system-permission, fix that first.
Otherwise save your cluster's fingerprint and send fingerprint.json to KubeMQ through Plans compared:
Terminal
```
kmq license fingerprint --kube-context YOUR_KUBE_CONTEXT --namespace kubemq --out fingerprint.json
```
Replace: YOUR_KUBE_CONTEXT — your cluster's kubectl context.
On Docker, contact support.

A warning ending "re-activating with the license key" needs no action.

Offline license file ended

What you see:

Server log

license: offline license file expired at <time> https://docs.kubemq.io/licensing/troubleshooting#offline-expired

Why: the offline license file reached its end date.

Fix: request and apply a new file: Install air-gapped.

Will not start: license request rejected

What you see:

Server log

license: first boot: the license backend rejected the activation request as malformed 3 times (HTTP 400 <code>: <message>); check KUBEMQ_LICENSE_KEY, the fingerprint and the server version https://docs.kubemq.io/licensing/troubleshooting#first-boot-bad-request
license: first boot: cannot build the activation request for KUBEMQ_LICENSE_ENDPOINT="<value>": <error> https://docs.kubemq.io/licensing/troubleshooting#first-boot-bad-request
license: evaluation request refused (HTTP <status>) https://docs.kubemq.io/licensing/troubleshooting#first-boot-bad-request

Why: KubeMQ could not read the request, usually a malformed key: quotes, spaces, a line break, or a KUBEMQ_LICENSE_KEY= prefix in the key file.

Fix:

Save the key alone on one line, then repeat your install page's license step.
If the line names KUBEMQ_LICENSE_ENDPOINT, correct it: Core & Licensing.
Use the latest image. If it fails, contact support.

Will not start: key refused

What you see:

Server log

license: first boot: the license backend rejected the license key 3 times (HTTP 401 <code>); check KUBEMQ_LICENSE_KEY https://docs.kubemq.io/licensing/troubleshooting#first-boot-bad-key

Why: KubeMQ refused the key three times. It may be mistyped or replaced, or the license disabled or ended.

Fix:

Compare the server's key (the key file on Docker, the Secret on Kubernetes) with the latest key KubeMQ sent.
If it is correct and current, contact KubeMQ through Plans compared.

Will not start: cannot reach KubeMQ

What you see:

Server log

license: first boot: the license backend at https://license.kubemq.io (KUBEMQ_LICENSE_ENDPOINT) stayed unreachable for <duration> (last error: <error>); if this installation cannot reach the endpoint request a pre-activated license file https://docs.kubemq.io/licensing/troubleshooting#first-boot-unreachable
license: Signup-free evaluation must reach license.kubemq.io. Check that outbound HTTPS to license.kubemq.io:443 is allowed, or set KUBEMQ_LICENSE_KEY with a free 30-day trial key from https://onboarding.kubemq.io/trial, or use an offline license file. https://docs.kubemq.io/licensing/troubleshooting#first-boot-unreachable

Why: a first start must reach KubeMQ. An evaluation gives up after 2 minutes and a license key after 30 minutes (Core & Licensing).

Fix:

Check that the host answers "status":"ok":

Terminal

curl -sS https://license.kubemq.io/api/healthz

On Windows, in PowerShell:

Terminal

curl.exe -sS https://license.kubemq.io/api/healthz

Check from a container:

Terminal

docker run --rm -e HTTPS_PROXY -e NO_PROXY curlimages/curl -sS https://license.kubemq.io/api/healthz

Or from a pod:

Terminal

kubectl --context YOUR_KUBE_CONTEXT -n kubemq run license-egress-check --rm -i --restart=Never --image=curlimages/curl -- -sS https://license.kubemq.io/api/healthz

Replace: YOUR_KUBE_CONTEXT — your cluster's kubectl context.

If the image cannot be pulled, use the host check.

Allow HTTPS to license.kubemq.io, or set a proxy: Requirements and supported setups.
Otherwise, use an offline license file: Install air-gapped.

Warning: key and offline file both set

What you see:

Server log

"msg":"license boot warning", … "anchor":"both-key-and-file","detail":"both KUBEMQ_LICENSE_KEY and KUBEMQ_LICENSE_FILE/KUBEMQ_LICENSE_DATA are set; the file wins and the key is ignored"

Why: the server uses the file and never contacts KubeMQ.

Fix: remove the file settings to run online, or the key to run offline.

Will not start: more servers than the license allows

What you see:

Server log

license: cluster configuration <setting> names <n> members but the license allows kmq.max_instances=<n>; reduce the member list or upgrade the license https://docs.kubemq.io/licensing/troubleshooting#cluster-over-cap
license: cluster stayed over the license cap (<n> members > kmq.max_instances=<n>) for <n> consecutive minutes https://docs.kubemq.io/licensing/troubleshooting#cluster-over-cap
license: Clustering requires operator-managed Kubernetes and an approved license for at least three servers. Request approval at https://onboarding.kubemq.io/trial. https://docs.kubemq.io/licensing/troubleshooting#cluster-over-cap

Why: the cluster has more servers than the license covers. A clustered evaluation is refused too.

Fix: the operator never resizes a cluster. Buy a license for your server count through Plans compared, or move traffic to a licensed-size cluster.

Will not start: exit code 4

What you see: exit code 4 and a line such as:

Server log

kubemq on Kubernetes is supported only through the KubeMQ operator: this pod was not created by the operator, so the server refuses to start. Install the operator and create a KubemqCluster instead of applying a StatefulSet, Deployment or Pod directly — https://docs.kubemq.io/deploy/kubernetes-helm
unsupported KubeMQ deployment: Docker and Podman support a single non-clustered server; use single-node Docker or Podman, or an operator-managed Kubernetes cluster with at least 3 servers; migrate existing installations before upgrading — https://docs.kubemq.io/deploy/supported-deployments

Why: not a license problem. KubeMQ runs only on one Docker or Podman server, or an operator-created Kubernetes cluster of three or more servers.

Fix: follow Install on Kubernetes; see Requirements and supported setups.

Stopped: could not reach KubeMQ for too long

What you see:

Server log

license: lease expired at <time> and the <n>-day grace window ended at <time> without a refresh https://docs.kubemq.io/licensing/troubleshooting#lease-and-grace-exhausted
license: evaluation lease and grace expired; reconnect to the license backend https://docs.kubemq.io/licensing/troubleshooting#lease-and-grace-exhausted

Why: the license was not renewed before the time under RUNS UNTIL (How licensing works).

Fix:

If the network was the cause (see PROBLEM in kmq license, or the log lines before the stop), restore it. Otherwise renew or buy through Plans compared.
Start the server.

Warning: cannot reach KubeMQ

What you see:

Server log

"msg":"license warning", … "anchor":"grace-countdown","detail":"lease expired at <time> and the backend has not answered; running on grace, <n> day(s) left until <time>"

Why: the server cannot reach KubeMQ. It keeps running until the time under RUNS UNTIL.

Fix: restore the connection before then, using the connection checks.

Stopped: license revoked

What you see:

Server log

license: license <id> revoked (<reason>); <n> signed assertions confirmed https://docs.kubemq.io/licensing/troubleshooting#revoked
license: license <id> remains revoked (<reason>); … https://docs.kubemq.io/licensing/troubleshooting#revoked
license: license <id> was revoked: <n> signed revocation assertions were confirmed before the last stop (reason: <reason>); obtain a reinstated license with a newer token_version from the licensing authority; preserve cached state <path> and enforcement state <path> https://docs.kubemq.io/licensing/troubleshooting#revoked

Why: KubeMQ revoked this license. The server finishes current work, stops, and kmq license shows stopping. It will not start with this license.

Fix: contact support. Never delete files on the data volume.

Warning: revocation received

What you see:

Server log

"msg":"license warning", … "anchor":"revocation-seen","detail":"a signed revocation assertion has been seen <n> time(s) (reason: <reason>); …"

Why: KubeMQ has started to revoke this license.

Fix: contact support now.

Will not start or stopped: clock moved back

What you see:

Server log

license: wall clock <time> is more than 10m0s behind the persisted high-water mark <time> and the license backend is unreachable; correct the clock and restore allowed connectivity; preserve the enforcement record <path> https://docs.kubemq.io/licensing/troubleshooting#clock-rollback
license: wall clock <time> is behind the persisted high-water mark <time> on an offline license; correct the clock; preserve the enforcement record <path> https://docs.kubemq.io/licensing/troubleshooting#clock-rollback

Why: the clock is earlier than a time this server already saw.

Fix:

Set the clock with NTP (Network Time Protocol), then start the server.
If the clock is right, contact support. Never delete files on the data volume.

Warning or stop: clock differs from KubeMQ

What you see:

Server log

"msg":"local clock differs from the license backend", … "skew_seconds":<n>, … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#clock-skew"
license: lease expired and the local clock differs from the license backend by <n>s (more than …) https://docs.kubemq.io/licensing/troubleshooting#clock-skew
"msg":"server_time disagrees with the signed lease iat; ignoring server_time", … "server_time":"<time>","lease_iat":"<time>","tolerance":"<duration>", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#clock-skew"
"msg":"usage report refused as terminal; the cursor advances past this row", … "status":<status>,"error":"<error>", … "docs_url":"https://docs.kubemq.io/licensing/troubleshooting#clock-skew"

Why: the server's clock differs from KubeMQ's; if the license also cannot be renewed, the server stops.

Fix: synchronize the clock with NTP, then start the server if it stopped.

Warning: more installations than licensed

What you see:

Server log

"msg":"license warning", … "anchor":"over-cap","detail":"this license exceeds kmq.max_instances=<n> (over cap); the server keeps running, contact KubeMQ"

Why: more installations use this license than it allows; the server keeps running.

Fix:

Stop the extra installations, or get a higher limit through Plans compared.
Look for containers started without their volume, and for servers missing the cluster identity permission.

Warning: usage reports not arriving

What you see:

Server log

"msg":"license warning", … "anchor":"silent-usage","detail":"the license backend has received no usage from this license for …; leases are capped at … until usage reports resume"
"msg":"license refresh answered a server error; keeping the cached lease", … "status":<status>,"code":"silence_suspended", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#silent-usage"

Why: a firewall or proxy lets renewals through but not usage reports. KubeMQ eventually stops renewing.

Fix: let usage reports through like renewals: Data sent to KubeMQ.

Warning or refusal: data folder not persistent

What you see: a warning at start:

Server log

"msg":"license boot warning", … "anchor":"store-not-persistent","detail":"store path \"<path>\" is on the root filesystem, not a mounted volume; the license cache, instance id and usage cursor will not survive a container replacement"

Or exit code 3 and a refusal:

Server log

license: cannot durably save accepted license record: <error> https://docs.kubemq.io/licensing/troubleshooting#store-not-persistent
license: cannot persist the installation id: <error> https://docs.kubemq.io/licensing/troubleshooting#store-not-persistent
license: Cannot save evaluation files in store folder <path>. Make the store writable, or get a key at https://onboarding.kubemq.io/trial. https://docs.kubemq.io/licensing/troubleshooting#store-not-persistent

Why: the data folder is not on a volume (it dies with the container) or is not writable.

Fix:

On Docker, mount the kubemq-data volume at /kubemq/store.
On Kubernetes, set volume.size and volume.storageClass in the cluster values. Never set volume: null.
For the refusal, make the folder writable by user 1001 and free disk space. Never delete files in it.

Warning: cannot read the cluster identity

What you see:

Server log

"msg":"license boot warning", … "anchor":"missing-kube-system-permission","detail":"could not read the kube-system namespace UID (<error>); the service account needs a ClusterRole with get on namespaces (resourceName kube-system); falling back to the persisted instance id"

Why: without the kube-system namespace, each server counts as its own installation and an offline license file does not match.

Fix:

Check the permission. It must print yes:

Terminal

kubectl --context YOUR_KUBE_CONTEXT auth can-i get namespace/kube-system --as=system:serviceaccount:kubemq:kubemq-cluster-next

Replace: YOUR_KUBE_CONTEXT — your cluster's kubectl context.

If it prints no, reinstall the KubeMQ Helm releases; they create that ServiceAccount and its role.
Restart the servers one at a time:
Terminal
```
kubectl --context YOUR_KUBE_CONTEXT -n kubemq delete pod messaging-0
```
Then repeat for messaging-1 and messaging-2.

Will not start: server too old for KubeMQ's signing key

What you see:

Server log

license: first boot: the license backend signs with a key this server does not trust (trusted: <ids>); upgrade the server https://docs.kubemq.io/licensing/troubleshooting#untrusted-kid
"msg":"license refresh refused with an unsigned answer; keeping the cached lease until the grace window ends", … "status":422,"code":"untrusted_kid", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#untrusted-kid"

Why: this release does not trust KubeMQ's current signing key. A running server keeps running until the time under RUNS UNTIL.

Fix: use the latest image: Upgrade KubeMQ.

Warning: renewal refused

What you see:

Server log

"msg":"license refresh refused with an unsigned answer; keeping the cached lease until the grace window ends", … "status":<status>,"code":"<code>","run_until":"<time>", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#lease-refused"
"msg":"license refresh answered HTTP 200 without a decodable lease; keeping the cached lease", … "endpoint":"<url>", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#lease-refused"
"msg":"license refresh answered a server error; keeping the cached lease", … "status":<status>,"code":"<code>", … "doc_url":"https://docs.kubemq.io/licensing/troubleshooting#lease-refused"

Why: KubeMQ did not renew the license, its service failed, or a proxy answered instead. The server keeps running until the time under RUNS UNTIL.

Fix:

For "refused", read EXPIRES in kmq license. In the past, renew through Plans compared; in the future, the license was disabled: contact support.
For "HTTP 200", check the proxy between the server and license.kubemq.io.
For "a server error", wait; contact support if it continues.

Stopped: evaluation ended

What you see:

Server log

license: This evaluation has finished. Set KUBEMQ_LICENSE_KEY with a free 30-day trial key from https://onboarding.kubemq.io/trial to keep your data; preserve the data volume and installation identity. https://docs.kubemq.io/licensing/troubleshooting#evaluation-expired
"msg":"evaluation expires soon", … "anchor":"evaluation-expired","detail":"Your KubeMQ evaluation expires in <n> days. Get a free 30-day trial key at https://onboarding.kubemq.io/trial."

Why: the 14-day evaluation ended; reconnecting does not extend it.

Fix: add a trial key or license key on the same volume: Install with kmq or Install with Docker. Removing the volume deletes all messages.

New license not shown after a change

What you see: after a license change, kmq license shows the old PLAN or EXPIRES, or refused.

Why: the server did not accept the new license at restart.

Fix:

Check that the key file holds only the key, on one line, and that only one license source is set.
Make sure the server can reach license.kubemq.io, then restart it.
To recover, put the previous license back. Never delete files on the data volume.

Get help

Send support:

The output of kmq license --details -o json (it never includes the key).
The last 50 log lines of each affected server (Check the license status).
How you installed: kmq, Docker or Helm.

Troubleshooting

Check the license status

Exit codes

Symptoms

Will not start: no license

Will not start: license not genuine or unreadable

Will not start: license issued for another installation

Offline license file ended

Will not start: license request rejected

Will not start: key refused

Will not start: cannot reach KubeMQ

Warning: key and offline file both set

Will not start: more servers than the license allows

Will not start: exit code 4

Stopped: could not reach KubeMQ for too long

Warning: cannot reach KubeMQ

Stopped: license revoked

Warning: revocation received

Will not start or stopped: clock moved back

Warning or stop: clock differs from KubeMQ

Warning: more installations than licensed

Warning: usage reports not arriving

Warning or refusal: data folder not persistent

Warning: cannot read the cluster identity

Will not start: server too old for KubeMQ's signing key

Warning: renewal refused

Stopped: evaluation ended

New license not shown after a change

Get help

On this page