Bug #22177
closed
No receive compliance reports
Description
Rudder Version 4.3.1
j'ai ce phenomène, fichier joint sur plusieurs serveur. les deploiement se font bien mais je n'ai aucun état de ces deploiement.
merci pour votre aide
Files
Updated by Alexis Mousset over 1 year ago
Note: Rudder 4.3 is EOL since January 2019 and had no security patches since then, so we strongly advice to always use a maintained versioned.
Given the symptoms the problem seems to be related to syslog flows (udp or tcp/514) not correctly allowed from nodes to the server or a problem with the local syslog daemon on the nodes (rsyslog probably).
Syslog reporting has been completely replaced since Rudder 6 and we probably won't be able to help you much further with this problem.
Updated by nabyle soufi over 1 year ago
Alexis Mousset wrote in #note-1:
Note: Rudder 4.3 is EOL since January 2019 and had no security patches since then, so we strongly advice to always use a maintained versioned.
Given the symptoms the problem seems to be related to syslog flows (udp or tcp/514) not correctly allowed from nodes to the server or a problem with the local syslog daemon on the nodes (rsyslog probably).
Syslog reporting has been completely replaced since Rudder 6 and we probably won't be able to help you much further with this problem.
Bonjour,
Merci pour votre reponse. le probleme est que je ne peux pas upgrader vers la 6.0 car mes noeuds sont en Redhat 6.10. la 6.0 ne supporte pas cette version linux pour les agent
Updated by Alexis Mousset over 1 year ago
- Status changed from New to Rejected
je ne peux pas upgrader vers la 6.0 car mes noeuds sont en Redhat 6.10. la 6.0 ne supporte pas cette version linux pour les agent
The agent for RHEL/CentOS 6 is actually free until 6.2, but it has reached end-of-life as well.
If you want to use RHEL 6 with a supported version of Rudder (7.2 currently) it is possible with a subscription, you can more details and contact info on our website.
Regarding the reporting issue you have on 4.3 we can't do much more than advice you to check syslog flows (udp or tcp/514) or local syslog daemon on the nodes (rsyslog probably). I'm hence closing this ticket.