can't add second node to cluster MAriaDB 10.1

HI. I want make cluster 3 node SST wsrep_sst_method = xtrabackup-v2
(MariaDB 10.1, xtrabackup version 2.2.13 try 2.3 and 2.4 same result, Ubuntu 14.04)
my.cnf

[galera]
wsrep_provider=/usr/lib/galera/libgalera_smm.so
query_cache_size=0
binlog_format=ROW
default-storage-engine=innodb
innodb_autoinc_lock_mode=2
query_cache_type=0
bind-address=0.0.0.0
innodb_log_file_size=100M
innodb_file_per_table
innodb_flush_log_at_trx_commit=2
open_files_limit = 10240
wsrep_provider=/usr/lib/galera/libgalera_smm.so
wsrep_provider_options=“gcache.size=32G”
wsrep_cluster_name=“galera_cluster”
wsrep_cluster_address=“gcomm://ip1,ip2,ip3”
wsrep_sst_method = xtrabackup-v2
wsrep_sst_auth=login:pass
wsrep_node_address=“ip1”
wsrep_node_name=“db1”
wsrep_on=ON

On first node run mariadb: service mysql start --wsrep_new_cluster
On second node run: service mysql start
But after sync DB’s I have error on second node

May 29 16:29:36 mariadb2 mysqld: 2016-05-29 16:29:36 139681434408896 [ERROR] Binlog file ‘/var/log/mysql/mariadb-bin.006314’ not found in binlog index, needed for recovery. Aborting.
May 29 16:29:36 mariadb2 mysqld: 2016-05-29 16:29:36 139681434408896 [ERROR] Crash recovery failed. Either correct the problem (if it’s, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}
May 29 16:29:36 mariadb2 mysqld: 2016-05-29 16:29:36 139681434408896 [ERROR] Can’t init tc log
May 29 16:29:36 mariadb2 mysqld: 2016-05-29 16:29:36 139681434408896 [ERROR] Aborting

I try copy ​mariadb-bin.006314 from first node to second server (/var/log/mysql/)
Then start mariadb: service mysql start
and have error:

May 29 16:44:55 mariadb2 mysqld_safe: WSREP: Failed to recover position: ‘2016-05-29 16:44:52 140598846638016 [Note] InnoDB: Using mutexes to ref count buffer pool pages#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: The InnoDB memory heap is disabled#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Memory barrier is not used#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Compressed tables use zlib 1.2.8#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Using Linux native AIO#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Using generic crc32 instructions#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Initializing buffer pool, size = 8.0G#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Completed initialization of buffer pool#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Highest supported file format is Barracuda.#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: 128 rollback segment(s) are active.#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Waiting for purge to start#0122016-05-29 16:44:52 140598846638016 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.29-76.2 started; log sequence number 1053141849055#0122016-05-29 16:44:52 140598846638016 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery.#0122016-05-29 16:44:52 140598846638016 [Note] Plugin ‘FEEDBACK’ is disabled.#0122016-05-29 16:44:52 140598846638016 [Note] Recovering after a crash using /var/log/mysql/mariadb-bin#0122016-05-29 16:44:52 140598846638016 [ERROR] Binlog file ‘/var/log/mysql/mariadb-bin.006314’ not found in binlog index, needed for recovery. Aborting.#0122016-05-29 16:44:52 140598846638016 [ERROR] Crash recovery failed. Either correct the problem (if it’s, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}#0122016-05-29 16:44:52 140598846638016 [ERROR] Can’t init tc log#0122016-05-29 16:44:52 140598846638016 [ERROR] Aborting’

Please help…

try renaming /var/lib/mysql
then create a new /var/lib/mysql owned by mysql.mysql