[MXS-3448] Unable to disable maxlog Created: 2021-03-17  Updated: 2021-04-01  Resolved: 2021-03-24

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.8, 2.5.9
Fix Version/s: 2.5.10

Type: Bug Priority: Major
Reporter: Jozef Kováč Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Ubuntu 18.04.5 & RHEL 8.3


Issue Links:
Relates
relates to MXS-3479 Disabling maxlog doesn't fully preven... Closed

 Description   

I have disabled maxlog in global configuration options but logs are still written to /var/log/maxscale/maxscale.log. Even this entry is part of logs "notice : maxlog logging is disabled."

part of my conf:
[maxscale]
threads=8
syslog=1
maxlog=0
log_notice=0
load_persisted_configs=false
local_address=10.1.1.14
auth_connect_timeout=20s
users_refresh_time=10s
max_auth_errors_until_block=100
admin_gui=0
....



 Comments   
Comment by Jozef Kováč [ 2021-03-29 ]

After update to 2.5.10 still maxscale with maxlog=0 continously writing to /var/log/maxscale/maxscale.log, symlink to /dev/null works but...

Comment by markus makela [ 2021-03-29 ]

Can you check if there's a file in /var/lib/maxscale/maxscale.cnf.d/ that contains the maxlog parameter? If there is, does removing that file solve it?

Comment by Jozef Kováč [ 2021-03-29 ]

/var/lib/maxscale/maxscale.cnf.d/ is empty directory

Comment by markus makela [ 2021-03-29 ]

OK, I think I managed to reproduce it. Can you verify that you'll get a few lines of code every time MaxScale is restarted but nothing after that?

This is what I'm getting:

 
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.

I think this might be how older releases behaves so in some sense it's a separate bug. Ideally, we'd of course not log a single message before the log configuration has been read.

Comment by Jozef Kováč [ 2021-03-31 ]

yes only few lines at start or restart is written

Comment by markus makela [ 2021-04-01 ]

This seems like a different issue as the maxlog option now works as it used to work. I've opened MXS-3479 for the problem of the log being written to even if maxlog is disabled.

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