[MXS-780] Crash /modules/protocol/mysql_backend.c:622 Created: 2016-06-23  Updated: 2016-08-09  Resolved: 2016-08-09

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.4.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Kenny Assignee: Johan Wikman
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

maxscale 64 bit debian wheezy


 Description   

MaxScale crashes under load with:

2016-06-17 01:57:05 error : Fatal: MaxScale 1.4.3 received fatal signal 11. Attempting backtrace.
2016-06-17 01:57:05 error : Commit ID: c2706bab69d1f3b5f1f3ec70f78b1a4803788fec System name: Linux Release string: undefined Embedded library version: (null)
2016-06-17 01:57:05 error : /usr/bin/maxscale() [0x40406c]
2016-06-17 01:57:05 error : /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0) [0x7f24f8dd40a0]
2016-06-17 01:57:05 error : /usr/lib/x86_64-linux-gnu/maxscale/libMySQLBackend.so(+0x36d4) [0x7f24de8e76d4]
2016-06-17 01:57:05 error : /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(+0x4645f) [0x7f24f96f145f]
2016-06-17 01:57:05 error : /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(poll_waitevents+0x5df) [0x7f24f96f0f69]
2016-06-17 01:57:05 error : /usr/bin/maxscale(worker_thread_main+0x2a) [0x405067]
2016-06-17 01:57:05 error : /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f24f8dcbb50]
2016-06-17 01:57:05 error : /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f24f793a30d]

using https://github.com/mariadb-corporation/MaxScale/wiki/Debugging), I get:

  1. addr2line -e /usr/lib/x86_64-linux-gnu/maxscale/libMySQLBackend.so 0x36d4
    /home/vagrant/workspace/server/modules/protocol/mysql_backend.c:622

 Comments   
Comment by Johan Wikman [ 2016-06-28 ]

Thank you for reporting this.
Can you provide more information regarding what was being done when this happened?
Do you have a core file and would you be able to share it?

Comment by Kenny [ 2016-06-30 ]

Unfortunately, it is not known on what specifically caused this. MaxScale was in production at the time.

However, because of the crash, MaxScale was taken out of production.

Because we don't know what caused it, we can't reproduce and cannot create a corefile.
The only way to try to get a corefile for you is to put MaxScale back in production and have it crash again (creating a corefile).

However, my customer might not be up for doing this as this impacts their production environment heavily.

Comment by Johan Wikman [ 2016-06-30 ]

Thanks. We havn't seen anything similar, but will try to reproduce it and will also by code inspection try to find a possible cause.
In case we find something we'll update this item.

Comment by Johan Wikman [ 2016-06-30 ]

gryp would you have the maxscale log?

Comment by Johan Wikman [ 2016-08-09 ]

Without additional information it is hard to address.

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