Bug #5773
closed
Syslog configuration on agent can conflict with loghosts
Added by Benoît PECCATTE almost 10 years ago.
Updated over 9 years ago.
Description
The promise /var/rudder/configuration-repository/techniques/system/common/1.0/promises.st sets the configuration for syslog-ng on agents.
This configuration uses a syslog destination named loghost.
However, this name is generic and can already be used by someone who has loghosts.
Rudder will then send its reports to the loghost instead of rudder policy server.
- Target version set to 3.0.0~beta1
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/558
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:24ee9cd0dc7e80022d8f6d3f6ebfbe3d45c6c5b1.
Applied in changeset policy-templates:commit:b345801b5830a179f8dff28b9f71c7619b32f122.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Related to Bug #7635: syslog-ng's loghost regex does not match with set line added
Also available in: Atom
PDF