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

LP:942283 - MariaDB crashes on import from MySQL mysqldump export

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Resolution: Not a Bug
    • None
    • None
    • None

    Description

      So in the process of moving to a new VPS (fancy name for a VM) with MariaDB installed (Ubuntu 10.04 LTS, stock MariaDB, whichever one is the latest in the apt sources), and when I try run the .sql export on my MariaDB installation I get the following:

      root@primary:~# mysql -q -u root -p prod_test < dmp.sql
      ERROR 2013 (HY000) at line 1529: Lost connection to MySQL server during query

      Line 1529 is quite innocuous: /*!40000 ALTER TABLE `tblSubscriptionEmail` ENABLE KEYS */;

      This is consistent and reproducible. Since MariaDB errors out to syslog, I checked my syslog to see what it had to say, and here it is:

      Feb 28 00:14:21 primary kernel: [2247125.181808] OOM killed process 20943 (mysqld) vm:1347796kB, rss:404944kB, swap:0kB
      Feb 28 00:14:22 primary mysqld_safe: Number of processes running now: 0
      Feb 28 00:14:22 primary mysqld_safe: mysqld restarted
      Feb 28 00:14:22 primary mysqld: 120228 00:14:22 [Note] PrimeBase XT (PBXT) Engine 1.0.11-7 Pre-GA loaded...
      Feb 28 00:14:22 primary mysqld: 120228 00:14:22 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
      Feb 28 00:14:22 primary mysqld: 120228 00:14:22 [Note] The server was not shutdown correctly, recovery required
      Feb 28 00:14:22 primary mysqld: InnoDB: The InnoDB memory heap is disabled
      Feb 28 00:14:22 primary mysqld: InnoDB: Mutexes and rw_locks use GCC atomic builtins
      Feb 28 00:14:22 primary mysqld: InnoDB: Compressed tables use zlib 1.2.3.3
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 InnoDB: Initializing buffer pool, size = 256.0M
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 InnoDB: Completed initialization of buffer pool
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 InnoDB: highest supported file format is Barracuda.
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 Percona XtraDB (http://www.percona.com) 1.0.17-13.0 started; log sequence number 45356
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 [Note] Recovering after a crash using /var/log/mysql/mariadb-bin
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 [Note] Starting crash recovery...
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 [Note] Crash recovery finished.
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 [Note] Event Scheduler: Loaded 0 events
      Feb 28 00:14:22 primary mysqld: 120228 0:14:22 [Note] /usr/sbin/mysqld: ready for connections.
      Feb 28 00:14:22 primary mysqld: Version: '5.3.4-MariaDB-rc-mariadb111~lucid-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (MariaDB - http://mariadb.com/)

      What gives? Is it a memory leak that's causing the process to be terminated? I'll gladly give up a copy of the 44mb MySQL dump, but I would have to do so privately for privacy concerns.

      Attachments

        1. LPexportBug942283_my.cnf
          6 kB
          Rasmus Johansson
        2. LPexportBug942283.xml
          25 kB
          Rasmus Johansson

        Activity

          People

            Unassigned Unassigned
            riccardospagni Riccardo Spagni (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 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.