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> undeployallBecause there is an additional Tungsten Replicator running, each must be individually configured to startup on boot:
For the Tungsten Cluster service, use Section 4.3, “Configuring Startup on Boot”.
For the Tungsten Replicator service, a custom startup script must be created, otherwise the replicator will be unable to start as it has been configured in a different directory.
Create a link from the Tungsten Replicator service startup script in
the operating system startup directory
(/etc/init.d):
shell> sudo ln -s /opt/replicator/tungsten/tungsten-replicator/bin/replicator /etc/init.d/mm_replicatorStop the Tungsten Replicator process. Failure to do this will cause issues because the service will no longer recognize the existing PID file and report it is not running.
shell> /etc/init.d/mm_replicator stop
Modify the APP_NAME variable
within the startup script
(/etc/init.d/mm_replicator)
to mm_replicator:
APP_NAME="mmreplicator"
Start the Tungsten Replicator process.
shell> /etc/init.d/mm_replicator startUpdate the operating system startup configuration to use the updated script.
On Debian/Ubuntu:
shell> sudo update-rc.d mm_replicator defaultsOn RedHat/CentOS:
shell> sudo chkconfig --add mm_replicator