innobackupex and SST xtrabackup fails if log specified in my.cnf

Bug #1394936 reported by Stefano
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
New
Undecided
Unassigned

Bug Description

If in my.cnf is specified "log"

i.e.
....
....
log=/tmp/query.log
....
....

innobackupex fails and also xtrabackup SST

innobackupex output:

(....)

Unknown suffix '/' used for variable 'log-copy-interval' (value '/tmp/query.log')
xtrabackup: Error while setting value '/tmp/query.log' to 'log-copy-interval'
innobackupex: Error: no 'mysqld' group in MySQL options at /usr/bin/innobackupex line 4350.

SST in mariadb error.log (log in my.cnf specified in both sender and receiver):

141120 16:20:34 [Note] WSREP: Member 1.0 (1.2.3.4) requested state transfer from '*any*'. Selected 0.0 (1.2.3.5)(SYNCED) as donor.
141120 16:20:34 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 52552847)
141120 16:20:34 [Note] WSREP: Requesting state transfer: success, donor: 0
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
WSREP_SST: [ERROR] Error while getting data from donor node: exit codes: 0 2 (20141120 16:20:34.457)

Revision history for this message
Alexey Kopytov (akopytov) wrote :

This looks like a duplicate of bug #1347698 (fixed in 2.2.5+).

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

Other bug subscribers

Remote bug watches

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