MariaDB MaxScale /var/log/maxscale/maxscale.log Tue Mar 25 21:24:20 2025 ---------------------------------------------------------------------------- 2025-03-25 21:24:20 warning: Overwriting configuration section 'maxscale' from main file '/etc/maxscale.cnf' with contents from runtime file '/var/lib/maxscale/maxscale.cnf.d/maxscale.cnf'. To prevent this warning message, manually move the runtime changes to the main file. 2025-03-25 21:24:20 notice : Module 'mariadbmon' loaded from '/usr/lib/x86_64-linux-gnu/maxscale/libmariadbmon.so'. 2025-03-25 21:24:20 notice : Module 'readconnroute' loaded from '/usr/lib/x86_64-linux-gnu/maxscale/libreadconnroute.so'. 2025-03-25 21:24:20 notice : Module 'readwritesplit' loaded from '/usr/lib/x86_64-linux-gnu/maxscale/libreadwritesplit.so'. 2025-03-25 21:24:20 notice : Module 'binlogrouter' loaded from '/usr/lib/x86_64-linux-gnu/maxscale/libbinlogrouter.so'. 2025-03-25 21:24:20 notice : Using up to 9.38GiB of memory for query classifier cache 2025-03-25 21:24:20 notice : syslog logging is disabled. 2025-03-25 21:24:20 notice : maxlog logging is enabled. 2025-03-25 21:24:20 notice : Host: 'dbproxy2-jpn.mfg.aristanetworks.com' OS: Linux@5.4.0-208-generic, #228-Ubuntu SMP Fri Feb 7 19:41:33 UTC 2025, x86_64 with 48 processor cores (48.00 available). 2025-03-25 21:24:20 notice : Total main memory: 62.52GiB (62.52GiB usable). 2025-03-25 21:24:20 notice : MaxScale is running in process 2534 2025-03-25 21:24:20 notice : MariaDB MaxScale 23.08.7 started (Commit: 48a752fc71e0e2c2d1bd90b1d60a17d1b37c0b40) 2025-03-25 21:24:20 notice : Configuration file: /etc/maxscale.cnf 2025-03-25 21:24:20 notice : Log directory: /var/log/maxscale 2025-03-25 21:24:20 notice : Data directory: /var/lib/maxscale 2025-03-25 21:24:20 notice : Module directory: /usr/lib/x86_64-linux-gnu/maxscale 2025-03-25 21:24:20 notice : Service cache: /var/cache/maxscale 2025-03-25 21:24:20 notice : Working directory: /var/log/maxscale 2025-03-25 21:24:20 notice : Query classification results are cached and reused. Memory used per thread: 200.08MiB 2025-03-25 21:24:20 notice : Password encryption key file '/var/lib/maxscale/.secrets' not found, using configured passwords as plaintext. 2025-03-25 21:24:20 notice : The systemd watchdog is Enabled. Internal timeout = 30s 2025-03-25 21:24:20 notice : Module 'pp_sqlite' loaded from '/usr/lib/x86_64-linux-gnu/maxscale/libpp_sqlite.so'. 2025-03-25 21:24:20 notice : [MariaDBProtocol] Parser plugin loaded. 2025-03-25 21:24:20 warning: (Replication-Proxy); No (replication) primary found. Retrying silently until one is found. 2025-03-25 21:24:20 notice : Using HS256 for JWT signatures 2025-03-25 21:24:20 notice : Started REST API on [0.0.0.0]:8989 2025-03-25 21:24:20 error : Monitor was unable to connect to server db2.jpn[10.60.120.249:3306] : 'Can't connect to server on '10.60.120.249' (101)' 2025-03-25 21:24:20 error : Monitor was unable to connect to server db1.jpn[10.60.120.241:3306] : 'Can't connect to server on '10.60.120.241' (101)' 2025-03-25 21:24:20 error : Monitor was unable to connect to server db3.jpn[10.60.120.248:3306] : 'Can't connect to server on '10.60.120.248' (101)' 2025-03-25 21:24:20 notice : Server changed state: db1.jpn[10.60.120.241:3306]: master_down. [Master, Running] -> [Down] 2025-03-25 21:24:20 notice : Server changed state: db2.jpn[10.60.120.249:3306]: slave_down. [Slave, Running] -> [Down] 2025-03-25 21:24:20 notice : Server changed state: db3.jpn[10.60.120.248:3306]: slave_down. [Slave, Running] -> [Down] 2025-03-25 21:24:21 notice : Starting a total of 3 services... 2025-03-25 21:24:21 notice : (Replication-Listener); Listening for connections at [::]:3307 2025-03-25 21:24:21 notice : Service 'Replication-Proxy' started (1/3) 2025-03-25 21:24:21 notice : (Read-Write-Listener); Listening for connections at [::]:4006 2025-03-25 21:24:21 notice : Service 'Read-Write-Service' started (2/3) 2025-03-25 21:24:21 notice : (Read-Only-Listener); Listening for connections at [::]:4008 2025-03-25 21:24:21 notice : Service 'Read-Only-Service' started (3/3) 2025-03-25 21:24:21 warning: [mariadbmon] The current primary server 'db1.jpn' is no longer valid because it has been down over 2 (failcount) monitor updates and it does not have any running slaves, but there is no valid alternative to swap to. 2025-03-25 21:24:21 notice : MaxScale started with 48 worker threads. 2025-03-25 21:24:25 notice : db1.jpn sent version string '10.5.24-18-MariaDB-enterprise-log'. Detected type: MariaDB, version: 10.5.24. 2025-03-25 21:24:25 notice : db2.jpn sent version string '10.5.24-18-MariaDB-enterprise-log'. Detected type: MariaDB, version: 10.5.24. 2025-03-25 21:24:25 notice : db3.jpn sent version string '10.5.24-18-MariaDB-enterprise-log'. Detected type: MariaDB, version: 10.5.24. 2025-03-25 21:24:25 notice : Server 'db1.jpn' charset: utf8mb4_general_ci 2025-03-25 21:24:25 notice : Server 'db2.jpn' charset: utf8mb4_general_ci 2025-03-25 21:24:25 notice : Server 'db3.jpn' charset: utf8mb4_general_ci 2025-03-25 21:24:25 notice : Server changed state: db1.jpn[10.60.120.241:3306]: master_up. [Down] -> [Master, Running] 2025-03-25 21:24:25 notice : Server changed state: db2.jpn[10.60.120.249:3306]: slave_up. [Down] -> [Slave, Running] 2025-03-25 21:24:25 notice : Server changed state: db3.jpn[10.60.120.248:3306]: slave_up. [Down] -> [Slave, Running] 2025-03-25 21:24:25 notice : Read 20 user@host entries from 'db1.jpn' for service 'Read-Write-Service'. 2025-03-25 21:24:25 notice : Read 20 user@host entries from 'db1.jpn' for service 'Read-Only-Service'. 2025-03-25 21:24:25 notice : Read 20 user@host entries from 'db1.jpn' for service 'Replication-Proxy'. 2025-03-25 21:25:10 error : (Replication-Proxy); Error received during replication from '10.60.120.241:3306': Failed to fetch binlog event from master: Lost connection to server during query 2025-03-25 21:29:53 notice : Server 'db2.jpn' is going into maintenance. 2025-03-25 21:55:16 error : Monitor was unable to connect to server db2.jpn[10.60.120.249:3306] : 'Can't connect to server on '10.60.120.249' (115)' 2025-03-25 22:00:17 notice : Server 'db2.jpn' is coming out of maintenance.