[MXS-623] Error starting MaxScale beta-1.4.0 in Ubuntu 14.04.3 LTS Created: 2016-03-15  Updated: 2016-03-16  Resolved: 2016-03-16

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.4.0
Fix Version/s: 1.4.0

Type: Bug Priority: Major
Reporter: Wepngong Ngeh Benaiah Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Ubuntu 14.04.3 LTS



 Description   

Im using Ubuntu 14.04.3 LTS and this is my log file

MariaDB Corporation MaxScale	/var/log/maxscale/maxscale1.log Tue Mar 15 14:21:21 2016
-----------------------------------------------------------------------
2016-03-15 14:21:21   notice : Configuration file: /etc/maxscale.cnf
2016-03-15 14:21:21   notice : Log directory: /var/log/maxscale
2016-03-15 14:21:21   notice : Data directory: /var/lib/maxscale
2016-03-15 14:21:21   notice : Module directory: /usr/lib/x86_64-linux-gnu/maxscale
2016-03-15 14:21:21   notice : Service cache: /var/cache/maxscale
2016-03-15 14:21:21   notice : Initialise CLI router module V1.0.0.
2016-03-15 14:21:21   notice : Loaded module cli: V1.0.0 from /usr/lib/x86_64-linux-gnu/maxscale/libcli.so
2016-03-15 14:21:21   notice : Initializing statemend-based read/write split router module.
2016-03-15 14:21:21   notice : Loaded module readwritesplit: V1.0.2 from /usr/lib/x86_64-linux-gnu/maxscale/libreadwritesplit.so
2016-03-15 14:21:21   notice : Initialise readconnroute router module V1.1.0.
2016-03-15 14:21:21   notice : Loaded module readconnroute: V1.1.0 from /usr/lib/x86_64-linux-gnu/maxscale/libreadconnroute.so
2016-03-15 14:21:21   notice : Initialise the MySQL Monitor module V1.4.0.
2016-03-15 14:21:21   notice : Loaded module mysqlmon: V1.4.0 from /usr/lib/x86_64-linux-gnu/maxscale/libmysqlmon.so
2016-03-15 14:21:21   error  : Unable to find server '127.0.0.1' that is configured in the monitor 'MySQL Monitor'.
2016-03-15 14:21:21   notice : Encrypted password file /var/lib/maxscale/.secrets can't be accessed (No such file or directory). Password encryption is not used.
2016-03-15 14:21:21   error  : Fatal: MaxScale beta-1.4.0 received fatal signal 11. Attempting backtrace.
2016-03-15 14:21:21   error  : Commit ID: 1a2bd8b234cd77660115f0ae3297eea9ea7d4ae7 System name: Linux Release string: Ubuntu 14.04.3 LTS Embedded library version: 5.5.5-10.0.22-MariaDB
2016-03-15 14:21:21   error  :   /usr/bin/maxscale() [0x52fefb] 
2016-03-15 14:21:21   error  :   /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7fa9edbb1340] 
2016-03-15 14:21:21   error  :   /usr/bin/maxscale(check_monitor_permissions+0x9a) [0x5574a5] 
2016-03-15 14:21:21   error  :   /usr/bin/maxscale() [0x54c412] 
2016-03-15 14:21:21   error  :   /usr/bin/maxscale(config_load+0x3d0) [0x54a094] 
2016-03-15 14:21:21   error  :   /usr/bin/maxscale(main+0x1d20) [0x532bf2] 
2016-03-15 14:21:21   error  :   /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fa9ec7d2ec5] 
2016-03-15 14:21:21   error  :   /usr/bin/maxscale() [0x52e859] 

Why does the server crash?



 Comments   
Comment by markus makela [ 2016-03-16 ]

The monitor permission checks assumed that a monitor always has at least one valid server.

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