In this blog post, we talk about how to configure automatic start at boot time for the Tungsten Clustering components.
By default, Tungsten Clustering does not start automatically on boot. To enable Tungsten Clustering to start at boot time, use the
deployall script provided to create the necessary boot scripts:
shell> sudo /opt/continuent/tungsten/cluster-home/bin/deployall
To disable automatic startup at boot time, use the
shell> sudo /opt/continuent/tungsten/cluster-home/bin/undeployall
For Multisite/Multimaster deployments in specific, there are separate cross-site replicators running. In this case, 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/mmreplicator
- Stop 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/mmreplicator stop
- Modify the APP_NAME variable within the startup script (/etc/init.d/mmreplicator) to mmreplicator:
- Start the Tungsten Replicator process.
shell> /etc/init.d/mmreplicator start
- Update the operating system startup configuration to use the updated script.On Debian/Ubuntu:
shell> sudo update-rc.d mmreplicator defaults
shell> sudo chkconfig --add mmreplicator
In future articles, we will continue to cover more advanced subjects of interest!
Questions? Contact Continuent