innobackupex should have better error reporting for unrecognized server versions

Bug #1087219 reported by Alexey Kopytov
14
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_ibbackup_binary in concatenation (.) or string at ./bin/innobackupex-1.5.1 line 2140.
Can't exec "--print-param": No such file or directory at ./bin/innobackupex-1.5.1 line 2141.
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.

Tags: i29543

Related branches

description: updated
tags: added: i29543
Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :

I think for all unrecognized version we should
output proper message and exit, and do not assume
some version by default

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-608

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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