[MXS-1751] Maxscale crashes when certain config is in play (with nodes down) Created: 2018-03-29  Updated: 2018-04-03  Resolved: 2018-04-03

Status: Closed
Project: MariaDB MaxScale
Component/s: Monitor, readwritesplit
Affects Version/s: 2.2.4
Fix Version/s: 2.2.5

Type: Bug Priority: Major
Reporter: Tobias Genberg Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

3x MariaDB 10.2.14
(1 offline, 1 doing full SST, last node master,synced)
Maxscale 2.2.4 with rwsplit


 Description   

Testing full sst-sync and wanted the master-node to be able to available in maxscale,
So I added the following config to maxscale:

master_accept_reads=true under service
 
available_when_donor=true under monitor

When restarting, maxscale will die with the following error:

Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21889]: Fatal: MaxScale 2.2.4 received fatal signal 11. Attempting backtrace.
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21886]: Fatal: MaxScale 2.2.4 received fatal signal 11. Attempting backtrace.
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21886]: Commit ID: 7df28f330b88cd3240eeb045fac9b5ce87a7d008 System name: Linux Release string: NAME="CentOS Linux"
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21886]: /usr/bin/maxscale[0x4079d1]
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21886]: /lib64/libpthread.so.0(+0xf5e0)[0x7f537d05d5e0]
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21886]: /usr/lib64/maxscale/libgaleramon.so(+0x30b2)[0x7f53776ae0b2]
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21886]: /lib64/libpthread.so.0(+0x7e25)[0x7f537d055e25]
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21886]: /lib64/libc.so.6(clone+0x6d)[0x7f537b03934d]
 
Mar 29 15:55:56 db1.fraggelberget.nu maxscale[21889]: Commit ID: 7df28f330b88cd3240eeb045fac9b5ce87a7d008 System name: Linux Release string: NAME="CentOS Linux
 
Mar 29 15:56:42 db2.fraggelberget.nu maxscale[21529]:   /usr/bin/maxscale() [0x4079d1]: ??:0
 
Mar 29 15:56:42 db2.fraggelberget.nu maxscale[21529]:   /lib64/libpthread.so.0(+0xf5e0) [0x7f52b09675e0]: sigaction.c:?
 
Mar 29 15:56:42 db2.fraggelberget.nu maxscale[21529]:   /usr/lib64/maxscale/libgaleramon.so(+0x30b2) [0x7f52aafb80b2]: /home/ec2-user/MaxScale/server/modules/monitor/galeramon/galeramon.c:395
 
Mar 29 15:56:42 db2.fraggelberget.nu maxscale[21529]:   /lib64/libpthread.so.0(+0x7e25) [0x7f52b095fe25]: pthread_create.c:?
 
Mar 29 15:56:42 db2.fraggelberget.nu maxscale[21529]:   /lib64/libc.so.6(clone+0x6d) [0x7f52ae94334d]: ??:?
 
Mar 29 15:56:42 db2.fraggelberget.nu systemd[1]: maxscale.service: main process exited, code=killed, status=11/SEGV



 Comments   
Comment by Tobias Genberg [ 2018-03-29 ]

Removing available_when_donor=true will stop the crash.

Comment by markus makela [ 2018-03-31 ]

Commit 6c2f06460af5712fa1457d81c0a1cfb5cff96259 appears to fix it.

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