[MXS-3364] Maxscale does not startup properly due to loading the'maxscaled' protocol Created: 2021-01-05  Updated: 2021-01-05  Resolved: 2021-01-05

Status: Closed
Project: MariaDB MaxScale
Component/s: cli
Affects Version/s: 2.5.6
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Sophie Jeong Assignee: Johan Wikman
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

CentOS7 , MariaDB MaxScale 2.5.6 started



 Description   
  • Problem part of MaxScale's configuration file
    -> I can start up MaxScale without this part.

    // Some comments here
    [MaxAdmin]
    type=service
    router=cli
    enable_root_user=1
    [MaxAdmin-Unix-Listener]
    type=listener
    service=MaxAdmin
    protocol=maxscaled
    socket=default
     
    [MaxAdmin-Inet-Listener]
    type=listener
    service=MaxAdmin
    protocol=maxscaled
    address=localhost
    port=6603
    
    

  • Starting Error log

     sudo maxscale -d -U maxscale -lstdout
    info   : MaxScale will be run in the terminal process.
    2021-01-05 12:27:57   notice : (mxb_log_set_syslog_enabled): syslog logging is enabled.
    2021-01-05 12:27:57   notice : (mxb_log_set_maxlog_enabled): maxlog logging is enabled.
    2021-01-05 12:27:57   notice : (init_sqlite3): The collection of SQLite memory allocation statistics turned off.
    2021-01-05 12:27:57   notice : (init_sqlite3): Threading mode of SQLite set to Multi-thread.
    2021-01-05 12:27:57   notice : (create): Worker message queue size: 1MiB
    2021-01-05 12:27:57.572   notice : (mxb_log_set_highprecision_enabled): highprecision logging is enabled.
    2021-01-05 12:27:57.572   notice : (configure): Using up to 4.67GiB of memory for query classifier cache
    2021-01-05 12:27:57.573   notice : (main): Running OS: Linux@3.10.0-1127.19.1.el7.x86_64, #1 SMP Tue Aug 25 17:23:54 UTC 2020, x86_64 with 4 processor cores.
    2021-01-05 12:27:57.573   notice : (main): Total usable main memory: 31.13GiB.
    2021-01-05 12:27:57.573   notice : (main): MariaDB MaxScale 2.5.6 started (Commit: fddc0526ee79ac9a87f7a7170f3204263240ab57)
    2021-01-05 12:27:57.573   notice : (main): MaxScale is running in process 6105
     
    Configuration file : /etc/maxscale.cnf
    Log directory      : /var/log/maxscale
    Data directory     : /var/lib/maxscale
    Module directory   : /usr/lib64/maxscale
    Service cache      : /var/cache/maxscale
     
    2021-01-05 12:27:57.573   notice : (main): Configuration file: /etc/maxscale.cnf
    2021-01-05 12:27:57.573   notice : (main): Log directory: /var/log/maxscale
    2021-01-05 12:27:57.573   notice : (main): Data directory: /var/lib/maxscale
    2021-01-05 12:27:57.573   notice : (main): Module directory: /usr/lib64/maxscale
    2021-01-05 12:27:57.573   notice : (main): Service cache: /var/cache/maxscale
    2021-01-05 12:27:57.574   notice : (load_module): Loaded module qc_sqlite: V1.0.0 from /usr/lib64/maxscale/libqc_sqlite.so
    2021-01-05 12:27:57.574   notice : (qc_setup): Query classification results are cached and reused. Memory used per thread: 1.17GiB
    2021-01-05 12:27:57.574   notice : (load_encryption_keys): Password encryption key file '/var/lib/maxscale/.secrets' not found, using configured passwords as plaintext.
    2021-01-05 12:27:57.575   notice : (main): MaxScale started with 4 worker threads, each with a stack size of 8388608 bytes.
    2021-01-05 12:27:57.575   notice : (config_load_single_file): Loading /etc/maxscale.cnf.
    2021-01-05 12:27:57.576   notice : (is_directory): /etc/maxscale.cnf.d does not exist, not reading.
    2021-01-05 12:27:57.576   error  : (load_module): Unable to find library for module: maxscaled. Module dir: /usr/lib64/maxscale
    2021-01-05 12:27:57.576   error  : (load_module): Unable to find library for module: maxscaled. Module dir: /usr/lib64/maxscale
    2021-01-05 12:27:57.576   notice : (load_module): Loaded module MariaDBClient: V1.1.0 from /usr/lib64/maxscale/libmariadbclient.so
    2021-01-05 12:27:57.576   error  : (load_module): Unable to find library for module: cli. Module dir: /usr/lib64/maxscale
    2021-01-05 12:27:57.577   notice : (load_module): Loaded module readwritesplit: V1.1.0 from /usr/lib64/maxscale/libreadwritesplit.so
    2021-01-05 12:27:57.578   notice : (load_module): Loaded module readconnroute: V2.0.0 from /usr/lib64/maxscale/libreadconnroute.so
    2021-01-05 12:27:57.578   notice : (load_module): Loaded module mariadbmon: V1.5.0 from /usr/lib64/maxscale/libmariadbmon.so
    alert  : Failed to open, read or process the MaxScale configuration file. See the error log for details.
    2021-01-05 12:27:57.578   alert  : (operator()): Failed to open, read or process the MaxScale configuration file /etc/maxscale.cnf.
    2021-01-05 12:27:57.578   notice : (mxs_admin_shutdown): Stopped MaxScale REST API
    2021-01-05 12:27:57.778   notice : (main): MaxScale is shutting down.
    2021-01-05 12:27:57.778   notice : (main): All workers have shut down.
    2021-01-05 12:27:57.778   notice : (main): MaxScale shutdown completed.
    

Please help me if you guys can.
Thanks in advance.



 Comments   
Comment by Johan Wikman [ 2021-01-05 ]

Those sections are related to maxadmin, the administration tool that no longer is supported in 2.5, so simply remove them. maxctrl is the administration tool that should be used with 2.5.

Comment by Sophie Jeong [ 2021-01-05 ]

@johan.wikman
Thank you

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