Bug #3914
closed
The rsyslog configuration deployed at install is invalid
Added by Nicolas CHARLES about 11 years ago.
Updated over 9 years ago.
Description
When we install the rudder server, the rsyslog script deployed is invalid; as it contains $InputTCPServerRun &SYSLOGPORT&
When the agent runs, it solves the issue, but it make a time window when nodes cannot connect
Indeed, in rudder-reports/SPECS/rudder-reports.spec, we copy the techniques version of this file, rather than the initial promises version, hence the unexpanded stringtemplate variable
- Project changed from Rudder to 34
- Category deleted (
39)
- Status changed from New to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/120
- Status changed from Pending technical review to Discussion
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
- Status changed from Discussion to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- Status changed from Pending technical review to Discussion
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
The Pull Request needs some adaptations - see inline comments.
- Status changed from Discussion to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
Jonathan CLARKE wrote:
The Pull Request needs some adaptations - see inline comments.
Done !
- Status changed from Pending technical review to Pending release
Applied in changeset commit:dcecc84f00a5846b5aacc48f9866b1e51c329e1b.
Applied in changeset commit:59472680c3521f9f56e12f8645adbb66a965b8e6.
This bug has been fixed in Rudder 2.4.9, which was released today.
Check out:
- Status changed from Pending release to Released
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by Jonathan CLARKE 
Updated by