Configuring autostart services for Linux installations

Linux installations that you perform as a non-root user or without sudo permissions cannot automatically start the CloudBees Flow server, web server, repository server, or agents. This means that you must set up service autostart after installation is complete. This section describes how to set up autostart and also how to disable it if needed.

Setting up autostart

This section describes how to set up autostart of services for all CloudBees Flow components as follows:

Setting Up Autostart Services

Provide a service control script in the /etc/init.d directory by using one of the following methods.

<install_dir> is /opt/Electric Cloud/ElectricCommander by default.
- Secure (preferred) method:
  
  `$ sudo cp -v <install_dir>/startup/commanderServer /etc/init.d/ef-user-server `
  
  `‘<install_dir>/startup/commanderServer’ → ‘/etc/init.d/ef-user-server’ `
  
  `$ sudo chown -v root:root /etc/init.d/ef-user-server `
  
  `ownership of ‘/etc/init.d/ef-user-server’ retained as root:root `
  
  `$ sudo chmod -v 0755 /etc/init.d/ef-user-server `
  
  mode of ‘/etc/init.d/ef-user-server’ retained as 0755 (rwxr-xr-x)
- Less secure (alternative) method:
  
  `$ sudo ln -sv <install_dir>/startup/commanderServer /etc/init.d/ef-user-server `
  
  '/etc/init.d/ef-user-server' → '<install_dir>/startup/commanderServer'

Create links in the “rc” directories.

The exact commands as well as the prompts displayed in response will vary with the specific distribution. Following are several examples: ** RHEL 5. x , 6. x , or 7. x ; CentOS 5. x , 6. x , or 7. x ; SLES 11 or 12:

$ sudo /sbin/chkconfig --add ef-user-server
$ sudo /sbin/chkconfig ef-user-server on▼

Ubuntu 14. x , 16. x , or 18. x :

$ sudo /usr/sbin/update-rc.d ef-user-server defaults▼

Adding system startup for /etc/init.d/ef-user-server ...
/etc/rc0.d/K20ef-user-server -> ../init.d/ef-user-server
/etc/rc1.d/K20ef-user-server -> ../init.d/ef-user-server
/etc/rc6.d/K20ef-user-server -> ../init.d/ef-user-server
/etc/rc2.d/S20ef-user-server -> ../init.d/ef-user-server
/etc/rc3.d/S20ef-user-server -> ../init.d/ef-user-server
/etc/rc4.d/S20ef-user-server -> ../init.d/ef-user-server
/etc/rc5.d/S20ef-user-server -> ../init.d/ef-user-server▼

Setting Up Autostart for CloudBees Flow Web Server Services

Provide a service control script in the /etc/init.d directory by using one of the following methods.

<install_dir> is /opt/Electric Cloud/ElectricCommander by default.
- Secure (preferred) method:
  
  `$ sudo cp -v <install_dir>/startup/commanderApache /etc/init.d/ef-user-apache `
  
  `‘<install_dir>/startup/commanderApache’ → ‘/etc/init.d/ef-user-apache’ `
  
  `$ sudo chown -v root:root /etc/init.d/ef-user-apache `
  
  `ownership of ‘/etc/init.d/ef-user-apache’ retained as root:root `
  
  `$ sudo chmod -v 0755 /etc/init.d/ef-user-apache `
  
  mode of ‘/etc/init.d/ef-user-apache’ retained as 0755 (rwxr-xr-x)
- Less secure (alternative) method:
  
  `$ sudo ln -sv <install_dir>/startup/commanderApache /etc/init.d/ef-user-apache `
  
  '/etc/init.d/ef-user-apache' → '<install_dir>/startup/commanderApache'

Create links in the “rc” directories.

$ sudo /sbin/chkconfig --add ef-user-apache
$ sudo /sbin/chkconfig ef-user-apache on▼

Ubuntu 14. x , 16. x , or 18. x :

$ sudo /usr/sbin/update-rc.d ef-user-apache defaults▼

Adding system startup for /etc/init.d/ef-user-apache ...
/etc/rc0.d/K20ef-user-apache -> ../init.d/ef-user-apache
/etc/rc1.d/K20ef-user-apache -> ../init.d/ef-user-apache
/etc/rc6.d/K20ef-user-apache -> ../init.d/ef-user-apache
/etc/rc2.d/S20ef-user-apache -> ../init.d/ef-user-apache
/etc/rc3.d/S20ef-user-apache -> ../init.d/ef-user-apache
/etc/rc4.d/S20ef-user-apache -> ../init.d/ef-user-apache
/etc/rc5.d/S20ef-user-apache -> ../init.d/ef-user-apache▼

