Not the answer you need?
Register and ask your own question!

xtrabackup_55: Error writing file 'UNOPENED' (Errcode: 32)

spin0usspin0us EntrantCurrent User Role Beginner
Hi all,

I have a 3 node percona XtraDB cluster. I've just upgraded one of my node, and can't get it back in the cluster. Here is the error :
131026 22:52:31 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup --role 'joiner' --address '1.2.3.4' --auth 'sstuser:*******' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' --parent '18284': 32 (Broken pipe)
131026 22:52:31 [ERROR] WSREP: Failed to read uuid:seqno from joiner script.
131026 22:52:31 [ERROR] WSREP: SST failed: 32 (Broken pipe)
131026 22:52:31 [ERROR] Aborting
Going on my master node i see this error :
WSREP_SST: [ERROR] innobackupex finished with error: 1. Check /var/lib/mysql//innobackup.backup.log (20131026 22:52:31.758)
Here is the content of /var/lib/mysql//innobackup.backup.log
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

131026 22:52:29 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_file=/etc/mysql/my.cnf;mysql_read_default_group=xtrabackup;mysql_s ocket=/var/run/mysqld/mysqld.sock' as 'sstuser' (using password: YES).
131026 22:52:29 innobackupex: Connected to MySQL server
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".

innobackupex: Using mysql server version 5.5.31-55

innobackupex: Created backup directory /tmp

131026 22:52:29 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-file="/etc/mysql/my.cnf" --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/tmp --tmpdir=/tmp --stream=tar
innobackupex: Waiting for ibbackup (pid=15666) to suspend
innobackupex: Suspend file '/tmp/xtrabackup_suspended_2'

xtrabackup_55 version 2.1.5 for Percona Server 5.5.31 Linux (x86_64) (revision id: 680)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 134217728
>> log scanned up to (44555358797)
xtrabackup_55: Error writing file 'UNOPENED' (Errcode: 32)
archive_write_header() failed.
[01] xtrabackup: error: cannot open the destination stream for ibdata1
[01] xtrabackup: Error: xtrabackup_copy_datafile() failed.
[01] xtrabackup: Error: failed to copy datafile.
innobackupex: Error: The xtrabackup child process has died at /usr//bin/innobackupex line 2579.
SELINUX is disabled on each nodes.

Comments

  • spin0usspin0us Entrant Current User Role Beginner
    Downgrading to previous server version seems to solve this problem.
    dpkg -i percona-xtradb-cluster-server-5.5_5.5.31-23.7.5-438.precise_amd64.deb
    
    So to perform the server upgrade, i need to stop all nodes of cluster ... :(
  • lolominlolomin Contributor Current User Role Supporter
    Hi spin0us,

    I have the exact same problem trying to prepare the upgrade of a production cluster on Debian Wheezy from 5.5.31-23.7.5-438.wheezy to 5.5.33-23.7.6-496.wheezy, what could be done to solve this problem please ?

    Regards,

    Laurent
  • lolominlolomin Contributor Current User Role Supporter
    Ok, after downgrading/rollback this node to v5.5.31 then checks that everything was still OK for all nodes after downgrade, I've finally found these informations (bottom of the page) at this URL : http://www.percona.com/doc/percona-xtradb-cluster/errata.html#incompatibilities

    So I've replaced wsrep_sst_xtrabackup and wsrep_sst_common on donor node *before* upgrade of first node to v5.5.33 and everything works OK, node was upgraded properly and syncs back OK with others nodes still in v5.5.31 in the cluster.

    Regards,

    Laurent
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.