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

Maxscale crashed after losing connection to master database

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 2.3.4
    • N/A
    • failover
    • None
    • Centos 7, Percona Mysql backend, PHP front end

    Description

      MaxScale lost connection to the master server and promptly crashed. The relevant log lines are below.

      Mar  7 03:10:17 maxscale-2 maxscale[15414]: Monitor timed out when connecting to server db-master[192.168.50.46:3306] : 'Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 110'
      		 
      Mar  7 03:10:17 maxscale-2 maxscale[15414]: Server changed state: db-master[192.168.50.46:3306]: master_down. [Master, Running] -> [Down]
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]: Server changed state: db-master[192.168.50.46:3306]: master_up. [Down] -> [Master, Running]
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]: Fatal: MaxScale 2.3.4 received fatal signal 11. Attempting backtrace.
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]: Commit ID: aea64aede280558ca6b55500dfa7eb049ec9c377 System name: Linux Release string: CentOS Linux release 7.6.1810 (Core)
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]:  /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceESt8functionIFvPKcS2_EE+0x2b) [0x40cbab]: /home/vagrant/MaxScale/maxutils/maxbase/src/stacktrace.cc:130
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]:  /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceEPFvPKcS1_E+0x4e) [0x40cf0e]: /usr/include/c++/4.8.2/functional:2029
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]:  /usr/bin/maxscale() [0x4095b9]: ??:0
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]:  /lib64/libpthread.so.0(+0xf5d0) [0x7f0653b925d0]: sigaction.c:?
      		 
      Mar  7 03:10:18 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession17handle_got_targetEP5gwbufRSt10shared_ptrIN8maxscale9RWBackendEEb+0x9d) [0x7f064747512d]: /home/vagrant/MaxScale/include/maxscale/protocol/mysql.h:629
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession17route_single_stmtEP5gwbuf+0xa05) [0x7f0647476115]: /home/vagrant/MaxScale/server/modules/routing/readwritesplit/rwsplit_route_stmt.cc:328
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession10routeQueryEP5gwbuf+0x1bc) [0x7f064746d71c]: /home/vagrant/MaxScale/server/modules/routing/readwritesplit/rwsplitsession.cc:199
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libreadwritesplit.so(_ZN8maxscale6RouterI7RWSplit14RWSplitSessionE10routeQueryEP10mxs_routerP18mxs_router_sessionP5gwbuf+0x1e) [0x7f064746b7ae]: /home/vagrant/MaxScale/include/maxscale/router.hh:181
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xcbf9f) [0x7f065430df9f]: /home/vagrant/MaxScale/server/core/session.cc:1115
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker4tickEv+0xe6) [0x7f065431b426]: /home/vagrant/MaxScale/maxutils/maxbase/include/maxbase/worker.hh:777
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase11WorkerTimer6handleEPNS_6WorkerEj+0x36) [0x7f0654319bc6]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:256
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1b5) [0x7f065431a5c5]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:844
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x51) [0x7f065431a7c1]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:545
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /lib64/libstdc++.so.6(+0xb5070) [0x7f0652bc6070]: ??:?
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /lib64/libpthread.so.0(+0x7dd5) [0x7f0653b8add5]: pthread_create.c:?
      		 
      Mar  7 03:10:19 maxscale-2 maxscale[15414]:  /lib64/libc.so.6(clone+0x6d) [0x7f0651b6aead]: ??:?
      		 
      Mar  7 03:10:19 maxscale-2 abrt-hook-ccpp: Process 15414 (maxscale) of user 995 killed by SIGSEGV - dumping core
      		 
      Mar  7 03:10:28 maxscale-2 abrt-hook-ccpp: Failed to create core_backtrace: waitpid failed: No child processes
      		 
      Mar  7 03:10:29 maxscale-2 systemd: maxscale.service: main process exited, code=killed, status=11/SEGV
      		 
      Mar  7 03:10:29 maxscale-2 systemd: Unit maxscale.service entered failed state.
      		 
      Mar  7 03:10:29 maxscale-2 systemd: maxscale.service failed.

      Attachments

        1. maxscale.cnf
          3 kB
        2. CCRFilter.cnf
          0.0 kB
        3. Hint.cnf
          0.0 kB
        4. QLAProd.cnf
          0.1 kB
        5. QLASMP01.cnf
          0.1 kB
        6. Read-Write-Service.cnf
          0.5 kB
        7. Top.cnf
          0.0 kB
        8. TopSmp01.cnf
          0.1 kB
        9. dbm-lock-filter.cnf
          0.2 kB
        10. dnr-filter.cnf
          0.1 kB
        11. engine-injector-recipients-filter.cnf
          0.1 kB

        Activity

          People

            markus makela markus makela
            jparker-resgen Jeffrey Parker
            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.