Comment 9 for bug 1201686

From the investigation I did I found

a) A bug in xb_galera_sst introduced by new framework - fixing it.

b) An issue with innobackupex itself:

 >> log scanned up to (8443459)
 130723 5:20:06 InnoDB: Warning: allocated tablespace 10, old maximum was 9
 [01] Streaming ./ibdata1
 [01] ...done
 [01] Streaming ./sakila/actor.ibd
 [01] ...done
 [01] Streaming ./sakila/address.ibd
 [01] ...done
 [01] Streaming ./sakila/category.ibd
 [01] ...done
 [01] Streaming ./sakila/city.ibd
 [01] ...done
 [01] Streaming ./sakila/country.ibd
 [01] ...done
 [01] Streaming ./sakila/customer.ibd
 [01] ...done
 [01] Streaming ./sakila/film.ibd
 [01] ...done
 [01] Streaming ./sakila/film_actor.ibd
 [01] ...done
 [01] Streaming ./sakila/film_category.ibd
 [01] ...done
 [01] Streaming ./sakila/inventory.ibd
 [01] ...done
 [01] Streaming ./sakila/language.ibd
 [01] ...done
 [01] Streaming ./sakila/payment.ibd
 [01] ...done
 [01] Streaming ./sakila/rental.ibd
 [01] ...done
 [01] Streaming ./sakila/staff.ibd
 [01] ...done
 [01] Streaming ./sakila/store.ibd
 [01] ...done
 >> log scanned up to (8443459)
 130723 05:20:08 innobackupex: Continuing after ibbackup has suspended
 130723 05:20:08 innobackupex: Starting to lock all tables...
 tar: -: Cannot write: Broken pipe
 tar: Error is not recoverable: exiting now
 innobackupex: Error: Failed to stream 'xtrabackup_binlog_info': Inappropriate ioctl for device at /usr/sbin/innobackupex line 413.

It looks like an EOF is being sent somewhere in between there which closes the socat on other end causing EPIPE later on.