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

Fatal: MaxScale 2.0.6 received fatal signal 11 - for DDL statement

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.0.6
    • 2.1.4
    • avrorouter
    • None

    Description

      MariaDB Corporation MaxScale /app/mariadb/maxscale/maxscale1.log Thu Jun 15 09:55:44 2017
      -----------------------------------------------------------------------
      2017-06-15 09:55:44 notice : Working directory: /app/mariadb/maxscale
      2017-06-15 09:55:44 notice : MariaDB MaxScale 2.0.6 started
      2017-06-15 09:55:44 notice : MaxScale is running in process 13548
      2017-06-15 09:55:44 notice : Configuration file: /etc/maxscale.cnf
      2017-06-15 09:55:44 notice : Log directory: /app/mariadb/maxscale
      2017-06-15 09:55:44 notice : Data directory: /app/mariadb/maxscale
      2017-06-15 09:55:44 notice : Module directory: /usr/lib64/maxscale
      2017-06-15 09:55:44 notice : Service cache: /app/mariadb/maxscale
      2017-06-15 09:55:44 warning: Number of threads set to 4 which is greater than the number of processors available: 2
      2017-06-15 09:55:44 notice : Initialise CLI router module V1.0.0.
      2017-06-15 09:55:44 notice : Loaded module cli: V1.0.0 from /usr/lib64/maxscale/libcli.so
      2017-06-15 09:55:44 notice : Initialized avrorouter module V1.0.0.
      2017-06-15 09:55:44 notice : Loaded module avrorouter: V1.0.0 from /usr/lib64/maxscale/libavrorouter.so
      2017-06-15 09:55:44 notice : Initialise binlog router module V2.0.0.
      2017-06-15 09:55:44 notice : Loaded module binlogrouter: V2.0.0 from /usr/lib64/maxscale/libbinlogrouter.so
      2017-06-15 09:55:44 notice : Initialise readconnroute router module V1.1.0.
      2017-06-15 09:55:44 notice : Loaded module readconnroute: V1.1.0 from /usr/lib64/maxscale/libreadconnroute.so
      2017-06-15 09:55:44 notice : Initializing statemend-based read/write split router module.
      2017-06-15 09:55:44 notice : Loaded module readwritesplit: V1.1.0 from /usr/lib64/maxscale/libreadwritesplit.so
      2017-06-15 09:55:44 notice : Initialise the MySQL Galera Monitor module V2.0.0.
      2017-06-15 09:55:44 notice : Loaded module galeramon: V2.0.0 from /usr/lib64/maxscale/libgaleramon.so
      2017-06-15 09:55:44 notice : Monitor 'Galera Monitor' is missing the 'monitor_interval' parameter, using default value of 10000 milliseconds.
      2017-06-15 09:55:44 notice : Initialise the MySQL Monitor module V1.4.0.
      2017-06-15 09:55:44 notice : Loaded module mysqlmon: V1.4.0 from /usr/lib64/maxscale/libmysqlmon.so
      2017-06-15 09:55:44 warning: Multiple monitors are monitoring server [dbserv1]. This will cause undefined behavior.
      2017-06-15 09:55:44 notice : No query classifier specified, using default 'qc_sqlite'.
      2017-06-15 09:55:44 notice : Loaded module qc_sqlite: V1.0.0 from /usr/lib64/maxscale/libqc_sqlite.so
      2017-06-15 09:55:44 notice : Using encrypted passwords. Encryption key: '/app/mariadb/maxscale/.secrets'.
      2017-06-15 09:55:44 notice : Loaded 12 MySQL Users for service [Read-Only Service].
      2017-06-15 09:55:44 notice : Loaded module MySQLClient: V1.1.0 from /usr/lib64/maxscale/libMySQLClient.so
      2017-06-15 09:55:44 notice : Listening connections at 0.0.0.0:4008 with protocol MySQL
      2017-06-15 09:55:44 notice : Loaded 12 MySQL Users for service [Read-Write Service].
      2017-06-15 09:55:44 notice : Listening connections at 0.0.0.0:4006 with protocol MySQL
      2017-06-15 09:55:44 notice : Loaded 12 MySQL Users for service [Galera Service].
      2017-06-15 09:55:44 notice : Listening connections at 0.0.0.0:4306 with protocol MySQL
      2017-06-15 09:55:44 notice : Listening connections at /tmp/DB.Cluster with protocol MySQL
      2017-06-15 09:55:44 notice : Loaded module maxscaled: V2.0.0 from /usr/lib64/maxscale/libmaxscaled.so
      2017-06-15 09:55:44 notice : Listening connections at /tmp/maxadmin.sock with protocol MaxScale Admin
      2017-06-15 09:55:44 notice : Validating binlog file 'mariadb-bin.000087' ...
      2017-06-15 09:55:44 notice : Loaded module MySQLBackend: V2.0.0 from /usr/lib64/maxscale/libMySQLBackend.so
      2017-06-15 09:55:44 notice : replication-service: attempting to connect to master server cdldfosdbc05s02:3406, binlog mariadb-bin.000087, pos 542429275
      2017-06-15 09:55:44 notice : Listening connections at 0.0.0.0:4000 with protocol MySQL
      2017-06-15 09:55:44 notice : [avro-service] Using configuration options from service 'replication-service'.
      2017-06-15 09:55:44 notice : [avro-service] Avro files stored at: /app/mariadb/maxscale/avro/
      2017-06-15 09:55:44 notice : [avro-service] Using existing GTID index: //app/mariadb/maxscale/avro//avro.index
      2017-06-15 09:55:44 notice : [avro-service] Loading stored conversion state: /app/mariadb/maxscale/avro//avro-conversion.ini
      2017-06-15 09:55:44 notice : Loaded stored binary log conversion state: File: [mariadb-bin.000087] Position: [86711988] GTID: [0-505-21942659:0]
      2017-06-15 09:55:44 notice : Loaded module CDC: V1.0.0 from /usr/lib64/maxscale/libCDC.so
      2017-06-15 09:55:44 notice : Listening connections at 0.0.0.0:4001 with protocol CDC
      2017-06-15 09:55:44 notice : Listening connections at /tmp/maxadmin.sock with protocol MaxScale Admin
      2017-06-15 09:55:44 notice : Started MaxScale log flusher.
      2017-06-15 09:55:44 notice : MaxScale started with 4 server threads.
      2017-06-15 09:55:44 notice : replication-service: Request binlog records from mariadb-bin.000087 at position 542429275 from master server cdldfosdbc05s02:3406
      2017-06-15 09:55:44 notice : replication-service: identity seen by the master: server_id: 5005, uuid: 53d2e352-51d2-11e7-a055-005056b05792
      2017-06-15 09:55:44 notice : replication-service: identity seen by the slaves: server_id: 505, hostname: cdldfosdbc05s02, MySQL version: 10.1.20-MariaDB-enterprise
      2017-06-15 09:55:45 notice : Server changed state: dbserv1[cdldfosdbc05s01:3406]: new_master. [Running] -> [Master, Running]
      2017-06-15 09:55:45 notice : A Master Server is now available: cdldfosdbc05s01:3406
      2017-06-15 09:55:45 notice : Server changed state: dbserv1[cdldfosdbc05s01:3406]: new_slave. [Master, Running] -> [Slave, Synced, Running]
      2017-06-15 09:55:45 notice : Server changed state: dbserv2[cdldfosdbc05s02:3406]: new_master. [Running] -> [Master, Synced, Running]
      2017-06-15 09:55:45 warning: Table map event for table 'portal.RTiESBSendQueue' read before the DDL statement for that table was read. Data will not be processed for this table until a DDL statement for it is read.
      2017-06-15 09:55:45 error : Fatal: MaxScale 2.0.6 received fatal signal 11. Attempting backtrace.
      2017-06-15 09:55:45 error : Commit ID: 673eb3d5001a184fa341ef4bb3c83b4a8019ba82 System name: Linux Release string: NAME="SLES"
      2017-06-15 09:55:45 error : /usr/bin/maxscale() [0x404080]
      2017-06-15 09:55:45 error : /lib64/libpthread.so.0(+0xf870) [0x7fad9a4a3870]
      2017-06-15 09:55:45 error : /usr/lib64/maxscale/libavrorouter.so(handle_row_event+0x2ea) [0x7fad960b5bb6]
      2017-06-15 09:55:45 error : /usr/lib64/maxscale/libavrorouter.so(avro_read_all_events+0x819) [0x7fad960b8c68]
      2017-06-15 09:55:45 error : /usr/lib64/maxscale/libavrorouter.so(converter_func+0x8c) [0x7fad960af329]
      2017-06-15 09:55:45 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x4346b) [0x7fad9adcf46b]
      2017-06-15 09:55:45 error : /lib64/libpthread.so.0(+0x80a4) [0x7fad9a49c0a4]
      2017-06-15 09:55:45 error : /lib64/libc.so.6(clone+0x6d) [0x7fad98ef602d]
      

      Attachments

        Activity

          People

            markus makela markus makela
            niljoshi Nilnandan Joshi
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.