Rudder

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.

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