Actions
Bug #5773
closed
Syslog configuration on agent can conflict with loghosts
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
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.
Updated by Benoît PECCATTE about 10 years ago
- Target version set to 3.0.0~beta1
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/558
Updated by Benoît PECCATTE about 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
Updated by Benoît PECCATTE about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:24ee9cd0dc7e80022d8f6d3f6ebfbe3d45c6c5b1.
Updated by Jonathan CLARKE about 10 years ago
Applied in changeset policy-templates:commit:b345801b5830a179f8dff28b9f71c7619b32f122.
Updated by Vincent MEMBRÉ about 10 years ago
- 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.
- Announcement
- Changelog
- "Download information": https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Vincent MEMBRÉ about 9 years ago
- Related to Bug #7635: syslog-ng's loghost regex does not match with set line added
Actions