ProxySQL 1.4.3 restarts with signal 6

[niravshah2705]

OS: CentOS Linux release 7.2.1511 (Core)
ProxySQL: ProxySQL version v1.4.3-1.1, codename Truls

Error Logs:
Lock wait timeout exceeded; try restarting transaction
2017-11-23 05:27:05 MySQL_Session.cpp:1764:handler_again___status_CHANGING_AUTOCOMMIT(): [WARNING] Error during SET AUTOCOMMIT: 1205, Lock wait timeout exceeded; try restarting transaction
proxysql: ../include/MySQL_Data_Stream.h:28: void MyDS_real_query::init(PtrSize_t*): Assertion `QueryPtr==__null' failed.
Error: signal 6:
/usr/local/proxysql_base/usr/bin/proxysql(_Z13crash_handleri+0x1a)[0x483bea]
/lib64/libc.so.6(+0x35670)[0x7fb720a66670]
/lib64/libc.so.6(gsignal+0x37)[0x7fb720a665f7]
/lib64/libc.so.6(abort+0x148)[0x7fb720a67ce8]
/lib64/libc.so.6(+0x2e566)[0x7fb720a5f566]
/lib64/libc.so.6(+0x2e612)[0x7fb720a5f612]
/usr/local/proxysql_base/usr/bin/proxysql(_ZN15MyDS_real_query4initEP10_PtrSize_t+0x61)[0x4bde11]
/usr/local/proxysql_base/usr/bin/proxysql(_ZN13MySQL_Session7handlerEv+0x1e48)[0x4bc4b8]
/usr/local/proxysql_base/usr/bin/proxysql(_ZN12MySQL_Thread20process_all_sessionsEv+0x1fc)[0x4a582c]
/usr/local/proxysql_base/usr/bin/proxysql(_ZN12MySQL_Thread3runEv+0xc8b)[0x4adddb]
/usr/local/proxysql_base/usr/bin/proxysql(_Z24mysql_worker_thread_funcPv+0x6c)[0x481fac]

Core dump:
#0 0x00007fb720a665f7 in raise () from /lib64/libc.so.6
#1 0x00007fb720a67ce8 in abort () from /lib64/libc.so.6
#2 0x00007fb720a5f566 in __assert_fail_base () from /lib64/libc.so.6
#3 0x00007fb720a5f612 in __assert_fail () from /lib64/libc.so.6
#4 0x00000000004bde11 in MyDS_real_query::init (this=, _pkt=) at ../include/MySQL_Data_Stream.h:28
#5 0x00000000004bc4b8 in MySQL_Session::handler (this=this@entry=0x7fb71369e780) at MySQL_Session.cpp:1999
#6 0x00000000004a582c in MySQL_Thread::process_all_sessions (this=this@entry=0x7fb71c60d000) at MySQL_Thread.cpp:2978
#7 0x00000000004adddb in MySQL_Thread::run (this=this@entry=0x7fb71c60d000) at MySQL_Thread.cpp:2769
#8 0x0000000000481fac in mysql_worker_thread_func (arg=0x7fb71ee3ae30) at main.cpp:226
#9 0x00007fb721ea8dc5 in start_thread () from /lib64/libpthread.so.0
#10 0x00007fb720b2721d in clone () from /lib64/libc.so.6

[niravshah2705]

Unable to upload coredump file here. Use below to download:
https://drive.google.com/file/d/1zfytfZFHsj4jcrTx_9S00Vqqo2P7hf_g/view?usp=sharing

[niravshah2705]

Another set of coredump
https://drive.google.com/file/d/1FgQKjKCofPjogzycfADkgDLAJSnz0NfI/view?usp=sharing

[renecannao]

@niravshah2705:
Thank you for the core dumps.
Although, I am not able to read them. See here:

Core was generated by `/usr/local/proxysql_base/usr/bin/proxysql -c /etc/proxysql.cnf -D /var/lib/prox'.
Program terminated with signal 6, Aborted.
#0  0x00007fb720a665f7 in ?? ()
(gdb) bt  
#0  0x00007fb720a665f7 in ?? ()
#1  0x00007fb720a67ce8 in ?? ()
#2  0x0000000000000020 in ?? ()
#3  0x0000000000000000 in ?? ()
(gdb) quit
[root@0a06d9f9e10d ~]# proxysql --version  
ProxySQL version v1.4.3-1.1, codename Truls
[root@0a06d9f9e10d ~]# cat /etc/centos-release                                                                                                      
CentOS Linux release 7.2.1511 (Core) 

OS version matches, same proxysql version (Percona package).
Can you confirm that OS version is the same?
Are you able to open these core dumps with gdb?
Thanks

[renecannao]

Is this standard MySQL , or Galera/PXC ?
I am trying to understand why SET AUTOCOMMIT fails with Lock wait timeout exceeded

[renecannao]

@niravshah2705 : can you please recompile 1.4.3 with this small patch (just one line) and let me know if it stop crashing?
Thanks

[niravshah2705]

This is NDB cluster in the backend being used . We will try to reproduce same in our test environment & replace patch.

[renecannao]

Hi @niravshah2705 : did it crash again after applying the patch?

[renecannao]

Hi @niravshah2705 , is this ok to close?

[niravshah2705]

We were trying to reproduce scenario in staging servers, we are not yet able to reproduce same. If we would we will apply same there. Applying patch on production is not yet approved for us.

[renecannao]

Closing due to no feedback.
Please feel free to open it again if needed.

[niravshah2705]

Sorry for late feedback. Yes it has worked Now we don't have issues. currently we are using 1.4.6 version.