Actions
User story #3021
closed
Add explanation on how to workaround the use of specific port with syslogd by iptables rules
Added by Nicolas PERRON about 12 years ago. Updated over 9 years ago.
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
Since #2943, the use of Rudder Server on an Ubuntu Server requires to use a specific port with syslog. Nevertheless, we can't configure syslogd to use another port than 514. Then any Rudder node with syslogd will not be able to send reports to its server.
We have to inform of the workarounds in the documentation of Rudder 2.4.
Updated by Nicolas PERRON almost 12 years ago
- Target version changed from 2.4.0~rc2 to 2.4.0
Updated by Nicolas PERRON almost 12 years ago
- Target version changed from 2.4.0 to 61
Updated by François ARMAND almost 12 years ago
- Target version changed from 61 to 2.4.2
Updated by Nicolas PERRON almost 12 years ago
- Target version changed from 2.4.2 to 2.4.3
Updated by François ARMAND almost 12 years ago
- Tracker changed from Bug to User story
- Project changed from Rudder to 30
- Category deleted (
Documentation) - Status changed from New to 8
- Priority changed from 1 (highest) to 2
Moved to Rudder Doc.
Updated by Matthieu CERDA almost 12 years ago
- Target version changed from 2.4.3 to 2.4.4
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.4 to 2.4.5
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.5 to 2.4.6
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.6 to 2.4.7
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.7 to 2.4.8
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.8 to 2.4.9
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.9 to 2.4.10
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.10 to 2.4.11
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.11 to 2.4.12
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.12 to 2.4.13
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.4.13 to 2.6.11
Since Support for 2.4 branch is over, retargeting this issue to 2.6
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.6.11 to 2.6.12
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.6.12 to 2.6.13
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.6.13 to 2.6.14
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.6.14 to 2.6.16
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.6.16 to 2.6.17
Updated by Nicolas PERRON over 10 years ago
- Target version changed from 2.6.17 to 2.6.18
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 2.6.18 to 2.6.19
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.6.19 to 2.6.20
Updated by François ARMAND almost 10 years ago
- Status changed from 8 to Rejected
It is done in Rudder 2.10 documentation and up (see for example: http://www.rudder-project.org/rudder-doc-2.10/rudder-doc.html#_compatibility_with_rhel_centos_5_and_syslogd
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 30 to Rudder
- Category set to Documentation
Actions