[MDEV-12294] wsrep_sst_rsync: command not found ? Created: 2017-03-17  Updated: 2018-06-01  Resolved: 2018-06-01

Status: Closed
Project: MariaDB Server
Component/s: Galera, Galera SST
Affects Version/s: 10.1.21, 10.1.22
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: none now Assignee: Jan Lindström (Inactive)
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

[galera]

  1. Mandatory settings
    wsrep_on=ON
    wsrep_provider = /usr/lib64/galera/libgalera_smm.so
    wsrep_cluster_name = "maria-cluster"
    wsrep_cluster_address = "gcomm://10.5.6.17,10.5.6.32,10.5.6.100"
    wsrep_node_address = "10.5.6.49"
    wsrep_node_name = "hale"
    wsrep_sst_method = rsync
    log-bin = mariadb.binlog
    binlog_format = row
    default_storage_engine = InnoDB
    innodb_autoinc_lock_mode = 2

wsrep-log-conflicts
wsrep-debug


 Description   

2017-03-17 15:18:34 140487019469568 [Note] WSREP: New cluster view: global state: d208fa07-5344-11e6-b5a4-87184603aed0:27388, view# 463: Primary, number of nodes: 4, my index: 3, protocol version 3
2017-03-17 15:18:34 140487019469568 [Warning] WSREP: Gap in state sequence. Need state transfer.
2017-03-17 15:18:34 140487019469568 [Note] WSREP: Setting wsrep_ready to 0
2017-03-17 15:18:34 140486681556736 [Note] WSREP: Running: 'wsrep_sst_rsync --role 'joiner' --address '10.5.6.49' --datadir '/var/lib/mysql/' --parent '26324' --binlog 'mariadb' '
sh: wsrep_sst_rsync: command not found
2017-03-17 15:18:34 140486681556736 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_rsync --role 'joiner' --address '10.5.6.49' --datadir '/var/lib/mysql/' --parent '26324' --binlog 'mariadb'
Read: '(null)'
2017-03-17 15:18:34 140486681556736 [ERROR] WSREP: Process completed with error: wsrep_sst_rsync --role 'joiner' --address '10.5.6.49' --datadir '/var/lib/mysql/' --parent '26324' --binlog 'mariadb' : 2 (No such file or directory)
2017-03-17 15:18:34 140487019469568 [ERROR] WSREP: Failed to prepare for 'rsync' SST. Unrecoverable.
2017-03-17 15:18:34 140487019469568 [ERROR] Aborting

 Comments   
Comment by none now [ 2017-03-17 ]

guys, you sill have not got your SE rules fixed (Centos 7.x selinux-policy-3.13.1-102.el7_3.15.noarch).
Daemon(s) would not start when these in use:
#log-basename = server
#log-error

Comment by Daniel Black [ 2017-03-19 ]

This is a file not found error and appears related to the the wsrep_sst_rsync script being not found.

Do you have the audit log showing this is a selinux issue? If it is it selinux - this appears to be a duplicate of MDEV-12231 as a result of missing packages on MariaDB's Centos build VMs.

Generated at Thu Feb 08 07:56:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.