FS#63877 - [syslog-ng] 3.22 and newer needs config update
Attached to Project:
Arch Linux
Opened by Anton (Xakep_SDK) - Saturday, 21 September 2019, 16:17 GMT
Last edited by Florian Pritz (bluewind) - Friday, 27 September 2019, 21:05 GMT
Opened by Anton (Xakep_SDK) - Saturday, 21 September 2019, 16:17 GMT
Last edited by Florian Pritz (bluewind) - Friday, 27 September 2019, 21:05 GMT
|
Details
Description:
Arch provides syslog-ng 3.23.1 with config for 3.17. Syslog-ng 3.22 and newer changes some behavior and new version requires config modification. I'm not sure how to make proper fix, but changing @version: 3.17 to @version: 3.22 fixes issue for me. Additional info: https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.22/release-notes Steps to reproduce: 1. Install syslog-ng 2. Try to start 3. Check logs for error Log: Sep 21 14:33:08 localhost syslog-ng[493]: syslog-ng starting up; version='3.23.1' Sep 21 14:33:08 localhost syslog-ng[493]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().; |
This task depends upon
Comment by
Florian Pritz (bluewind) - Saturday,
21 September 2019, 21:59 GMT
Fixed in [testing] with syslog-ng 3.23.1-2.