docker 4

bridge 1

network 2

base64 1

lua 2

kong 1

linux 4

figlet 1

asciinema 1

golang 2

kvm 1

macvtap 1

reading 3

db2 1

sql 2

ceph 1

mariadb 1

maxscale 1

shell 1

elasticsearch 1

logstash 1

numa 1

security 1

keepalived 1

logrotate 1

crontab 1

openstack 1

terminal 1

sdn 1

socat 1

openshift 2

k8s 2

jira 1

sso 1

superset 1


Rotate Maxscale log files

2017年07月07日

Overview

MaxScale write log data into four log files with varying degrees of detail. The default behavior of MaxScale is to grow the log files indefinitely, we must take action to prevent this. There are two methods to rotate log files.

Method 1

Run maxadmin command to rotate a single log file or all the log files.

$ maxadmin -pmariadb
    MaxScale> flush log error
    MaxScale> flush log trace
    MaxScale>

or

$ maxadmin -pmariadb flush logs

When the logfile is rotated, the current log file is closed and a new log file, with an increased sequence number in its name, is created.

Method 2

Follow Linux logrotate mechanism by adding a configuration file to the /etc/logrotate.d directory.

The configuration file would look like the following:

/var/log/maxscale/*.log {
	monthly
	rotate 5
	missingok
	nocompress
	sharedscripts
	postrotate
	# run if maxscale is running
	if test -n "`ps acx|grep maxscale`"; then
		/usr/bin/maxadmin -pmariadb flush logs
	fi
	endscript
}

If avoid password appear in the conf file, use the following conf:

/var/log/maxscale/*.log {
    weekly
    rotate 7
    missingok
    nocompress
    sharedscripts
    compress
    postrotate
        kill -USR1 `cat /var/run/maxscale/maxscale.pid` 
    endscript
}

For details, please refer to maxscale-rotating