Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-164

setting log_debug=1 triggers signal 11 crash

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.3.0
    • Component/s: Core
    • Labels:
    • Environment:
      DISTRIB_ID=Ubuntu
      DISTRIB_RELEASE=14.04
      DISTRIB_CODENAME=trusty
      DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"

      Description

      Without any log_debug settings, maxscale actually seems to run fine. Once you set this flag to 1, it will not start and crash with signal 11.

      It happens, nomatter what config you use, below is a tracer of an unfinished setup but I have a semi-production setup that does exactly the same. All ubuntu 14.04

      May 20 11:55:48 ttextlb1 MaxScale[18055]: Home directory : /usr/local/mariadb-maxscale
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Data directory : /usr/local/mariadb-maxscale/data/data18055
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Log directory : /usr/local/mariadb-maxscale/log
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Configuration file : /usr/local/mariadb-maxscale/etc/MaxScale.cnf
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Initialise CLI router module V1.0.0.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded module cli: V1.0.0 from /usr/local/mariadb-maxscale/modules/libcli.so
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Initialise debug CLI router module V1.1.1.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded module debugcli: V1.1.1 from /usr/local/mariadb-maxscale/modules/libdebugcli.so
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Initializing statemend-based read/write split router module.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded module readwritesplit: V1.0.2 from /usr/local/mariadb-maxscale/modules/libreadwritesplit.so
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Error: Unable to find server 'slave2' that is configured as part of service 'RW Split Router'.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Initialise the MySQL Monitor module V1.4.0.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded module mysqlmon: V1.4.0 from /usr/local/mariadb-maxscale/modules/libmysqlmon.so
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Error: Unable to find server 'slave2' that is configured in the monitor 'MySQL Monitor'.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: MariaDB Corporation MaxScale 1.1.0 (C) MariaDB Corporation Ab 2013-2014
      May 20 11:55:48 ttextlb1 MaxScale[18055]: MaxScale is running in process 18055
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Encrypted password file /usr/local/mariadb-maxscale/etc/.secrets can't be accessed (No such file or directory). Password encryption is not used.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Error : Monitor was unable to connect to server 192.168.128.89:3306 : "Access denied for user 'lb_mon'@'ttextlb1' (using password: YES)"
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketing_archive_master
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Warning: Duplicate MySQL user found for service [RW Split Router]: brenden@% for database: ticketing_unittest_master
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded 33 MySQL Users for service [RW Split Router].
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded module MySQLClient: V1.0.0 from /usr/local/mariadb-maxscale/modules/libMySQLClient.so
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Listening MySQL connections at 0.0.0.0:4006
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded module telnetd: V1.0.1 from /usr/local/mariadb-maxscale/modules/libtelnetd.so
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Listening telnet connections at 127.0.0.1:4442
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Loaded module maxscaled: V1.0.0 from /usr/local/mariadb-maxscale/modules/libmaxscaled.so
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Listening maxscale connections at 0.0.0.0:6603
      May 20 11:55:48 ttextlb1 MaxScale[18055]: Started MaxScale log flusher.
      May 20 11:55:48 ttextlb1 MaxScale[18055]: MaxScale started with 4 server threads.
      May 20 11:56:14 ttextlb1 MaxScale[18055]: MaxScale received signal SIGTERM. Exiting.
      May 20 11:56:14 ttextlb1 MaxScale[18055]: Finished MaxScale log flusher.
      May 20 11:56:14 ttextlb1 MaxScale[18055]: MaxScale is shutting down.
      May 20 11:56:14 ttextlb1 MaxScale[18055]: MaxScale shutdown completed.
      May 20 11:56:32 ttextlb1 MaxScale[18196]: Home directory : /usr/local/mariadb-maxscale
      May 20 11:56:32 ttextlb1 MaxScale[18196]: Data directory : /usr/local/mariadb-maxscale/data/data18196
      May 20 11:56:32 ttextlb1 MaxScale[18196]: Log directory : /usr/local/mariadb-maxscale/log
      May 20 11:56:32 ttextlb1 MaxScale[18196]: Configuration file : /usr/local/mariadb-maxscale/etc/MaxScale.cnf
      May 20 11:56:32 ttextlb1 MaxScale[18196]: Fatal: MaxScale received fatal signal 11. Attempting backtrace.
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /usr/local/mariadb-maxscale/bin/maxscale() [0x5483e3]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f4b23861340]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /lib/x86_64-linux-gnu/libc.so.6(+0x97d3a) [0x7f4b224f9d3a]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /usr/local/mariadb-maxscale/bin/maxscale() [0x55caca]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /usr/local/mariadb-maxscale/bin/maxscale(ini_parse_file+0x388) [0xae0d03]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /usr/local/mariadb-maxscale/bin/maxscale(ini_parse+0x50) [0xae0dcd]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /usr/local/mariadb-maxscale/bin/maxscale(config_load+0xed) [0x55cca9]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /usr/local/mariadb-maxscale/bin/maxscale(main+0x17b3) [0x54ac79]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f4b22483ec5]
      May 20 11:56:32 ttextlb1 MaxScale[18196]: /usr/local/mariadb-maxscale/bin/maxscale() [0x54722a]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: Home directory : /usr/local/mariadb-maxscale
      May 20 11:56:46 ttextlb1 MaxScale[18212]: Data directory : /usr/local/mariadb-maxscale/data/data18212
      May 20 11:56:46 ttextlb1 MaxScale[18212]: Log directory : /usr/local/mariadb-maxscale/log
      May 20 11:56:46 ttextlb1 MaxScale[18212]: Configuration file : /usr/local/mariadb-maxscale/etc/MaxScale.cnf
      May 20 11:56:46 ttextlb1 MaxScale[18212]: Fatal: MaxScale received fatal signal 11. Attempting backtrace.
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /usr/local/mariadb-maxscale/bin/maxscale() [0x5483e3]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f73f3b3f340]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /lib/x86_64-linux-gnu/libc.so.6(+0x97d3a) [0x7f73f27d7d3a]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /usr/local/mariadb-maxscale/bin/maxscale() [0x55caca]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /usr/local/mariadb-maxscale/bin/maxscale(ini_parse_file+0x388) [0xae0d03]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /usr/local/mariadb-maxscale/bin/maxscale(ini_parse+0x50) [0xae0dcd]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /usr/local/mariadb-maxscale/bin/maxscale(config_load+0xed) [0x55cca9]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /usr/local/mariadb-maxscale/bin/maxscale(main+0x17b3) [0x54ac79]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f73f2761ec5]
      May 20 11:56:46 ttextlb1 MaxScale[18212]: /usr/local/mariadb-maxscale/bin/maxscale() [0x54722a]

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Massimiliano Pinto Massimiliano Pinto (Inactive)
              Reporter:
              gplv2 Glenn Plas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.