Rudder

Hello

I will like to push this option too. This had caused us problems in the past and it is also causing problems now. The issue is that all the services that relies on syslog for logging get stuck and stop responding when the syslog server on rudder is not available which, as you imagine, is not welcomed at all.

Also, is there any way we can customise this in the meantime (even if it will be overwritten by Rudder upgrades)? Thank you

Hey

Any update on this? The problem is still active and can cause lots of headaches if it is not fixed.

Here is a workaroudn for this issue, for rsyslog

On the rudder policy server, in /var/rudder/configuration-repository/techniques/system/common/1.0/promises.st, replace

    !windows.rsyslogd.!policy_server::
      "/etc/rsyslog.d/rudder-agent.conf" 
        edit_line => append_if_no_lines("#Rudder log system${const.n}if $syslogfacility-text == 'local6' and $programname startswith 'rudder' then @@${server_info.cfserved}:&SYSLOGPORT&${const.n}if $syslogfacility-text == 'local6' and $programname startswith 'rudder' then ~"),
        create => "true",
        edit_defaults => empty_backup,
        classes => kept_if_else("rsyslog_kept", "rsyslog_repaired" , "rsyslog_failed");

by

    !windows.rsyslogd.!policy_server::
      "/etc/rsyslog.d/rudder-agent.conf" 
        edit_line => append_if_no_lines("#Rudder log system${const.n}if $syslogfacility-text == 'local6' and $programname startswith 'rudder' then @${server_info.cfserved}:&SYSLOGPORT&${const.n}if $syslogfacility-text == 'local6' and $programname startswith 'rudder' then ~"),
        create => "true",
        edit_defaults => empty_backup,
        classes => kept_if_else("rsyslog_kept", "rsyslog_repaired" , "rsyslog_failed");

then execute, in the folder /var/rudder/configuration-repository/techniques/system/common/1.0/, the following commands:

git add promises.st
git commit -m "Use UDP rather than TCP for rsyslog" 

and then, in the web interface, go to administration page, and click on "Update technique now".

If you are not using rsyslog, please tell me so that I can offer another workaround

Applied in changeset rudder-techniques|fbc428842a9efc9370ece414811bb802441a3909.