[MXS-2453] Maxscale 2.3.4 getting crashed with Signal 11 Created: 2019-04-25  Updated: 2019-07-02  Resolved: 2019-07-02

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 2.3.4
Fix Version/s: 2.3.5

Type: Bug Priority: Major
Reporter: Nilnandan Joshi Assignee: markus makela
Resolution: Fixed Votes: 1
Labels: None

Sprint: MXS-SPRINT-81, MXS-SPRINT-82, MXS-SPRINT-83, MXS-SPRINT-84, MXS-SPRINT-85

 Description   

2019-04-24 10:06:13.767   warning: (18750) recieved unexpecting session track type:51 (subsequent similar messages suppressed for 10000 milliseconds)
OOM: __func__
2019-04-24 10:06:13.771   alert  : (18750) Fatal: MaxScale 2.3.4 received fatal signal 11. Attempting backtrace.
2019-04-24 10:06:13.771   alert  : (18750) Commit ID: aea64aede280558ca6b55500dfa7eb049ec9c377 System name: Linux Release string: Red Hat Enterprise Linux Server release 7.4 (Maipo)
nm: 'maxscale': No such file
addr2line: 'maxscale': No such file
2019-04-24 10:06:13.801   alert  : (18750)   maxscale(_ZN7maxbase15dump_stacktraceESt8functionIFvPKcS2_EE+0x2b) [0x40cbab]: 
2019-04-24 10:06:13.816   alert  : (18750)   maxscale(_ZN7maxbase15dump_stacktraceEPFvPKcS1_E+0x4e) [0x40cf0e]: 
2019-04-24 10:06:13.829   alert  : (18750)   maxscale() [0x4095b9]: 
2019-04-24 10:06:13.835   alert  : (18750)   /lib64/libpthread.so.0(+0xf5e0) [0x7f7daf5bb5e0]: sigaction.c:?
2019-04-24 10:06:13.842   alert  : (18750)   /lib64/libc.so.6(+0x86c31) [0x7f7dad525c31]: :?
2019-04-24 10:06:13.879   alert  : (18750)   /lib64/libc.so.6(__strdup+0xe) [0x7f7dad52593e]: :?
2019-04-24 10:06:13.923   alert  : (18750)   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(mxs_strdup+0xe) [0x7f7dafa9542e]: /home/vagrant/MaxScale/server/core/alloc.cc:112
2019-04-24 10:06:13.965   alert  : (18750)   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(gwbuf_add_property+0x28) [0x7f7dafa97cf8]: /home/vagrant/MaxScale/server/core/buffer.cc:606
2019-04-24 10:06:13.984   alert  : (18750)   /usr/lib64/maxscale/libmysqlcommon.so.2.0.0(_Z25mxs_mysql_parse_ok_packetP5gwbufmm+0x17c) [0x7f7da96e934c]: /home/vagrant/MaxScale/server/modules/protocol/MySQL/mysql_common.cc:1554
2019-04-24 10:06:14.001   alert  : (18750)   /usr/lib64/maxscale/libmysqlcommon.so.2.0.0(mxs_mysql_get_session_track_info+0xc7) [0x7f7da96e94c7]: /home/vagrant/MaxScale/server/modules/protocol/MySQL/mysql_common.cc:1600
2019-04-24 10:06:14.009   alert  : (18750)   /usr/lib64/maxscale/libmariadbbackend.so(+0x45b9) [0x7f7da8e9a5b9]: /home/vagrant/MaxScale/server/modules/protocol/MySQL/mariadbbackend/mysql_backend.cc:842
2019-04-24 10:06:14.024   alert  : (18750)   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7c957) [0x7f7dafab6957]: /home/vagrant/MaxScale/server/core/dcb.cc:3136
2019-04-24 10:06:14.041   alert  : (18750)   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7caf1) [0x7f7dafab6af1]: /home/vagrant/MaxScale/server/core/dcb.cc:3228
2019-04-24 10:06:14.086   alert  : (18750)   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1b5) [0x7f7dafb125c5]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:844
2019-04-24 10:06:14.131   alert  : (18750)   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x51) [0x7f7dafb127c1]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:545
2019-04-24 10:06:14.147   alert  : (18750)   maxscale(main+0x2019) [0x4087f9]: 
2019-04-24 10:06:14.184   alert  : (18750)   /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7dad4c0c05]: ??:?
2019-04-24 10:06:14.198   alert  : (18750)   maxscale() [0x409022]: 



 Comments   
Comment by markus makela [ 2019-05-02 ]

Possibly fixed by the change in 2.3.5 that enables the session tracking only when needed.

Comment by markus makela [ 2019-07-02 ]

Closing as Fixed in 2.3.5 as testing with MariaDB and MySQL didn't reproduce the problems.

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