packetfence
packetfence copied to clipboard
v12: remove useless lines from proxysql.log
Describe the bug
proxysql
is writing these lines each 5 seconds in proxysql.log
(if you have this fix 541ad8a4c3)
Sep 8 10:15:25 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:25 [INFO] Scheduler starting id: 1 , filename: /proxysql-read-only-handler.sh
Sep 8 10:15:26 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:26 [INFO] Received LOAD MYSQL QUERY RULES TO RUNTIME command
Sep 8 10:15:30 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:30 [INFO] Scheduler starting id: 1 , filename: /proxysql-read-only-handler.sh
Sep 8 10:15:31 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:31 [INFO] Received LOAD MYSQL QUERY RULES TO RUNTIME command
Sep 8 10:15:35 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:35 [INFO] Scheduler starting id: 1 , filename: /proxysql-read-only-handler.sh
Sep 8 10:15:36 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:36 [INFO] Received LOAD MYSQL QUERY RULES TO RUNTIME command
Sep 8 10:15:41 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:41 [INFO] Scheduler starting id: 1 , filename: /proxysql-read-only-handler.sh
Sep 8 10:15:41 nqb-deb3 proxysql-docker-wrapper[233217]: 2022-09-08 10:15:41 [INFO] Received LOAD MYSQL QUERY RULES TO RUNTIME command
If it's possible, I suggest we remove these lines or we switch log level of these lines to DEBUG.
That output is generated by proxysql itself and not the scheduler script. Its actually when proxysql receives a control command. Perhaps there is a way to tweak that in proxysql's config file
Some directive that may help are:
diff --git a/conf/proxysql.conf.example b/conf/proxysql.conf.example
index 2aabd302c4..eef6d6cdfd 100644
--- a/conf/proxysql.conf.example
+++ b/conf/proxysql.conf.example
@@ -70,6 +70,11 @@ mysql_variables=
monitor_galera_healthcheck_interval=2000
monitor_galera_healthcheck_timeout=800
+ eventslog_filename="mysql-events.log"
+ auditlog_filename="mysql-audit.log"
+ log_mysql_warnings_enabled=true
+ log_unhealthy_connections=true
+ verbose_query_error=true
}
[% UNLESS single_server %]