Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

mysql container not loading #1

Open
kjetilhp opened this issue Oct 30, 2015 · 2 comments
Open

mysql container not loading #1

kjetilhp opened this issue Oct 30, 2015 · 2 comments

Comments

@kjetilhp
Copy link

Having issues with the mysql container during set up of resources.

=> Waiting for confirmation of MySQL service startup, trying 58/60 ...
=> Waiting for confirmation of MySQL service startup, trying 59/60 ...
Time out. Error log is shown as below:
150921 19:42:34 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150921 19:42:34 [Note] Plugin 'FEDERATED' is disabled.
150921 19:42:34 InnoDB: The InnoDB memory heap is disabled
150921 19:42:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150921 19:42:34 InnoDB: Compressed tables use zlib 1.2.8
150921 19:42:34 InnoDB: Using Linux native AIO
150921 19:42:35 InnoDB: Initializing buffer pool, size = 128.0M
150921 19:42:35 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
150921 19:42:35  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
150921 19:42:35  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
150921 19:42:36  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
150921 19:42:36  InnoDB: Waiting for the background threads to start
150921 19:42:37 InnoDB: 5.5.44 started; log sequence number 0
150921 19:42:37  InnoDB: Starting shutdown...
150921 19:42:38  InnoDB: Shutdown completed; log sequence number 1595675
150921 19:42:38 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150921 19:42:38 [Note] Plugin 'FEDERATED' is disabled.
150921 19:42:38 InnoDB: The InnoDB memory heap is disabled
150921 19:42:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150921 19:42:38 InnoDB: Compressed tables use zlib 1.2.8
150921 19:42:38 InnoDB: Using Linux native AIO
150921 19:42:38 InnoDB: Initializing buffer pool, size = 128.0M
150921 19:42:38 InnoDB: Completed initialization of buffer pool
150921 19:42:38 InnoDB: highest supported file format is Barracuda.
150921 19:42:38  InnoDB: Waiting for the background threads to start
150921 19:42:39 InnoDB: 5.5.44 started; log sequence number 1595675
ERROR: 1064  You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ALTER TABLE user ADD column Show_view_priv enum('N','Y') CHARACTER SET utf8 NOT ' at line 1
150921 19:42:39 [ERROR] Aborting

150921 19:42:39  InnoDB: Starting shutdown...
150921 19:42:43  InnoDB: Shutdown completed; log sequence number 1595675
150921 19:42:44 [Note] /usr/sbin/mysqld: Shutdown complete

150921 19:42:44 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150921 19:42:44 [Note] Plugin 'FEDERATED' is disabled.
150921 19:42:44 InnoDB: The InnoDB memory heap is disabled
150921 19:42:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150921 19:42:44 InnoDB: Compressed tables use zlib 1.2.8
150921 19:42:44 InnoDB: Using Linux native AIO
150921 19:42:44 InnoDB: Initializing buffer pool, size = 128.0M
150921 19:42:44 InnoDB: Completed initialization of buffer pool
150921 19:42:44 InnoDB: highest supported file format is Barracuda.
150921 19:42:44  InnoDB: Waiting for the background threads to start
150921 19:42:45 InnoDB: 5.5.44 started; log sequence number 1595675
150921 19:42:45  InnoDB: Starting shutdown...
150921 19:42:46  InnoDB: Shutdown completed; log sequence number 1595675
150921 19:42:46 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150921 19:42:46 [Note] Plugin 'FEDERATED' is disabled.
150921 19:42:46 InnoDB: The InnoDB memory heap is disabled
150921 19:42:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150921 19:42:46 InnoDB: Compressed tables use zlib 1.2.8
150921 19:42:46 InnoDB: Using Linux native AIO
150921 19:42:46 InnoDB: Initializing buffer pool, size = 128.0M
150921 19:42:46 InnoDB: Completed initialization of buffer pool
150921 19:42:46 InnoDB: highest supported file format is Barracuda.
150921 19:42:46  InnoDB: Waiting for the background threads to start
150921 19:42:47 InnoDB: 5.5.44 started; log sequence number 1595675
ERROR: 1050  Table 'plugin' already exists
150921 19:42:47 [ERROR] Aborting

150921 19:42:47  InnoDB: Starting shutdown...
150921 19:42:48  InnoDB: Shutdown completed; log sequence number 1595675
150921 19:42:48 [Note] /usr/sbin/mysqld: Shutdown complete

151030 10:06:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
/usr/sbin/mysqld: error while loading shared libraries: libaio.so.1: cannot open shared object file: Permission denied
151030 10:06:20 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

I've tried running the the tutum/mysql image directly and the same happens there as soon as the /var/lib/mysql directory is set.
so this doesn't work:

docker run --privileged -p 3306:3306 -e "MYSQL_USER=ninja" -e "MYSQL_PASS=ninja" -e ON_CREATE_DB="douitsu" -v /var/lib/sphere-stack/mysql:/var/lib/mysql tutum/mysql

but this works..

$ docker run -p 3306:3306 -e "MYSQL_USER=ninja" -e "MYSQL_PASS=ninja" -e ON_CREATE_DB="douitsu" tutum/mysql
Unable to find image 'tutum/mysql:latest' locally
latest: Pulling from tutum/mysql
5b76f7c1436d: Pull complete
de9f9f30df91: Pull complete
18c0be32c896: Pull complete
89bc2eaf6fe4: Pull complete
662882007e5b: Pull complete
bee42056badb: Pull complete
7028a3ad3c2d: Pull complete
7bfea61b3a2f: Pull complete
6078d9206b7b: Pull complete
f18c96af8f24: Pull complete
3c093a4184ec: Pull complete
6cee3e08ca18: Pull complete
d87c8f9088e2: Pull complete
e94ac571b623: Pull complete
Digest: sha256:6777c5f2627b954fc6f7937f1722fbbab363666d091816c4ea8dd1117458670a
Status: Downloaded newer image for tutum/mysql:latest
=> Using an existing volume of MySQL
=> Starting MySQL ...
=> Waiting for confirmation of MySQL service startup, trying 0/60 ...
=> Waiting for confirmation of MySQL service startup, trying 1/60 ...
=> Creating admin user ...
151030 10:14:26  InnoDB: Waiting for the background threads to start
151030 10:14:27 InnoDB: 5.5.44 started; log sequence number 1595675
151030 10:14:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
151030 10:14:27 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
151030 10:14:27 [Note] Server socket created on IP: '0.0.0.0'.
151030 10:14:27 [Warning] 'user' entry 'root@e611e15f9c9d' ignored in --skip-name-resolve mode.
151030 10:14:27 [Warning] 'proxies_priv' entry '@ root@e611e15f9c9d' ignored in --skip-name-resolve mode.
151030 10:14:27 [Note] Event Scheduler: Loaded 0 events
151030 10:14:27 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.44-0ubuntu0.14.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
=> Creating MySQL user ninja with preset password
=> Done!
========================================================================
You can now connect to this MySQL Server using:

    mysql -uninja -pninja -h<host> -P<port>

Please remember to change the above password as soon as possible!
MySQL user 'root' has no password but only allows local connections
========================================================================
Creating MySQL database douitsu
Database created!
tail -F $LOG
@jonseymour
Copy link
Contributor

Hi, sorry I completely missed this issue until just now. Let me know if this is still a problem and I will help you get to a resolution.

@techknowlogick
Copy link
Collaborator

@kjetilhp this is 3 years later, but I've just committed a new PR (#5) which upgrades docker-compose to v3 format, which also includes a change from the tumtum mysql docker image to the official mariadb one, which may work for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@techknowlogick @jonseymour @kjetilhp