User story #5796
closed
User story #5622: Let the user choose between udp and tcp for syslog messages
Make syslog transport configurable from web interface
Added by Florian Heigl about 10 years ago.
Updated over 9 years ago.
Category:
Web - Maintenance
Description
Currently the transport method of TCP is hardcoded in the system techniques.
Would you please make this configurable?
There is a horror scenario
DB issue locks DB.
Syslog cannot write to DB
Syslog on all Agents cannot write reports to Syslog Server
Syslog calls on all Agents block
All applications block if they properly use syslog to commit their logfiles
So I'm switching to UDP, but it seems I have to run my branch of the system techniques for this as of now.
Similar to #5797, this needs to be configurable in Techniques, then made available in the web interface.
- Subject changed from Make syslog transport configurable to Make syslog transport configurable from web interface
- Category changed from System techniques to Web - Maintenance
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Priority changed from N/A to 1 (highest)
- Target version set to 3.1.0~rc1
- Parent task set to #5622
This is a duplicate of #5622, however I will keep that user story to add The web interface to manage the system variable "SEND_UDP_REPORTS"
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/871
- Status changed from Pending technical review to Pending release
- % Done changed from 50 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.0~rc1 which was released on the 16th June 2015.
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by