Setting Up Autostart for CloudBees Flow Repository Server Services

Provide a service control script in the /etc/init.d directory by using one of the following methods.

<install_dir> is /opt/Electric Cloud/ElectricCommander by default.
- Secure (preferred) method:
  
  `$ sudo cp -v <install_dir>/startup/commanderRepository /etc/init.d/ef-user-repository `
  
  `‘<install_dir>/startup/commanderRepository’ → ‘/etc/init.d/ef-user-repository’ `
  
  `$ sudo chown -v root:root /etc/init.d/ef-user-repository `
  
  `ownership of ‘/etc/init.d/ef-user-repository’ retained as root:root `
  
  `$ sudo chmod -v 0755 /etc/init.d/ef-user-repository `
  
  mode of ‘/etc/init.d/ef-user-repository’ retained as 0755 (rwxr-xr-x)
- Less secure (alternative) method:
  
  `$ sudo ln -sv <install_dir>/startup/commanderRepository /etc/init.d/ef-user-repository `
  
  '/etc/init.d/ef-user-repository' → '<install_dir>/startup/commanderRepository'

Create links in the “rc” directories.

$ sudo /sbin/chkconfig --add ef-user-repository
$ sudo /sbin/chkconfig ef-user-repository on▼

Ubuntu 14. x , 16. x , or 18. x :

$ sudo /usr/sbin/update-rc.d ef-user-repository defaults▼

Adding system startup for /etc/init.d/ef-user-repository ...
/etc/rc0.d/K20ef-user-repository -> ../init.d/ef-user-repository
/etc/rc1.d/K20ef-user-repository -> ../init.d/ef-user-repository
/etc/rc6.d/K20ef-user-repository -> ../init.d/ef-user-repository
/etc/rc2.d/S20ef-user-repository -> ../init.d/ef-user-repository
/etc/rc3.d/S20ef-user-repository -> ../init.d/ef-user-repository
/etc/rc4.d/S20ef-user-repository -> ../init.d/ef-user-repository
/etc/rc5.d/S20ef-user-repository -> ../init.d/ef-user-repository▼

Setting Up Autostart for CloudBees Flow Built-In Database Server Services

Provide a service control script in the /etc/init.d directory by using one of the following methods.

<install_dir> is /opt/Electric Cloud/ElectricCommander by default.
- Secure (preferred) method:
  
  `$ sudo cp -v <install_dir>/startup/commanderDatabase /etc/init.d/ef-user-database `
  
  `‘<install_dir>/startup/commanderDatabase’ → ‘/etc/init.d/ef-user-database’ `
  
  `$ sudo chown -v root:root /etc/init.d/ef-user-database `
  
  `ownership of ‘/etc/init.d/ef-user-database’ retained as root:root `
  
  `$ sudo chmod -v 0755 /etc/init.d/ef-user-database `
  
  mode of ‘/etc/init.d/ef-user-database’ retained as 0755 (rwxr-xr-x)
- Less secure (alternative) method:
  
  `$ sudo ln -sv <install_dir>/startup/commanderDatabase /etc/init.d/ef-user-database `
  
  '/etc/init.d/ef-user-database' → '<install_dir>/startup/commanderDatabase'

Create links in the “rc” directories.

$ sudo /sbin/chkconfig --add ef-user-database
$ sudo /sbin/chkconfig ef-user-database on▼

Ubuntu 14. x , 16. x , or 18. x :

$ sudo /usr/sbin/update-rc.d ef-user-database defaults▼

Adding system startup for /etc/init.d/ef-user-database ...
/etc/rc0.d/K20ef-user-database -> ../init.d/ef-user-database
/etc/rc1.d/K20ef-user-database -> ../init.d/ef-user-database
/etc/rc6.d/K20ef-user-database -> ../init.d/ef-user-database
/etc/rc2.d/S20ef-user-database -> ../init.d/ef-user-database
/etc/rc3.d/S20ef-user-database -> ../init.d/ef-user-database
/etc/rc4.d/S20ef-user-database -> ../init.d/ef-user-database
/etc/rc5.d/S20ef-user-database -> ../init.d/ef-user-database▼

Setting Up Autostart for CloudBees Flow Agent Services

Provide a service control script in the /etc/init.d directory by using one of the following methods.

