Skip to main content
Tungsten Clustering

Configuring Startup on Boot

By default, Tungsten Cluster does not start automatically on boot. To enable Tungsten Cluster 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.

note

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:

shell> sudo semanage fcontext -a -t bin_t "/opt/continuent(/.*)?"
shell> sudo restorecon -r -v /opt/continuent

If you have installed the software in an alternative directory, adjust the paths in the example above accordingly

To disable automatic startup at boot time, use the undeployall command:

shell> undeployall

Configuring Multi-Site Active/Active Cross-Site Replicator Startup on Boot​

v7.2.0 onwards​

Version availability

These steps are for version from 7.2.0 onwards.

See here for versions prior to 7.2.0

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/bin
shell> ./deployall

If the replicator is already running, then issue:

shell> mm_replicator stop sysd
shell> sudo systemctl start mm_treplicator
note

Examples above assume install-directory was set to /opt/replicator and executable-prefix was set to mm

Version upto v7.1.x​

Version availability

These steps are for all versions upto and including v7.1.x

See here for v7.2.0 onwards

Because there is an additional Tungsten Replicator running, each must be individually configured to startup on boot:

  • For the Tungsten Cluster service, use "deployment-startonboot".
  • 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, see steps below.

  1. 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_replicator

  2. 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/mm_replicator stop

  3. Modify the APP_NAME variable within the startup script (/etc/init.d/mm_replicator) to mm_replicator:

    APP_NAME="mm_replicator"

  4. Start the Tungsten Replicator process.

    shell> /etc/init.d/mm_replicator start

  5. Update the operating system startup configuration to use the updated script.

    On Debian/Ubuntu:

    shell> sudo update-rc.d mm_replicator defaults

    On RedHat/CentOS:

    shell> sudo chkconfig --add mm_replicator