docs: Explain benign cloud.conf load error for unclaimed nodes - #23399
Draft
nedi-app[bot] wants to merge 2 commits into
Draft
docs: Explain benign cloud.conf load error for unclaimed nodes#23399nedi-app[bot] wants to merge 2 commits into
nedi-app[bot] wants to merge 2 commits into
Conversation
…README.md explaining that the daemon error "CLAIM: cannot load cloud config ... Running with internal defaults." is expected and harmless on an unclaimed node, because cloud.conf is written only when a node is claimed. The entry notes the message path reflects the install's library directory, links to claim-status verification (api/v3/info, netdatacli aclk-state) and the claiming methods, and explicitly tells users not to change the log level or suppress the line. All factual claims were verified against the agent source before editing.
….conf error entry
|
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
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
Explain benign cloud.conf load error for unclaimed nodes. Files changed: src/claim/README.md.
User Request
sudo journalctl -xe --namespace=netdata -n 100 --no-pager | grep -iE "error|fail|invalid|cannot|unable|parse" | head -30time=2026-08-05T09:32:16.199Z comm=netdata source=daemon level=error errno="2, No such file or directory" tid=11063 msg="CLAIM: cannot load cloud co...Prompt (English)
Netdata Parent netdata.conf with everything under /data/netdata/, 12GB RAM cap, 1000GB tier split, active-active parents setup
Reason for Change
This change applies the specific user request using repository-truth evidence from the audit execution workspace.
Summary by cubic
Documented that the daemon message "CLAIM: cannot load cloud config ... Running with internal defaults." is expected and harmless on unclaimed nodes. Added a brief troubleshooting entry to src/claim/README.md covering path specifics, how to verify claim status (api/v3/info, netdatacli aclk-state), and what to do if the node should be claimed.
Written for commit 4130118. Summary will update on new commits.