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

Plantage Maxcale en charge

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 1.4.3
    • N/A
    • Core
    • None
    • Maxscale 64 bit debian wheezy

    Description

      Bonjour,

      Nous avons tenté de mettre en prod dans la soirée du 16 au 17/06, Maxscale mais ce dernier n'a pas tenu la charge après plusieurs heures. voici les logs d'erreur :
      2016-06-16 17:36:25 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 17:46:27 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 18:48:27 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 19:06:10 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 19:13:09 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 19:57:02 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 20:38:52 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 20:50:29 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 21:01:20 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 21:18:45 error : Write to dcb 0x7f24d400da30 in state DCB_STATE_NOPOLLING fd 301 failed due errno 9, Bad file descriptor
      2016-06-16 21:18:45 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 21:23:14 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 21:42:24 error : Write to dcb 0x7f24d8024870 in state DCB_STATE_NOPOLLING fd 549 failed due errno 9, Bad file descriptor
      2016-06-16 21:42:24 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 22:07:46 error : Write to dcb 0x7f24d0002890 in state DCB_STATE_NOPOLLING fd 259 failed due errno 9, Bad file descriptor
      2016-06-16 22:07:46 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 22:23:34 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 22:31:33 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 22:36:49 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-16 23:35:52 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-17 00:49:38 error : Write to dcb 0x7f24d80070f0 in state DCB_STATE_NOPOLLING fd 182 failed due errno 9, Bad file descriptor
      2016-06-17 00:49:38 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-17 01:03:46 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-17 01:27:05 error : Attempt to write buffered data to backend failed due internal inconsistent state.
      2016-06-17 01:28:54 error : Write to dcb 0x7f24d8010b30 in state DCB_STATE_DISCONNECTED fd -1 failed due errno 9, Bad file descriptor
      2016-06-17 01:28:54 error : Attempt to write buffered data to backend failed due internal inconsistent state.

      AFAIK this the 'Attempt ...' messages are related to issues with the databases itself. Does this cause any problems to the production?

      Now related to the crash at ~2AM which is the reason you opened this ticket. this is what we can see in the log:

      2016-06-17 01:57:05 error : Fatal: MaxScale 1.4.3 received fatal signal 11. Attempting backtrace.
      2016-06-17 01:57:05 error : Commit ID: c2706bab69d1f3b5f1f3ec70f78b1a4803788fec System name: Linux Release string: undefined Embedded library version: (null)
      2016-06-17 01:57:05 error : /usr/bin/maxscale() [0x40406c]
      2016-06-17 01:57:05 error : /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0) [0x7f24f8dd40a0]
      2016-06-17 01:57:05 error : /usr/lib/x86_64-linux-gnu/maxscale/libMySQLBackend.so(+0x36d4) [0x7f24de8e76d4]
      2016-06-17 01:57:05 error : /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(+0x4645f) [0x7f24f96f145f]
      2016-06-17 01:57:05 error : /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(poll_waitevents+0x5df) [0x7f24f96f0f69]
      2016-06-17 01:57:05 error : /usr/bin/maxscale(worker_thread_main+0x2a) [0x405067]
      2016-06-17 01:57:05 error : /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f24f8dcbb50]
      2016-06-17 01:57:05 error : /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f24f793a30d]

      Que peut-on faire pour résoudre ce problème ?

      En vous remerciant

      Cordialement,

      Aziz Jouhdi DSI

      Attachments

        1. maxscale.cnf
          12 kB
          dsi
        2. maxscale1.log
          846 kB
          dsi

        Activity

          People

            Unassigned Unassigned
            dsimbline dsi
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.