FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (1 retries left)

Bug #1678356 reported by jeck
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Expired
Undecided
Unassigned

Bug Description

always retry ,but not ok
system centos7.2 ocata release image :centos source registry

ok: [node02]
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (10 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (9 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (8 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (7 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (6 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (5 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (4 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (3 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (2 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (1 retries left).
fatal: [node01]: FAILED! => {"changed": false, "elapsed": 60, "failed": true, "msg": "Timeout when waiting for search string MariaDB in 10.5.11.16:3306"}

TASK [mariadb : Creating haproxy mysql user] ***********************************
fatal: [node02]: FAILED! => {"changed": false, "failed": true, "msg": "(1047, 'WSREP has not yet prepared node for application use')"}

NO MORE HOSTS LEFT *************************************************************
 to retry, use: --limit @/usr/share/kolla-ansible/ansible/site.retry

PLAY RECAP *********************************************************************
node01 : ok=113 changed=62 unreachable=0 failed=1
node02 : ok=109 changed=59 unreachable=0 failed=1

all mariadb is ok
[root@node01 ~]# docker ps |grep maria
45b989f52473 localhost:4000/lokolla/centos-source-mariadb:4.0.0 "kolla_start" 12 minutes ago Up 12 minutes mariadb
[root@node01 ~]#
[root@node01 kolla-ansible]# docker ps |grep mar
45b989f52473 localhost:4000/lokolla/centos-source-mariadb:4.0.0 "kolla_start" 12 minutes ago Up 12 minutes

【maradb log】
[root@node01 mariadb]# ls
mariadb.log
[root@node01 mariadb]# grep -rn "failed"
mariadb.log:78:170401 10:52:21 [Warning] WSREP: access file(/var/lib/mysql//gvwstate.dat) failed(No such file or directory)
mariadb.log:79:170401 10:52:21 [Note] WSREP: restore pc from disk failed
mariadb.log:139:170401 10:52:21 [ERROR] WSREP: Notification command failed: 1 (Operation not permitted): "/usr/local/bin/wsrep-notify.sh --status Joined --uuid 39eb94e0-1686-11e7-ab6b-46fc30f0467c --primary yes --index 0 --members 39eab74c-1686-11e7-b05e-22e2f7acb676/node01/10.5.11.16:0"
mariadb.log:147:170401 10:52:21 [ERROR] WSREP: Notification command failed: 1 (Operation not permitted): "/usr/local/bin/wsrep-notify.sh --status Synced"
mariadb.log:218:170401 10:52:34 [Warning] WSREP: access file(/var/lib/mysql//gvwstate.dat) failed(No such file or directory)
mariadb.log:219:170401 10:52:34 [Note] WSREP: restore pc from disk failed

Revision history for this message
bruce (brucexie) wrote :

I also meet this issue:

TASK [mariadb : Waiting for MariaDB service to be ready] ********************************************************************
FAILED - RETRYING: Waiting for MariaDB service to be ready (10 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (9 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (8 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (7 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (6 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (5 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (4 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (3 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (2 retries left).
FAILED - RETRYING: Waiting for MariaDB service to be ready (1 retries left).
fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false, "elapsed": 60, "failed": true, "msg": "Timeout when waiting for search string MariaDB in 10.19.0.24:3306"}
 to retry, use: --limit @/usr/share/kolla-ansible/ansible/site.retry

PLAY RECAP ******************************************************************************************************************
localhost : ok=63 changed=7 unreachable=0 failed=1

Command failed ansible-playbook -i /root/all-in-one -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e action=deploy /usr/share/kolla-ansible/ansible/site.yml

Revision history for this message
Eduardo Gonzalez (egonzalez90) wrote :

Cannot verify, is still present the bug or provide more information?

Changed in kolla-ansible:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for kolla-ansible because there has been no activity for 60 days.]

Changed in kolla-ansible:
status: Incomplete → Expired
Revision history for this message
1091198228 (d1091198228) wrote :

我在尝试禁用haproxy的情况下开始部署,他也提示了这个错误。

Revision history for this message
1091198228 (d1091198228) wrote :

如果你禁用了haproxy,再尝试部署,请修改 /path/to/virtualenv/share/kolla-ansible/ansible/roles/mariadb/tasks/wait_for_loadbalancer.yml 文件,在此文件中加入ignore_errors: True来跳过此错误。

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.