mariadb cannot start in master

Bug #1543906 reported by Lingfeng Xiong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Undecided
Unassigned

Bug Description

I am using master branch (b479d8db0357d9c72aa95fc0bdbd7c873878bb4d) to build images with "-b ubuntu -t binary". The mariadb container stucked at restarting status.

docker logs:
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Removing existing destination: /etc/mysql/my.cnf
INFO:__main__:Copying /var/lib/kolla/config_files/galera.cnf to /etc/mysql/my.cnf
INFO:__main__:Setting permissions for /etc/mysql/my.cnf
INFO:__main__:Writing out command to execute
Running command: '/usr/bin/mysqld_safe'
160210 04:46:09 mysqld_safe Logging to '/var/lib/mysql//xxxxx.err'.
160210 04:46:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
160210 04:46:09 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql//wsrep_recovery.kgoj5s' --pid-file='/var/lib/mysql//xxxxx-recover.pid'
160210 04:46:12 mysqld_safe WSREP: Recovered position 00000000-0000-0000-0000-000000000000:-1
160210 04:46:12 mysqld_safe mysqld from pid file /var/lib/mysql/mariadb.pid ended
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Removing existing destination: /etc/mysql/my.cnf
INFO:__main__:Copying /var/lib/kolla/config_files/galera.cnf to /etc/mysql/my.cnf
INFO:__main__:Setting permissions for /etc/mysql/my.cnf
INFO:__main__:Writing out command to execute
Running command: '/usr/bin/mysqld_safe'
160210 04:46:13 mysqld_safe Logging to '/var/lib/mysql//xxxxx.err'.
160210 04:46:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
160210 04:46:13 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql//wsrep_recovery.wtk7oD' --pid-file='/var/lib/mysql//xxxxx-recover.pid'
160210 04:46:15 mysqld_safe WSREP: Recovered position 00000000-0000-0000-0000-000000000000:-1
160210 04:46:15 mysqld_safe mysqld from pid file /var/lib/mysql/mariadb.pid ended
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Removing existing destination: /etc/mysql/my.cnf
INFO:__main__:Copying /var/lib/kolla/config_files/galera.cnf to /etc/mysql/my.cnf
INFO:__main__:Setting permissions for /etc/mysql/my.cnf
INFO:__main__:Writing out command to execute
Running command: '/usr/bin/mysqld_safe'
160210 04:46:15 mysqld_safe Logging to '/var/lib/mysql//xxxxx.err'.
160210 04:46:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
160210 04:46:15 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql//wsrep_recovery.v2HF3m' --pid-file='/var/lib/mysql//xxxxx-recover.pid'
160210 04:46:18 mysqld_safe WSREP: Recovered position 00000000-0000-0000-0000-000000000000:-1
160210 04:46:18 mysqld_safe mysqld from pid file /var/lib/mysql/mariadb.pid ended
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Removing existing destination: /etc/mysql/my.cnf
INFO:__main__:Copying /var/lib/kolla/config_files/galera.cnf to /etc/mysql/my.cnf
INFO:__main__:Setting permissions for /etc/mysql/my.cnf
INFO:__main__:Writing out command to execute
Running command: '/usr/bin/mysqld_safe'
160210 04:46:19 mysqld_safe Logging to '/var/lib/mysql//xxxxx.err'.
160210 04:46:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
160210 04:46:19 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql//wsrep_recovery.DrTuk0' --pid-file='/var/lib/mysql//xxxxx-recover.pid'
160210 04:46:21 mysqld_safe WSREP: Recovered position 00000000-0000-0000-0000-000000000000:-1
160210 04:46:21 mysqld_safe mysqld from pid file /var/lib/mysql/mariadb.pid ended
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Removing existing destination: /etc/mysql/my.cnf
INFO:__main__:Copying /var/lib/kolla/config_files/galera.cnf to /etc/mysql/my.cnf
INFO:__main__:Setting permissions for /etc/mysql/my.cnf
INFO:__main__:Writing out command to execute
Running command: '/usr/bin/mysqld_safe'
160210 04:46:23 mysqld_safe Logging to '/var/lib/mysql//xxxxx.err'.
160210 04:46:23 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
160210 04:46:23 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql//wsrep_recovery.Hx3Zi1' --pid-file='/var/lib/mysql//xxxxx-recover.pid'
160210 04:46:25 mysqld_safe WSREP: Recovered position 00000000-0000-0000-0000-000000000000:-1
160210 04:46:25 mysqld_safe mysqld from pid file /var/lib/mysql/mariadb.pid ended

Revision history for this message
Lingfeng Xiong (xionglingfeng) wrote :

This problem is resolved by removing volume for mariadb

docker volume rm mariadb

Changed in kolla:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.