innobackupex should have better error reporting for unrecognized server versions
Bug #1087219 reported by
Alexey Kopytov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Alexey Kopytov | ||
2.0 |
Fix Released
|
Medium
|
Alexey Kopytov | ||
2.1 |
Fix Released
|
Medium
|
Alexey Kopytov |
Bug Description
Currently when innobackupex cannot recognize a server version, it "reports" it in a rather awkward way, i.e.:
"
Use of uninitialized value $option_
Can't exec "--print-param": No such file or directory at ./bin/innobacku
innobackupex-1.5.1: fatal error: no 'mysqld' group in MySQL options
innobackupex-1.5.1: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options
"
We should improve it, so that it is at least clear the server version is not supported.
Related branches
lp:~akopytov/percona-xtrabackup/bug1087219-2.0
- Sergei Glushchenko (community): Approve (g2)
-
Diff: 17 lines (+8/-0)1 file modifiedinnobackupex (+8/-0)
lp:~akopytov/percona-xtrabackup/bug1087219-2.1
- Sergei Glushchenko (community): Approve (g2)
-
Diff: 17 lines (+8/-0)1 file modifiedinnobackupex (+8/-0)
I think for all unrecognized version we should
output proper message and exit, and do not assume
some version by default