Project

General

Profile

Actions

User story #3818

closed

Add a section to debug/analyze why a Node is not sending any reports

Added by Vincent MEMBRÉ over 11 years ago. Updated almost 9 years ago.

Status:
Rejected
Priority:
1 (highest)
Category:
Documentation
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

One of the most common problem in Rudder is that reports are not sent to the server.

This may be because of various reasons : syslog configuration, time shift between the server and the node, ...

We should document where to look ( in Rudder -> Node -> node details -> Technical logs, or by running /var/rudder/cfengine-community/bin/cf-agent, syslog config files ...) and descibe what situation can be encountered (No reports, wrong reports date, ...)

depending on the situation we should propose a solution (restart syslog, correct timezone ...)

For reference, there is a FAQ for that: https://www.rudder-project.org/site/documentation/faq/some-reports-are-in-no-answer-for-a-node/


Related issues 1 (0 open1 closed)

Has duplicate Rudder - User story #7711: Add "Troubleshooting" sectionReleasedJonathan CLARKE2016-02-10Actions
Actions

Also available in: Atom PDF