<install_dir> is /opt/Electric Cloud/ElectricCommander by default.
- Secure (preferred) method:
  
  `$ sudo cp -v <install_dir>/startup/commanderAgent /etc/init.d/ef-user-agent `
  
  `‘<install_dir>/startup/commanderAgent’ → ‘/etc/init.d/ef-user-agent’ `
  
  `$ sudo chown -v root:root /etc/init.d/ef-user-agent `
  
  `ownership of ‘/etc/init.d/ef-user-agent’ retained as root:root `
  
  `$ sudo chmod -v 0755 /etc/init.d/ef-user-agent `
  
  mode of ‘/etc/init.d/ef-user-agent’ retained as 0755 (rwxr-xr-x)
- Less secure (alternative) method:
  
  `$ sudo ln -sv <install_dir>/startup/commanderAgent /etc/init.d/ef-user-agent `
  
  '/etc/init.d/ef-user-agent' → '<install_dir>/startup/commanderAgent'

Create links in the “rc” directories.

$ sudo /sbin/chkconfig --add ef-user-agent
$ sudo /sbin/chkconfig ef-user-agent on▼

Ubuntu 14. x , 16. x , or 18. x :

$ sudo /usr/sbin/update-rc.d ef-user-agent defaults▼

Adding system startup for /etc/init.d/ef-user-agent ...
/etc/rc0.d/K20ef-user-agent -> ../init.d/ef-user-agent
/etc/rc1.d/K20ef-user-agent -> ../init.d/ef-user-agent
/etc/rc6.d/K20ef-user-agent -> ../init.d/ef-user-agent
/etc/rc2.d/S20ef-user-agent -> ../init.d/ef-user-agent
/etc/rc3.d/S20ef-user-agent -> ../init.d/ef-user-agent
/etc/rc4.d/S20ef-user-agent -> ../init.d/ef-user-agent
/etc/rc5.d/S20ef-user-agent -> ../init.d/ef-user-agent▼

Setting Up Autostart for CloudBees Flow DevOps Insight Server Services

DevOps Insight requires autostart for two services: Elasticsearch and Logstash. The DevOps Insight server uses the Elasticsearch search engine and the Logstash data-collection and log-parsing engine to gather data from the CloudBees Flow server for use in the DevOps Insight dashboards such as the Deployments, Releases, and Release Command Center dashboards.

Setting Up Autostart for Elasticsearch

Provide a service control script in the /etc/init.d directory by using one of the following methods.

<install_dir> is /opt/Electric Cloud/ElectricCommander by default.
- Secure (preferred) method
  
  $ sudo cp -v <install_dir>/reporting/startup/commanderElasticsearch /etc/init.d/ef-user-elasticsearch
  
  `‘<install_dir>/reporting/startup/commanderElasticsearch’ → ‘/etc/init.d/ef-user-elasticsearch’ `
  
  `$ sudo chown -v root:root /etc/init.d/ef-user-elasticsearch `
  
  `ownership of ‘/etc/init.d/ef-user-elasticsearch’ retained as root:root `
  
  `$ sudo chmod -v 0755 /etc/init.d/ef-user-elasticsearch `
  
  mode of ‘/etc/init.d/ef-user-elasticsearch’ retained as 0755 (rwxr-xr-x)
- Less secure (alternative) method:
  
  `$ sudo ln -sv <install_dir>/reporting/startup/commanderElasticsearch /etc/init.d/ef-user-elasticsearch `
  
  '/etc/init.d/ef-user-elasticsearch' → '<install_dir>/reporting/startup/commanderElasticsearch'

Create links in the “rc” directories.

$ sudo /sbin/chkconfig --add ef-user-elasticsearch
$ sudo /sbin/chkconfig ef-user-elasticsearch on▼

Ubuntu 14. x , 16. x , or 18. x :

$ sudo /usr/sbin/update-rc.d ef-user-elasticsearch defaults▼

Adding system startup for /etc/init.d/ef-user-elasticsearch ...
/etc/rc0.d/K20ef-user-elasticsearch -> ../init.d/ef-user-elasticsearch
/etc/rc1.d/K20ef-user-elasticsearch -> ../init.d/ef-user-elasticsearch
/etc/rc6.d/K20ef-user-elasticsearch -> ../init.d/ef-user-elasticsearch
/etc/rc2.d/S20ef-user-elasticsearch -> ../init.d/ef-user-elasticsearch
/etc/rc3.d/S20ef-user-elasticsearch -> ../init.d/ef-user-elasticsearch
/etc/rc4.d/S20ef-user-elasticsearch -> ../init.d/ef-user-elasticsearch
/etc/rc5.d/S20ef-user-elasticsearch -> ../init.d/ef-user-elasticsearch▼

Setting Up Autostart for Logstash

Provide a service control script in the /etc/init.d directory by using one of the following methods.

<install_dir> is /opt/Electric Cloud/ElectricCommander by default.
- Secure (preferred) method:
  
  $ sudo cp -v <install_dir>/reporting/startup/commanderLogstash /etc/init.d/ef-user-logstash
  
  `‘<install_dir>/reporting/startup/commanderLogstash’ → ‘/etc/init.d/ef-user-logstash’ `
  
  `$ sudo chown -v root:root /etc/init.d/ef-user-logstash `
  
  `ownership of ‘/etc/init.d/ef-user-logstash’ retained as root:root `
  
  `$ sudo chmod -v 0755 /etc/init.d/ef-user-logstash `
  
  mode of ‘/etc/init.d/ef-user-logstash’ retained as 0755 (rwxr-xr-x)
- Less secure (alternative) method:
  
  `$ sudo ln -sv <install_dir>/reporting/startup/commanderLogstash /etc/init.d/ef-user-logstash `
  
  '/etc/init.d/ef-user-logstash' → '<install_dir>/reporting/startup/commanderLogstash'

Create links in the “rc” directories.

$ sudo /sbin/chkconfig --add ef-user-logstash
$ sudo /sbin/chkconfig ef-user-logstash on▼

Ubuntu 14. x , 16. x , or 18. x :

$ sudo /usr/sbin/update-rc.d ef-user-logstash defaults▼

Adding system startup for /etc/init.d/ef-user-logstash ...
/etc/rc0.d/K20ef-user-logstash -> ../init.d/ef-user-logstash
/etc/rc1.d/K20ef-user-logstash -> ../init.d/ef-user-logstash
/etc/rc6.d/K20ef-user-logstash -> ../init.d/ef-user-logstash
/etc/rc2.d/S20ef-user-logstash -> ../init.d/ef-user-logstash
/etc/rc3.d/S20ef-user-logstash -> ../init.d/ef-user-logstash
/etc/rc4.d/S20ef-user-logstash -> ../init.d/ef-user-logstash
/etc/rc5.d/S20ef-user-logstash -> ../init.d/ef-user-logstash▼

Disabling Services Autostart

This section describes how to disable autostart of services for all CloudBees Flow components as follows:

Disabling Autostart for CloudBees Flow Server Services on page 1
Disabling Autostart for CloudBees Flow Web Server Services on page 1
Disabling Autostart for CloudBees Flow Repository Server Services on page 1
Disabling Autostart for CloudBees Flow Built-In Database Server Services on page 1
Disabling Autostart for CloudBees Flow Agent Services on page 1
Disabling Autostart for CloudBees Flow DevOps Insight Server Services on page 1

Disabling Autostart for CloudBees Flow Server Services

Enter the following command:

$ sudo rm -fv /etc/init.d/ef-user-server /etc/rc?.d/*ef-user-server /etc/init.d/rc?.d/*ef-user-server

removed ‘/etc/init.d/ef-user-server’removed ‘/etc/rc0.d/K20ef-user-server’removed ‘/etc/rc1.d/K20ef-user-server’removed ‘/etc/rc2.d/S20ef-user-server’removed ‘/etc/rc3.d/S20ef-user-server’removed ‘/etc/rc4.d/S20ef-user-server’removed ‘/etc/rc5.d/S20ef-user-server’removed ‘/etc/rc6.d/K20ef-user-server’

The prompts displayed in response to these commands might vary with the specific distribution and version.

Disabling Autostart for CloudBees Flow Web Server Services

Enter the following command:

$ sudo rm -fv /etc/init.d/ef-user-apache /etc/rc?.d/*ef-user-apache /etc/init.d/rc?.d/*ef-user-apache

removed ‘/etc/init.d/ef-user-apache’removed ‘/etc/rc0.d/K20ef-user-apache’removed ‘/etc/rc1.d/K20ef-user-apache’removed ‘/etc/rc2.d/S20ef-user-apache’removed ‘/etc/rc3.d/S20ef-user-apache’removed ‘/etc/rc4.d/S20ef-user-apache’removed ‘/etc/rc5.d/S20ef-user-apache’removed ‘/etc/rc6.d/K20ef-user-apache’

The prompts displayed in response to these commands might vary with the specific distribution and version.

Disabling Autostart for CloudBees Flow Repository Server Services

Enter the following command:

$ sudo rm -fv /etc/init.d/ef-user-repository /etc/rc?.d/*ef-user-repository /etc/init.d/rc?.d/*ef-user-repository

removed ‘/etc/init.d/ef-user-repository’removed ‘/etc/rc0.d/K20ef-user-repository’removed ‘/etc/rc1.d/K20ef-user-repository’removed ‘/etc/rc2.d/S20ef-user-repository’removed ‘/etc/rc3.d/S20ef-user-repository’removed ‘/etc/rc4.d/S20ef-user-repository’removed ‘/etc/rc5.d/S20ef-user-repository’removed ‘/etc/rc6.d/K20ef-user-repository’

The prompts displayed in response to these commands might vary with the specific distribution and version.

Disabling Autostart for CloudBees Flow Built-In Database Server Services

Enter the following command:

$ sudo rm -fv /etc/init.d/ef-user-database /etc/rc?.d/*ef-user-database /etc/init.d/rc?.d/*ef-user-database

removed ‘/etc/init.d/ef-user-database’removed ‘/etc/rc0.d/K20ef-user-database’removed ‘/etc/rc1.d/K20ef-user-database’removed ‘/etc/rc2.d/S20ef-user-database’removed ‘/etc/rc3.d/S20ef-user-database’removed ‘/etc/rc4.d/S20ef-user-database’removed ‘/etc/rc5.d/S20ef-user-database’removed ‘/etc/rc6.d/K20ef-user-database’

The prompts displayed in response to these commands might vary with the specific distribution and version.

Disabling Autostart for CloudBees Flow Agent Services

Enter the following command:

$ sudo rm -fv /etc/init.d/ef-user-agent /etc/rc?.d/*ef-user-agent /etc/init.d/rc?.d/*ef-user-agent

removed ‘/etc/init.d/ef-user-agent’removed ‘/etc/rc0.d/K20ef-user-agent’removed ‘/etc/rc1.d/K20ef-user-agent’removed ‘/etc/rc2.d/S20ef-user-agent’removed ‘/etc/rc3.d/S20ef-user-agent’removed ‘/etc/rc4.d/S20ef-user-agent’removed ‘/etc/rc5.d/S20ef-user-agent’removed ‘/etc/rc6.d/K20ef-user-agent’

The prompts displayed in response to these commands might vary with the specific distribution and version.

Disabling Autostart for CloudBees Flow DevOps Insight Server Services

DevOps Insight requires that you disable autostart for two services: Elasticsearch and Logstash.

Disabling Autostart for Elasticsearch

$ sudo rm -fv /etc/init.d/ef-user-elasticsearch /etc/rc?.d/*ef-user-elasticsearch /etc/init.d/rc?.d/*ef-user-elasticsearch

removed ‘/etc/init.d/ef-user-elasticsearch’removed ‘/etc/rc0.d/K20ef-user-elasticsearch’removed ‘/etc/rc1.d/K20ef-user-elasticsearch’removed ‘/etc/rc2.d/S20ef-user-elasticsearch’removed ‘/etc/rc3.d/S20ef-user-elasticsearch’removed ‘/etc/rc4.d/S20ef-user-elasticsearch’removed ‘/etc/rc5.d/S20ef-user-elasticsearch’removed ‘/etc/rc6.d/K20ef-user-elasticsearch’

The prompts displayed in response to these commands might vary with the specific distribution and version.

Disabling Autostart for Logstash

$ sudo rm -fv /etc/init.d/ef-user-logstash /etc/rc?.d/*ef-user-logstash /etc/init.d/rc?.d/*ef-user-logstash

removed ‘/etc/init.d/ef-user-logstash’removed ‘/etc/rc0.d/K20ef-user-logstash’removed ‘/etc/rc1.d/K20ef-user-logstash’removed ‘/etc/rc2.d/S20ef-user-logstash’removed ‘/etc/rc3.d/S20ef-user-logstash’removed ‘/etc/rc4.d/S20ef-user-logstash’removed ‘/etc/rc5.d/S20ef-user-logstash’removed ‘/etc/rc6.d/K20ef-user-logstash’

The prompts displayed in response to these commands might vary with the specific distribution and version.