[MXS-2104] Aurora Monitor maxscale crash Created: 2018-10-18  Updated: 2018-10-19  Resolved: 2018-10-19

Status: Closed
Project: MariaDB MaxScale
Component/s: Monitor
Affects Version/s: 2.2.15
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Eric Crepeau Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Ubuntu 18.04.1

Issue Links:
Duplicate
duplicates MXS-1851 Using backend protocol as client prot... Closed

 Description   

MariaDB MaxScale /var/log/maxscale/maxscale.log Thu Oct 18 16:35:27 2018
----------------------------------------------------------------------------
2018-10-18 16:35:27 notice : Working directory: /var/log/maxscale
2018-10-18 16:35:27 notice : The collection of SQLite memory allocation statistics turned off.
2018-10-18 16:35:27 notice : Threading mode of SQLite set to Multi-thread.
2018-10-18 16:35:27 notice : MariaDB MaxScale 2.2.15 started (Commit: 62ce6c15dcd45be035ff6a005ca5539ca3d2adc8)
2018-10-18 16:35:27 notice : MaxScale is running in process 1177
2018-10-18 16:35:27 notice : Configuration file: /etc/maxscale.cnf
2018-10-18 16:35:27 notice : Log directory: /var/log/maxscale
2018-10-18 16:35:27 notice : Data directory: /var/lib/maxscale
2018-10-18 16:35:27 notice : Module directory: /usr/lib/x86_64-linux-gnu/maxscale
2018-10-18 16:35:27 notice : Service cache: /var/cache/maxscale
2018-10-18 16:35:27 notice : Loading /etc/maxscale.cnf.
2018-10-18 16:35:27 notice : /etc/maxscale.cnf.d does not exist, not reading.
2018-10-18 16:35:27 notice : [cli] Initialise CLI router module
2018-10-18 16:35:27 notice : Loaded module cli: V1.0.0 from /usr/lib/x86_64-linux-gnu/maxscale/libcli.so
2018-10-18 16:35:27 notice : [readwritesplit] Initializing statement-based read/write split router module.
2018-10-18 16:35:27 notice : Loaded module readwritesplit: V1.1.0 from /usr/lib/x86_64-linux-gnu/maxscale/libreadwritesplit.so
2018-10-18 16:35:27 notice : Loaded module auroramon: V1.0.0 from /usr/lib/x86_64-linux-gnu/maxscale/libauroramon.so
2018-10-18 16:35:27 notice : Loaded module MariaDBBackend: V2.0.0 from /usr/lib/x86_64-linux-gnu/maxscale/libmariadbbackend.so
2018-10-18 16:35:27 notice : Loaded module MySQLBackendAuth: V1.0.0 from /usr/lib/x86_64-linux-gnu/maxscale/libmysqlbackendauth.so
2018-10-18 16:35:27 notice : Loaded module maxscaled: V2.0.0 from /usr/lib/x86_64-linux-gnu/maxscale/libmaxscaled.so
2018-10-18 16:35:27 notice : Loaded module MaxAdminAuth: V2.1.0 from /usr/lib/x86_64-linux-gnu/maxscale/libmaxadminauth.so
2018-10-18 16:35:27 notice : Monitor 'Aurora-Monitor' is missing the 'journal_max_age' parameter, using default value of 28800 seconds.
2018-10-18 16:35:27 notice : Monitor 'Aurora-Monitor' is missing the 'script_timeout' parameter, using default value of 90 seconds.
2018-10-18 16:35:27 notice : No query classifier specified, using default 'qc_sqlite'.
2018-10-18 16:35:27 notice : Loaded module qc_sqlite: V1.0.0 from /usr/lib/x86_64-linux-gnu/maxscale/libqc_sqlite.so
2018-10-18 16:35:27 notice : Using encrypted passwords. Encryption key: '/var/lib/maxscale/.secrets'.
2018-10-18 16:35:27 notice : Starting a total of 2 services...
2018-10-18 16:35:27 alert : Fatal: MaxScale 2.2.15 received fatal signal 11. Attempting backtrace.
2018-10-18 16:35:27 alert : Commit ID: 62ce6c15dcd45be035ff6a005ca5539ca3d2adc8 System name: Linux Release string: Ubuntu 18.04.1 LTS
2018-10-18 16:35:27 notice : Loaded server states from journal file: /var/lib/maxscale/Aurora-Monitor/monitor.dat
2018-10-18 16:35:27 alert : /usr/bin/maxscale() [0x40838d]: ??:0
2018-10-18 16:35:27 alert : /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f34cc75e890]: ??:?

MariaDB MaxScale /var/log/maxscale/maxscale.log Thu Oct 18 16:35:27 2018
----------------------------------------------------------------------------
2018-10-18 16:35:27 error : No data read from child process pipe.
2018-10-18 16:35:27 MariaDB MaxScale is shut down.
----------------------------------------------------

 Comments   
Comment by Eric Crepeau [ 2018-10-18 ]

Found issue and resolved. Ticket can be closed.

Comment by markus makela [ 2018-10-19 ]

MaxScale should not crash at any point. Could you explain what the problem was in case it is an actual problem?

Comment by Eric Crepeau [ 2018-10-19 ]

Incorrectly configured the listener as protocol=MariaDBBackend instead of protocol=MariaDBClient which was causing the crash. Nothing in the log showing the misconfigured entry. Server was just crashing out.

Comment by markus makela [ 2018-10-19 ]

OK then this would be a duplicate of MXS-1851.

Comment by Eric Crepeau [ 2018-10-19 ]

Only difference is this installation was done using script install and apt-get install maxscale.

I have not looked to see which package this fetches.

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