wsrep_sst_xtrabackup-v2 script causes innobackupex to print a false positive stack trace into the log about mysql-wsrep

[philip-galera]

This is reproducible both on Fedora and on Ubuntu. Our devel server is able to reproduce the error.

[philip-galera]

Possible fix:

--- ../scripts/wsrep_sst_xtrabackup-v2.sh       2014-12-16 00:32:31.996949073 -0800
+++ ../scripts/wsrep_sst_xtrabackup-v2  2015-01-02 06:01:55.240283301 -0800
@@ -550,7 +550,7 @@
 get_stream
 get_transfer

-if ${INNOBACKUPEX_BIN} /tmp --help  | grep -q -- '--version-check'; then
+if ${INNOBACKUPEX_BIN} /tmp --help  | grep -- '--version-check' >/dev/null ; then
     disver="--no-version-check"
 fi

If the output from grep is not silenced completely, the script fails elsewhere.

[philip-galera]

This is caused by this xtrabackup revision:

http://bazaar.launchpad.net/~percona-core/percona-xtrabackup/2.3/revision/5031

which was an attempt to add stack traces for error conditions.

[akopytov]

There's nothing wrong with the referenced revision: the code does what it is supposed to do. The root cause is a fatal signal received by innobackupex, rather than the stray backtrace, which is only a side effect. Which can be fixed by either making innobackupex ignore certain fatal signals with --help, or suppressing error output from "innobackupex --help". How about adding "2>/dev/null"?

[philip-galera]

Yes, you are right, as you can see above, adding >/dev/null seems to fix the problem.