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

MaxScale crashes on startup.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.3.5
    • Fix Version/s: N/A
    • Component/s: N/A
    • Labels:
      None
    • Environment:
      RHEL

      Description

      MaxScale 2.3.5 crashes once connections are moved to it.

      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Starting a total of 4 services...
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Listening for connections at [::]:3307 with protocol MySQL
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Service 'pam-service' started (1/4)
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Listening for connections at [/var/run/maxscale/maxadmin.sock]:0 with protocol MaxScale Admin
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Service 'MaxAdmin-Service' started (2/4)
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: [Splitter-Pers-Service] Loaded 58 MySQL users for listener Splitter-Pers-Listener.
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Listening for connections at [::]:3309 with protocol MySQL
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Service 'Splitter-Pers-Service' started (3/4)
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: [Splitter-Service] Loaded 58 MySQL users for listener Splitter-Listener.
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Listening for connections at [::]:3306 with protocol MySQL
      Apr 22 14:48:26 prvlopsmsc01 maxscale[18373]: Service 'Splitter-Service' started (4/4)
      Apr 22 14:48:27 prvlopsmsc01 maxscale[18373]: Started REST API on [127.0.0.1]:8989
      Apr 22 14:48:27 prvlopsmsc01 maxscale[18373]: MaxScale started with 2 worker threads, each with a stack size of 8388608 bytes.
      Apr 22 14:48:27 prvlopsmsc01 systemd: Started MariaDB MaxScale Database Proxy.
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) Fatal: MaxScale 2.3.5 received fatal signal 11. Attempting backtrace.
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) Commit ID: 758fec5e2f11dc078a8ca1530305dd5539c302a1 System name: Linux Release string: Red Hat Enterprise Linux Server release 7.6 (Maipo)
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceESt8functionIFvPKcS2_EE+0x2b) [0x40cbab]: /home/vagrant/MaxScale/maxutils/maxbase/src/stacktrace.cc:130
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceEPFvPKcS1_E+0x4e) [0x40cf0e]: /usr/include/c++/4.8.2/functional:2029
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/bin/maxscale() [0x4095b9]: ??:0
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /lib64/libpthread.so.0(+0xf5d0) [0x7f87ac2b25d0]: sigaction.c:?
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZNK8maxscale14SessionCommand12get_positionEv+0x1) [0x7f87aca31581]: /home/vagrant/MaxScale/server/core/session_command.cc:29
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession23process_sescmd_responseERSt10shared_ptrIN8maxscale9RWBackendEEPP5gwbuf+0x428) [0x7f87a51a6ee8]: /home/vagrant/MaxScale/server/modules/routing/readwritesplit/rwsplit_session_cmd.cc:177
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession11clientReplyEP5gwbufP3dcb+0x4df) [0x7f87a519c3af]: /home/vagrant/MaxScale/server/modules/routing/readwritesplit/rwsplitsession.cc:708
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libreadwritesplit.so(_ZN8maxscale6RouterI7RWSplit14RWSplitSessionE11clientReplyEP10mxs_routerP18mxs_router_sessionP5gwbufP3dcb+0x24) [0x7f87a5198714]: /home/vagrant/MaxScale/include/maxscale/router.hh:206
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libmariadbbackend.so(+0x43a7) [0x7f87a49663a7]: /home/vagrant/MaxScale/server/modules/protocol/MySQL/mariadbbackend/mysql_backend.cc:1041
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7c777) [0x7f87ac9de777]: /home/vagrant/MaxScale/server/core/dcb.cc:3136
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7c911) [0x7f87ac9de911]: /home/vagrant/MaxScale/server/core/dcb.cc:3228
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1b5) [0x7f87aca3a545]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:844
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x51) [0x7f87aca3a741]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:545
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/bin/maxscale(main+0x2019) [0x4087f9]: /home/vagrant/MaxScale/server/core/gateway.cc:2259
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f87aa1ae3d5]: ??:?
      Apr 22 14:48:28 prvlopsmsc01 maxscale[18373]: (8) /usr/bin/maxscale() [0x409022]: ??:0
      Apr 22 14:48:28 prvlopsmsc01 abrt-hook-ccpp: Process 18373 (maxscale) of user 996 killed by SIGSEGV - ignoring (repeated crash)
      Apr 22 14:48:28 prvlopsmsc01 systemd: maxscale.service: main process exited, code=dumped, status=11/SEGV
      Apr 22 14:48:28 prvlopsmsc01 systemd: Unit maxscale.service entered failed state.
      Apr 22 14:48:28 prvlopsmsc01 systemd: maxscale.service failed.
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              juan.vera Juan
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.