[MXS-418] crash - sig 11 Created: 2015-10-20  Updated: 2015-12-01  Resolved: 2015-12-01

Status: Closed
Project: MariaDB MaxScale
Component/s: Core, readwritesplit
Affects Version/s: 1.2.1
Fix Version/s: 1.3.0

Type: Bug Priority: Critical
Reporter: Rick James (Inactive) Assignee: markus makela
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

Ubuntu 14.04 LTS


 Description   

Here is this morning’s fatal error from maxscale, version 1.2.11

Another note is this is the Honk Kong server to China, so connectivity is always poor, maxscale is not dealing with it very nice.

2015-10-20 12:07:40 Error : Monitor was unable to connect to server mysql1a.bj.aofk.net:3306 : "Lost connection to MySQL server at 'reading authorization packet', system error: 11"
2015-10-20 12:07:40 Error : server mysql1a.bj.aofk.net:3306 lost the master status. Readwritesplit service can't locate the master. Client sessions will be closed.
2015-10-20 12:07:40 Error : No Master can be determined. Last known was mysql1a.bj.aofk.net:3306
2015-10-20 12:48:34 splitter service: login attempt for user 'root', authentication failed.
2015-10-20 13:18:38 splitter service: login attempt for user 'root', authentication failed.
2015-10-20 13:18:42 splitter service: login attempt for user 'root', authentication failed.
2015-10-20 13:18:46 Error : Loading database names for service splitter service encountered error: Lost connection to MySQL server during query.
2015-10-20 13:18:46 Fatal: MaxScale 1.2.1 received fatal signal 11. Attempting backtrace.
2015-10-20 13:18:46 Commit ID: 7bfda81b098bfd0db3c306495725d1910294d2e8 System name: Linux Release string: Ubuntu 14.04.3 LTS Embedded library version: 5.5.42-MariaDB
2015-10-20 13:18:46 /usr/bin/maxscale() [0x549855]
2015-10-20 13:18:46 /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f309ea3f340]
2015-10-20 13:18:46 /usr/bin/maxscale(hashtable_fetch+0x60) [0x567958]
2015-10-20 13:18:46 /usr/lib/x86_64-linux-gnu/maxscale/libMySQLClient.so(check_db_name_after_auth+0x68) [0x7f309486d8dd]
2015-10-20 13:18:46 /usr/lib/x86_64-linux-gnu/maxscale/libMySQLClient.so(+0x5744) [0x7f3094867744]
2015-10-20 13:18:46 /usr/lib/x86_64-linux-gnu/maxscale/libMySQLClient.so(+0x5e0c) [0x7f3094867e0c]
2015-10-20 13:18:46 /usr/bin/maxscale() [0x55fcca]
2015-10-20 13:18:46 /usr/bin/maxscale(poll_waitevents+0x6d4) [0x55f57b]
2015-10-20 13:18:46 /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7f309ea37182]
2015-10-20 13:18:46 /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f309d73a47d]
root@maxscale:~# ls

 Comments   
Comment by markus makela [ 2015-10-20 ]

File names and line numbers:

/home/vagrant/workspace/server/core/gateway.c:362
 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f309ea3f340]
 
/home/vagrant/workspace/server/core/hashtable.c:376
 
/home/vagrant/workspace/server/modules/protocol/mysql_common.c:2180
 
/home/vagrant/workspace/server/modules/protocol/mysql_client.c:603
 
/home/vagrant/workspace/server/modules/protocol/mysql_client.c:883
 
/home/vagrant/workspace/server/core/poll.c:878
 
/home/vagrant/workspace/server/core/poll.c:610
 
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7f309ea37182]
 
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f309d73a47d]

Comment by markus makela [ 2015-10-20 ]

To be able to further diagnose this, we need to know which modules were used. If possible, please provide the maxscale.cnf file.

Comment by Johan Wikman [ 2015-12-01 ]

Without more information it is hard to try reproducing it. However, it looks like many of the other 1.2.1 crashes that MXS-329 included in 1.3.0 is expected to fix. Consequently, I'll close this. If something similar occurs with the forthcoming 1.3.0 please create a new bug report.

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