innobackupex cannot treat exit code of xtrabackup executable
Bug #529874 reported by
Yasufumi Kinoshita
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Daniel Nichter | ||
Bug Description
Even if xtrabackup exit with error code, innobackupex script output "completed OK!".
(example)
xtrabackup: Stopping log copying thread..
xtrabackup: Error: log_copying_thread failed.
...
100301 15:43:52 innobackupex-1.5.1: completed OK!
That is because xtrabackup is executed from fork child process and the parent process don't know the exit code of the child process.
Related branches
lp:~percona-dev/percona-xtrabackup/exit-code
- Vadim Tkachenko: Approve
-
Diff: 77 lines (+20/-9)1 file modifiedinnobackupex-1.5.1 (+20/-9)
| Changed in percona-xtrabackup: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| assignee: | nobody → Daniel Nichter (daniel-percona) |
| Changed in percona-xtrabackup: | |
| status: | Confirmed → Fix Committed |
| Changed in percona-xtrabackup: | |
| milestone: | none → 1.6 |
| Changed in percona-xtrabackup: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/