PKG mysql keeps trying to start even after failure
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Fix Committed
|
Undecided
|
EvgeniyPatlan | ||
Bug Description
CentOS 7
Percona-
1. Bootstrap node1. (systemctl start mysql@bootstrap)
2. Attempt to start node2 (systemctl start mysql)
If the xtrabackup process fails for any reason, systemctl will show this message:
[root@pxc2-T1 /]# systemctl start mysql
Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
Normally, one would think that the "start" process has halted. This is NOT the case. In fact, systemctl will continue to "start" mysql over and over and over and over, etc etc, with absolutely no indication to the user unless the user is viewing the log files and sees the same messages over and over.
systemctl should not do this. If mysql fails to start, there should not be any further, automated, attempts. systemctl should mark the process dead/inactive and await manual user intervention.
| affects: | percona-server → percona-xtradb-cluster |
| Changed in percona-xtradb-cluster: | |
| assignee: | nobody → EvgeniyPatlan (evgeniy-patlan) |
| summary: |
- mysql keeps trying to start even after failure + PKG mysql keeps trying to start even after failure |
| EvgeniyPatlan (evgeniy-patlan) wrote | #1 |
| Changed in percona-xtradb-cluster: | |
| status: | New → Fix Committed |
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
The message into journal and messages has been added that indicates that the node is bootstrapped and how to work with it