Signal18 provides signed package repositories for Debian/Ubuntu and CentOS/RHEL. Package installations deploy binaries, configuration templates, and static assets to standard system paths.
Upgrading from 2.x? Version 3.x introduced configuration file location changes and parameter renames. See the Migration Guide before upgrading.
cat > /etc/yum.repos.d/signal18.repo <<'EOF'
[signal18]
name=Signal18 repositories
baseurl=http://repo.signal18.io/centos/${releasever}/${basearch}/3.1/
gpgcheck=0
enabled=1
EOF
yum install replication-manager-osc
Replace replication-manager-osc with your chosen flavor (replication-manager-pro, replication-manager-arb).
If you encounter this error when upgrading from 2.x:
file /usr/bin/replication-manager-cli from install of replication-manager-client-3.1.xx-1.x86_64
conflicts with file from package replication-manager-pro-1730721861:2.3.53-1.x86_64
This is caused by an epoch removed in 3.x packages. Resolve it as follows:
/var/lib/replication-manager/ and /etc/replication-manager/yum remove replication-manager-pro replication-manager-osc replication-manager-clientdnf clean metadata --disablerepo="*" --enablerepo=signal18# Set version
version="3.1"
# Import GPG signing key
gpg --recv-keys --keyserver keyserver.ubuntu.com FAE20E50
gpg --export FAE20E50 > /etc/apt/trusted.gpg.d/signal18.gpg
# Add repository
echo "deb [signed-by=/etc/apt/trusted.gpg.d/signal18.gpg] http://repo.signal18.io/deb $(lsb_release -sc) $version" \
> /etc/apt/sources.list.d/signal18.list
# Install
apt-get update
apt-get install replication-manager-osc
Replace replication-manager-osc with your chosen flavor (replication-manager-pro, replication-manager-arb).
After package installation:
/etc/replication-manager/config.toml/etc/replication-manager/cluster.d//usr/share/replication-manager//var/lib/replication-manager//var/log/replication-manager.logEnable and start the service:
systemctl enable --now replication-manager
Proceed to Configuration to set up your first cluster.