Added troubleshooting page for license check failures#429
Open
zzzeebra wants to merge 1 commit into
Open
Conversation
…ures New page listing canonical License Server client errors (INVALID_LICENSE_SECRET 101, INVALID_LICENSE_CHECK_SECRET 107, CONNECTION_ERROR 400, PKIX SSL trust failure, GENERAL_ERROR) with diagnostic steps and per-code recovery instructions. Documents the new ERROR banner format, container exit code semantics, and the docker-compose restart: on-failure recommendation that avoids the infinite restart loop on unresolved license errors. Linked from the prerequisites section of what-is-license-server.mdx where the "may shut down" behavior was previously only vaguely mentioned. Added a Troubleshooting group to the License Server sidebar.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new docs page documenting how License Server client failures manifest in ThingsBoard PE logs, and how to fix each canonical error code.
The existing
what-is-license-server.mdxonly vaguely says the client "may shut down the ThingsBoard instance" — leaving operators to debugINVALID_LICENSE_SECRET(101),INVALID_LICENSE_CHECK_SECRET(107),CONNECTION_ERROR(400), and PKIX/SSL failures from scratch. This page lists each mode with a concrete recovery procedure.Changes
docs/license-server/troubleshooting:*** LICENSE CHECK FAILED ({code} - code {n}) ***and a grep example to locate it across logs.-1→ POSIX255).restart: on-failurerecommendation that avoids the infinite-restart-loop symptom.what-is-license-server.mdx(right where the "may shut down" mention is).Troubleshootinggroup in the License Server sidebar.Companion PR
Backend PR introducing the ERROR banner the page references: thingsboard/thingsboard-pe#4799.
Test plan
npm run buildclean (3818 pages, no errors related to the new content)