[MXS-3479] Disabling maxlog doesn't fully prevent it from being written to Created: 2021-04-01  Updated: 2021-05-11  Resolved: 2021-05-07

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.9
Fix Version/s: 2.5.12

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

Issue Links:
Relates
relates to MXS-3448 Unable to disable maxlog Closed
Sprint: MXS-SPRINT-130

 Description   

When maxlog is disabled, there's always a small amount of text logged on startup. This happens because some parts of MaxScale are initialized before the variable is read from either the command line or from the configuration file.

Here's an example of what is logged on startup when maxlog is disabled.

MariaDB MaxScale  /home/markusjm/build-develop/log/maxscale/maxscale.log  Mon Mar 29 19:44:40 2021
----------------------------------------------------------------------------------------------------
2021-03-29 19:44:40   notice : The collection of SQLite memory allocation statistics turned off.
2021-03-29 19:44:40   notice : Threading mode of SQLite set to Multi-thread.
2021-03-29 19:44:40   notice : Worker message queue size: 1MiB
2021-03-29 19:44:40   notice : The logging of informational messages has been enabled.
2021-03-29 19:44:40   notice : Using up to 4.66GiB of memory for query classifier cache
2021-03-29 19:44:40   notice : syslog logging is enabled.



 Comments   
Comment by markus makela [ 2021-05-07 ]

The fix to MXS-3524 also fixes this.

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