Project

General

Profile

Actions

User story #12821

closed

No reports: 100.00% but agent interactive compliance OK => need a FAQ entry

Added by Nicolas ECARNOT almost 6 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
-
UX impact:
Suggestion strength:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Name check:
Fix check:
Regression:

Description

Hello,

[Old cfEngine user, but Rudder newbie]

I've just installed Rudder 4.3.2 on CentOS 7.5, then on 2 more nodes I installed the agent.
I've just added a MOTD directove in the default globale rule, and I see everything seems to go fine.

But in the dashboard, I see "No report: 100.00%" on the 2 nodes and on the hub.
I tried to run "rudder agent inventory" and all is fine.
I tried to run "rudder agent run" and it also seems fine :

Rudder agent 4.3.2.release
Node uuid: c3eb2724-5689-4210-825f-91e7273c86d0
Start execution with config [20180621-154638-fb5cad5]

M| State Technique Component Key Message
E| compliant Common Update Policy, tools and configuration library are already up to date. No action required.
E| compliant Common ncf Initialization Configuration library initialization was correct
E| compliant Common Security parameters The internal environment security is acceptable
E| n/a Common Process checking Rudder agent proccesses check is done by the rudder-agent cron job
E| compliant Common CRON Daemon Cron daemon status was correct
E| compliant Common Log system for reports Logging system for report centralization is already correctly configured
E| compliant Common Binaries update The agent binaries in /var/rudder/cfengine-community/bin are up to date
E| compliant Inventory inventory Next inventory scheduled between 00:00 and 06:00
E| compliant MOTD MOTD Configuration The MOTD file was correct
E| n/a Common Monitoring No Rudder monitoring information to share with the server

  1. Summary #####################################################################
    => 10 components in Enforce mode
    -> 8 compliant
    -> 2 not-applicable
    Execution time: 1.39s ################################################################################

On each node details, I can see the inventory went well as I can see its details.
But I see nothing in the Technical logs tab on any node.

Actions #1

Updated by Nicolas ECARNOT almost 6 years ago

Hello,

Thanks to IRC guys (Vince and peck), I found out that my previous cfEngine setup did add some parameters blocking the rsyslog transmission.

Do you think it would be worth that the installation process ensures that both server and nodes's /etc/rsyslog.conf files are correctly configured? (In my case, I had added a line in rsyslog.conf with local6, and another file in rsyslog.d dealing with cfengine logs).

In a pure pristine hub+nodes install, this should never happen.

Actions #2

Updated by François ARMAND over 5 years ago

  • Subject changed from No reports: 100.00% but compliance OK to No reports: 100.00% but agent interactive compliance OK => need a FAQ entry
  • Category set to Documentation
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
  • Effort required set to Small
  • Priority changed from 0 to 82

Hello, sorry for the very long time without an answer, we missed that ticket.

We are already doing some check on rsyslog, but we need to accept that the user can modify a syslog file, and the domain is quite diverse. So for now, we don't have a good one-size-fit-all solution. But we are currectly working on a new agent-server protocol, freed of syslog, which will be much better isolated from user services (for the benefits of all).

We should write a faq entry about "how to debug no reports from an agent".

Actions #3

Updated by François ARMAND over 5 years ago

  • Assignee set to Nicolas CHARLES
  • Priority changed from 82 to 81
Actions #4

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Priority changed from 81 to 0
Actions #5

Updated by Alexis Mousset over 5 years ago

  • Status changed from Pending technical review to Released

Published.

Actions #6

Updated by Alexis Mousset over 4 years ago

  • Tracker changed from Bug to User story
  • Project changed from Rudder to Rudder websites
  • Category deleted (Documentation)
  • Severity deleted (Major - prevents use of part of Rudder | no simple workaround)
  • Priority deleted (0)
Actions

Also available in: Atom PDF