Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6621

Drupal locked at replicated server,...

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not a Bug
    • Affects Version/s: 10.0.12-galera
    • Fix Version/s: 10.0.15-galera
    • Component/s: Galera
    • Labels:
    • Environment:
      Ubuntu LTS
      3.13.0-34-generic

      Description

      Have mixed aria, inno and tokudb database.
      All innidb realted work's 100%,.. but no drupal at any!

      Drupal works at first server started and at second drupal gives error from semphore lock.

      ====
      PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drupal.semaphore' doesn't exist: SELECT expire, value FROM

      {semaphore}

      WHERE name = :name; Array ( [:name] => variable_init ) in lock_may_be_available() (line 167 of /var/www/drupal/includes/lock.inc).
      ===

      from mysql log file:
      140821 17:12:05 476 Connect drupal@localhost as anonymous on drupal
      476 Query SET NAMES utf8
      476 Query SET sql_mode = 'ANSI,STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER'
      476 Query SELECT cid, data, created, expire, serialized FROM cache_bootstrap WHERE cid IN ('variables')
      476 Query INSERT INTO semaphore (name, value, expire) VALUES ('variable_init', '9908178453f5fe35772006.91507988', '1408630326.4874')
      476 Query SELECT expire, value FROM semaphore WHERE name = 'variable_init'
      476 Query SELECT cid, data, created, expire, serialized FROM cache_bootstrap WHERE cid IN ('module_implements')
      476 Query SELECT cid, data, created, expire, serialized FROM cache WHERE cid IN ('theme_registry:build:modules')
      476 Query SELECT filename FROM system WHERE name = 'bartik' AND type = 'theme'
      476 Query DELETE FROM semaphore
      WHERE (value = '9908178453f5fe35772006.91507988')
      476 Quit

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            Are you really using Galera as you stated in the 'Affects Versions' field?
            Which engine does the table semaphore belong to?

            Show
            elenst Elena Stepanova added a comment - Are you really using Galera as you stated in the 'Affects Versions' field? Which engine does the table semaphore belong to?
            Hide
            boy007 Joni-Pekka Kurronen added a comment -

            hi,

            wsrep just jam's.

            Solution is to uncoment wsrep and start and stop mariadb.
            Comment out wsrep and do create new cluster.

            It just jam's time to time and dose not come alive,...

            joni

            Show
            boy007 Joni-Pekka Kurronen added a comment - hi, wsrep just jam's. Solution is to uncoment wsrep and start and stop mariadb. Comment out wsrep and do create new cluster. It just jam's time to time and dose not come alive,... joni
            Hide
            elenst Elena Stepanova added a comment -

            I don't think Galera cluster is currently expected to work well on a mix of InnoDB, Aria and TokuDB. Assigning to Nirbhay Choubey to confirm.

            Show
            elenst Elena Stepanova added a comment - I don't think Galera cluster is currently expected to work well on a mix of InnoDB, Aria and TokuDB. Assigning to Nirbhay Choubey to confirm.
            Hide
            boy007 Joni-Pekka Kurronen added a comment -

            hi,

            REASON FOUND!

            mariadb can JAM at startup if wsrep user do not have needed privilges to access file's.
            Lacking proviledges was caused LDAP service that did not work all times.
            Still MARIADB should log situation to syslog / logfiles in clear language "Authentication failed / Can not aopen file, files right's / Can not open connetion / .... " to speed up problem solving. Hanging and starting-up mariadb client can be killed only by KILL -9 <PID> and that's
            not good practice.

            Show
            boy007 Joni-Pekka Kurronen added a comment - hi, REASON FOUND! mariadb can JAM at startup if wsrep user do not have needed privilges to access file's. Lacking proviledges was caused LDAP service that did not work all times. Still MARIADB should log situation to syslog / logfiles in clear language "Authentication failed / Can not aopen file, files right's / Can not open connetion / .... " to speed up problem solving. Hanging and starting-up mariadb client can be killed only by KILL -9 <PID> and that's not good practice.
            Hide
            nirbhay_c Nirbhay Choubey added a comment -

            Server does emit appropriate error messages like "Permission denied", etc, before aborting when its started with a data directory for which it does not have necessary permissions.

            Show
            nirbhay_c Nirbhay Choubey added a comment - Server does emit appropriate error messages like "Permission denied", etc, before aborting when its started with a data directory for which it does not have necessary permissions.

              People

              • Assignee:
                nirbhay_c Nirbhay Choubey
                Reporter:
                boy007 Joni-Pekka Kurronen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: