Skip to main content
Common Reference

The deployall Command

The deployall tool installs the required startup scripts into the correct location so that all required services can be automatically started and stopped during the startup and shutdown of your server.

To use, the tool should be executed with superuser privileges, either directly using sudo, or by logging in as the superuser and running the command directly.

The script will automatically detect the initialization system in use (systemd or initd) and prefer systemd when both are available.

shell> sudo deployall
important

In order for the configuration to persist during future updates, and/or to execute the deployall script at install time, you should add the install=true tpm option to your configuration.

The startup scripts are added to the correct run levels to enable operation during standard startup and shutdown levels.

For systemd configurations only

For continuity of service reasons, the deployall script will NOT restart individual components if they had already been previously started by other methods. It will only install systemd scripts. This implies that, right after a call to deployall and before host/component restart, the system will stay in a mixed mode where systemd scripts are in place but components that were started without systemd, won’t be controllable by it.

In order to align the configuration, you will need to run

shell> [component] stop sysd
shell> sudo systemctl start t[component]

Where component is one of replicator,manager or connector, for example:

shell> replicator stop sysd
shell> sudo systemctl start treplicator
From version 8.0.0

From version 8.0.0 as part of the configuration, the systemd script will automatically configure the replicator (and manager in Tungsten Cluster deployments) to get a higher CPU priority (-9 nice value). This will help to avoid monitoring and processing pauses during high CPU usage periods.

For all version up to and including 7.0.2

When a service is controlled by systemd, the relevant OS limits (such as open file limits) are not controlled in the normal way (via settings in the limits.conf file) and therefore for clusters and standalone replicators with heavy workloads there is a risk that you may experience open file limits being exceeded which will affect the operations.

To resolve this, you must ensure you increase the limits for each service. Follow the steps below to do this:

  • Edit the service files in /etc/systemd/system. There will be one file for each service, for example treplicator.service
  • Under the [service] stanza, add the following:
LimitNOFILE=65535
  • When you have changed all the files, reload the systemctl by issuing the following:
shell> systemctl daemon-reload
  • Restart each of the services, e.g:
shell> systemctl restart treplicator

Note that the restart will cause a momentary outage to each component therefore only do this when you are sure it is safe to do so, and if running Tungsten Clustering, ensure you place the cluster in MAINTENANCE mode first, and return to AUTOMATIC when complete.

The workaround mentioned above is included as default from v7.0.3 onwards.

Also see:

To remove the scripts from the system, use undeployall.