9

I am running mysql inside docker with its /var/lib/mysql mounted on HOST.

Eveything was working fine . Then i upgraded the docker from 1.4 to 1.5 .

I rebuild the mysql image and but /var/lib/mysql stays same.

Now whenever i start conatiner then the conatiner exits after 5 minutes. The log files sat this

2015-01-03 09:26:47 353 [Note] Plugin 'FEDERATED' is disabled.
2015-01-03 09:26:47 353 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-01-03 09:26:47 353 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-03 09:26:47 353 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-01-03 09:26:47 353 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-01-03 09:26:47 353 [Note] InnoDB: Using Linux native AIO
2015-01-03 09:26:47 353 [Note] InnoDB: Using CPU crc32 instructions
2015-01-03 09:26:47 353 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-01-03 09:26:47 353 [Note] InnoDB: Completed initialization of buffer pool
2015-01-03 09:26:47 353 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-03 09:26:51 353 [Note] InnoDB: 128 rollback segment(s) are active.
2015-01-03 09:26:51 353 [Note] InnoDB: Waiting for purge to start
2015-01-03 09:26:51 353 [Note] InnoDB: 5.6.19 started; log sequence number 1625977
2015-01-03 09:26:51 353 [Note] Binlog end
2015-01-03 09:26:51 353 [Note] InnoDB: FTS optimize thread exiting.
2015-01-03 09:26:51 353 [Note] InnoDB: Starting shutdown...
2015-02-13 09:08:02 1106 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-02-13 09:08:02 510 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2015-02-13 09:08:02 510 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-02-13 09:08:03 1106 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2015-02-13 09:08:03 1106 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-02-13 09:08:03 510 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2015-02-13 09:08:03 510 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2015-02-13 09:08:04 1106 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2015-02-13 09:08:04 1106 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
user192362127
  • 215
  • 1
  • 3
  • 5
  • While searching the internet for the error `Unable to lock ./ibdata1`, many wrote about solution that involved moving ibdata to another dir and then copying it back. After that, restarting mysql initiated db repair and all was good. But I cant tell why that works. You may try. – titus Feb 13 '15 at 09:38
  • @titus i tried that and i did mistake. instead of `cp -a` i just copied it and removed original one . i did `cp` instead of `mv` i can't even start the conatiner. is there way to fix that – user192362127 Feb 13 '15 at 10:18
  • Copy the file back. And start the container. Remember those are solutions people reported that are working. It was up to you to read a little bit deeper. – titus Feb 13 '15 at 13:53

1 Answers1

4
  1. Run ls -la in your mysql data directory:
-rw-r----- 1     999     999        56 апр 27 00:08 auto.cnf
-rw-r----- 1     999     999         0 мая 20 21:51 binlog.index
-rw------- 1     999     999      1679 апр 27 00:08 ca-key.pem
-rw-r--r-- 1     999     999      1107 апр 27 00:08 ca.pem
-rw-r--r-- 1     999     999      1107 апр 27 00:08 client-cert.pem
-rw------- 1     999     999      1675 апр 27 00:08 client-key.pem
drwxr-x--- 2     999     999      4096 июн  3 22:06 default
-rw-r----- 1     999     999     14730 мая 29 22:14 ib_buffer_pool
-rw-r----- 1     999     999  79691776 июн  6 08:49 ibdata1
-rw-r----- 1     999     999  50331648 июн  6 08:49 ib_logfile0
-rw-r----- 1     999     999  50331648 июн  6 08:49 ib_logfile1
-rw-r----- 1     999     999 146800640 июн  5 22:53 ibtmp1
drwxr-x--- 2     999     999      4096 апр 27 00:08 mysql
drwxr-x--- 2     999     999      4096 апр 27 00:08 performance_schema
-rw------- 1     999     999      1679 апр 27 00:08 private_key.pem
-rw-r--r-- 1     999     999       451 апр 27 00:08 public_key.pem
-rw-r--r-- 1     999     999      1107 апр 27 00:08 server-cert.pem
-rw------- 1     999     999      1679 апр 27 00:08 server-key.pem
drwxr-x--- 2     999     999     12288 апр 27 00:08 sys

In my case this is user 999

2.Try ps -ef | grep mysqld 

999      22177 22138  0 мая30 ?     00:09:25 mysqld
romiras  29164  6344  0 18:12 pts/2    00:00:00 grep --color=auto mysqld

  1. Kill this process sudo kill -9 22177

  2. Run the container again

Sintsov Roman
  • 41
  • 2