[MXS-964] Fatal: MaxScale 2.0.1 received fatal signal 6 Created: 2016-11-07  Updated: 2016-11-30  Resolved: 2016-11-30

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 2.0.1
Fix Version/s: 2.0.3

Type: Bug Priority: Major
Reporter: NoX Assignee: markus makela
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Debian GNU/Linux 8 (jessie)

Attachments: Text File maxscale1.log    
Issue Links:
Duplicate
duplicates MXS-956 Maxscale crash: Removing DCB 0x7fbf94... Closed
Sprint: 2016-23

 Description   

Full log in attachments

2016-11-07 18:42:54   error  : 140126193710848 [dcb_close] Error : Removing DCB 0x7f71a00134d0 but was in state DCB_STATE_DISCONNECTED which is not legal for a call to dcb_close. 
2016-11-07 18:42:54   error  : Fatal: MaxScale 2.0.1 received fatal signal 6. Attempting backtrace.
 
2016-11-07 18:42:54   error  : Commit ID: fa2a66719554d13a00db5c81c5c9ffd5b3a2ce14 System name: Linux Release string: undefined
 
2016-11-07 18:42:54   error  :   maxscale() [0x403bdf] 
2016-11-07 18:42:54   error  :   /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7f71bfb798d0] 
2016-11-07 18:42:54   error  :   /lib/x86_64-linux-gnu/libpthread.so.0(raise+0x2b) [0x7f71bfb7979b] 
2016-11-07 18:42:54   error  :   /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(dcb_close+0x108) [0x7f71c049bcba] 
2016-11-07 18:42:54   error  :   /usr/lib/x86_64-linux-gnu/maxscale/libreadwritesplit.so(+0x32b2) [0x7f71ba4f62b2] 
2016-11-07 18:42:54   error  :   /usr/lib/x86_64-linux-gnu/maxscale/libMySQLClient.so(+0x35ba) [0x7f71b94155ba] 
2016-11-07 18:42:54   error  :   /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(+0x31ad8) [0x7f71c0499ad8] 
2016-11-07 18:42:54   error  :   /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(+0x317c5) [0x7f71c04997c5] 
2016-11-07 18:42:54   error  :   /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(dcb_process_zombies+0x224) [0x7f71c049961a] 
2016-11-07 18:42:54   error  :   /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(poll_waitevents+0x66d) [0x7f71c04af177] 
2016-11-07 18:42:54   error  :   maxscale(worker_thread_main+0x2a) [0x404a82] 
2016-11-07 18:42:54   error  :   /lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4) [0x7f71bfb720a4] 
2016-11-07 18:42:54   error  :   /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f71be5d962d]



 Comments   
Comment by markus makela [ 2016-11-08 ]

This seems to be a duplicate of MXS-956. Just to be sure, please attach the part from configuration where the readwritesplit service is defined.

The current working theory is that this might be caused by master_failure_mode=error_on_write and removing it prevents the crash.

Comment by NoX [ 2016-11-08 ]

We are not redefining option router_options in cfg. So if master_failure_mode=error_on_write is default option, then its might be duplicate of MXS-956

[maxscale]
 
threads=4
 
 
 
[Splitter Service]
 
type=service
 
router=readwritesplit
 
servers=dbserv1, dbserv2
 
user=root
 
passwd=*******
 
enable_root_user=1
 
 
 
[Splitter Listener]
 
type=listener
 
service=Splitter Service
 
protocol=MySQLClient
 
port=3306
 
socket=/var/run/mysqld/mysqld.sock
 
 
 
[dbserv1]
 
type=server
 
address=db
 
port=3306
 
protocol=MySQLBackend
 
 
 
[dbserv2]
 
type=server
 
address=db1
 
port=3306
 
protocol=MySQLBackend
 
 
 
 
 
[Replication Monitor]
 
type=monitor
 
module=mysqlmon
 
servers=dbserv1, dbserv2
 
user=root
 
passwd=*******
 
 
 
[CLI]
 
type=service
 
router=cli
 
 
 
[CLI Listener]
 
type=listener
 
service=CLI
 
protocol=maxscaled
 
address=localhost
 
port=6603
 
 
 
[MaxAdmin Service]
 
type=service
 
router=cli
 
 
 
[MaxAdmin Listener]
 
type=listener
 
service=MaxAdmin Service
 
protocol=maxscaled
 
socket=default

Comment by markus makela [ 2016-11-16 ]

NoX please try adding router_options=disable_sescmd_history=true to the Splitter Service Our investigations for MXS-956 have found this to be an option which prevents the crash.

If adding the option prevents the crash, I am quite sure that this is a duplicate of MXS-956.

Comment by markus makela [ 2016-11-30 ]

This duplicates MXS-956.

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