[MXS-1465] MaxScale crashes while loading database names for readconnroute service Created: 2017-10-09  Updated: 2020-08-25  Resolved: 2018-06-12

Status: Closed
Project: MariaDB MaxScale
Component/s: readconnroute
Affects Version/s: 2.0.5
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Valerii Kravchuk Assignee: Johan Wikman
Resolution: Cannot Reproduce Votes: 0
Labels: need_feedback


 Description   

MaxScale 2.0.5 crashes like this:

2017-10-08 01:32:25 error : Loading database names for service Write Service encountered error when querying database privileges: Lost connection to MySQL server during query.
2017-10-08 01:32:25 error : Fatal: MaxScale 2.0.5 received fatal signal 11. Attempting backtrace.
2017-10-08 01:32:25 error : Commit ID: 60c69d0f7f461a1773a4e848e87fa3fcc7b0e421 System name: Linux Release string: Red Hat Enterprise Linux Server release 6.9 (Santiago)
2017-10-08 01:32:25 error : /usr/bin/maxscale() [0x403b9c]
2017-10-08 01:32:25 error : /lib64/libpthread.so.0() [0x394360f7e0]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(hashtable_fetch+0x88) [0x3946a3fae2]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libMySQLAuth.so.1.0.0(check_db_name_after_auth+0x68) [0x7fbd3ccf2f27]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libMySQLAuth.so.1.0.0(+0x1fe0) [0x7fbd3ccf2fe0]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libMySQLAuth.so.1.0.0(+0x1261) [0x7fbd3ccf2261]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libMySQLClient.so(+0x254a) [0x7fbd3cef654a]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libMySQLClient.so(+0x248c) [0x7fbd3cef648c]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0() [0x3946a4ceff]
2017-10-08 01:32:25 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(poll_waitevents+0x5fc) [0x3946a4c7a4]
2017-10-08 01:32:25 error : /usr/bin/maxscale(worker_thread_main+0x2a) [0x404a5f]
2017-10-08 01:32:25 error : /lib64/libpthread.so.0() [0x3943607aa1]
2017-10-08 01:32:25 error : /lib64/libc.so.6(clone+0x6d) [0x39432e8bcd]

It crashes way too often with this same backtrace.

Simplified configuration file content is:

[maxscale]
threads=auto
maxlog=1
logdir=/opt/hd/db/var/
datadir=/opt/hd/db/datadir1
cachedir=/opt/hd/db/tmp/maxscale_cache
 
[e47]
type=server
address=XXX.XX.XXX.25
port=3306
protocol=MySQLBackend
 
[e48]
type=server
address=XXX.XX.XXX.26
port=3306
protocol=MySQLBackend
 
[e49]
type=server
address=XXX.XX.XXX.27
port=3306
protocol=MySQLBackend
 
[MySQL Monitor]
type=monitor
module=mysqlmon
servers=e47,e48,e49
user=maxscale
passwd=YYY
#monitor_interval=10000
monitor_interval=1000
backend_connect_timeout=9
detect_stale_master=true
 
[Write Service]
type=service
router=readconnroute
router_options=master
servers=e47,e48,e49
user=maxscale
passwd=YYY
enable_root_user=true
 
[Read Service]
type=service
router=readconnroute
servers=e47,e48,e49
user=maxscale
passwd=YYY
enable_root_user=true
 
[MaxAdmin Service]
type=service
router=cli
 
[MaxInfo Service]
type=service
router=maxinfo
user=maxscale
passwd=YYY
 
[MaxInfo Listener]
type=listener
service=MaxInfo Service
protocol=MySQLClient
port=9003
 
[Write Listener]
type=listener
service=Write Service
protocol=MySQLClient
port=3306
 
[Read Listener]
type=listener
service=Read Service
protocol=MySQLClient
port=4307
 
[MaxAdmin Unix Listener]
type=listener
service=MaxAdmin Service
protocol=maxscaled
socket=default
 
[MaxAdmin TCP Listener]
address=0.0.0.0
type=listener
service=MaxAdmin Service
protocol=maxscaled
port=6603



 Comments   
Comment by Johan Wikman [ 2018-03-23 ]

Donwgraded to minor as it never happened again.

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