Comment 1 for bug 1647340

I pressed enter a bit too early.

But here is a longer example:

https://gist.github.com/kedazo/32189da227000dd00cadd28512cacde2

Also, to make things worse, this also happens during SST:

WSREP_SST: [INFO] Proceeding with SST (20161205 12:23:30.362)
WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr stdio | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20161205 12:23:30.368)
WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20161205 12:23:30.371)
WSREP_SST: [INFO] Waiting for SST streaming to complete! (20161205 12:23:30.425)
2016-12-05T12:23:31.117606Z 0 [Note] WSREP: (a04e0819, 'tcp://0.0.0.0:4567') turning message relay requesting off
xb_stream_read_chunk(): wrong chunk magic at offset 0x70bdc77.
2016-12-05T12:23:44.247957Z 0 [Note] WSREP: 1.0 (10.10.10.11): State transfer to 0.0 (10.10.10.12) complete.

Maybe there is a new setting that we have forgot to take into account.