Project

General

Profile

Actions
Copy link

Bug #12196

closed

Nodes not sending compliance reports

Added by Rémi Padrona about 6 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
-
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Hi,

I recently installed and configured rudder-agent on some machines and 5 of them strictly refuse to send compliance reports. They're the exact same machines than the others, with the same specs and configuration.
Commands rudder-agent check outputs nothing wrong. Hostnames are correctly configured in /etc/hosts file. I'm running out of ideas. I tried augmenting the agent run scheduled thinking these machines were slower than the other but nothing change. Whatever I try, these machines won't send compliance reports and therefore won't apply Rules.

Server and nodes are all running CentOS 7 and version 4.2.4.

Thnaks for your help

Files

Download all files
redmine no compliance.PNG (7.69 KB) redmine no compliance.PNG Rémi Padrona, 2018-03-08 14:21
redmine no compliance node.PNG (14.2 KB) redmine no compliance node.PNG Rémi Padrona, 2018-03-08 14:21
Actions
Copy link
 #2

Updated by Rémi Padrona about 6 years ago

I also don't have any error when running rudder agent update or rudder agent run

Actions
Copy link
 #3

Updated by Nicolas CHARLES about 6 years ago

Hi Rémi,

If rudder agent update and rudder agent run don't output any issue, then it might be a syslog issue, or network related to syslog
To troubleshoot this issue, can you check if
  • Is syslog running on the offending node ? Does restarting syslog on one of them, then running rudder agent run solves the issue ?
  • Do you have port 514 UDP open between the nodes and the server ?
  • If you go to Technical Logs, on the node detail, do you have any reports for these nodes ?
Actions
Copy link
 #4

Updated by Rémi Padrona about 6 years ago

Restarting rsyslog then running rudder agent run doesn't solve the probleme.
The port is correctly congifured.
Technical logs are empty for the 5 mentioned nodes.

Actions
Copy link
 #5

Updated by Rémi Padrona about 6 years ago

Rémi Padrona wrote:

Restarting rsyslog then running rudder agent run doesn't solve the problem.
The port is correctly configured.
Technical logs are empty for the 5 mentioned nodes.

Actions
Copy link
 #6

Updated by Rémi Padrona about 6 years ago

I solved the issue by updating rsyslog. Everything now works as expected. Thanks for your help.

Actions
Copy link
 #7

Updated by Rémi Padrona about 6 years ago

Rémi Padrona wrote:

I solved the issue by updating rsyslog. Everything now works as expected. Thanks for your help.

It seems that I spoke too fast. It made some of the nodes reporting again, but two of them still don't send any reports.

Actions
Copy link
 #8

Updated by Rémi Padrona about 6 years ago

Issue resolved. Last node was corrected by changing the server's ip by its DNS name in file /etc/rsyslog.d/rudder-agent.conf. All our nodes are now correctly sending compliance reportss.

Actions
Copy link
 #9

Updated by François ARMAND about 6 years ago

  • Status changed from New to Rejected

Great!

I'm closing the issue (it says "rejected", but it's only because no code modification was needed). Free to reopen if needed.

Actions
Copy link

Also available in: Atom PDF