[MXS-3509] Syslog output is not filtered according to current log configuration Created: 2021-04-22  Updated: 2022-11-27  Resolved: 2021-04-23

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.4.19, 2.5.10
Fix Version/s: 2.4.20, 2.5.11

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

Syslog messages are not filtered according to the current log configuration. As a result, all messages are logged into syslog which results in poor performance. To prevent this from happening, add syslog=false to the configuration

This happened because of a bug where session_trace was always enabled and the code that checked whether a message should be logged always thought the message should be processed.



 Comments   
Comment by markus makela [ 2022-03-31 ]

Turns out this is a problem in 2.4 as well.

Generated at Thu Feb 08 04:21:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.