By default, Tungsten Clustering does not start automatically on boot. To enable
Tungsten Clustering to start at boot time, use the deployall
script provided in the installation directory to create the necessary boot
scripts, or include install=true within
your configuration prior to installation.
If you are using systemctl to manage your startup scripts
and you have selinux enabled, you will also need to execute the following
commands to ensure components start correctly:
sudo semanage fcontext -a -t bin_t "/opt/continuent(/.*)?" sudo restorecon -r -v /opt/continuent
If you have installed the software in an alternative directory, adjust the paths in the exmaple above accordingly
To disable automatic startup at boot time, use the undeployall command:
shell> undeployallThis section applies to version 7.1 onwards, for earlier versions, see Configuring Multi-Site/Active-Active Replicator Startup on Boot
The easiest and safest method to ensure the cross-site services are also
handled by systemctl (or equivalent) is to ensure the tpm flag
install=true is set within the
[defaults] stanza of your /etc/tungsten/tungsten.ini
file prior to installation.
If this isn't set and you wish to configure the services post-installation, then execute the deployall script from the Cross-Site replicator install path, for example:
shell>cd /opt/replicator/tungsten/cluster-home/binshell>./deployall
If the replicator where already running, then issue:
shell>mm_replicator stop sysdshell>sudo systemctl start mm_treplicator
Examples above assume install-path was set to
/opt/replicator and executable-prefix
was set to mm