IntroductionInstallationFrequently asked questionsConfiguration valuesCreating Docker images
IntroductionSpecial-case installationsInstaller optionsServer topology best practicesDefault installation directories
IntroductionDefault configurationCustom configurationExpress agentExpress agent-onlyAdvanced agent-onlyCloudBees Analytics server
IntroductionExpress serverAdvanced serverExpress agentExpress agent-only (standalone)Advanced agent-only (standalone)CloudBees Analytics server installation
IntroductionSilent install overviewSilent install argumentsLinux installation examplesWindows installation examplesLinux repository server installation exampleWindows repository server installation exampleWindows or Linux CloudBees Analytics server installation example
IntroductionUNIX agent interactive command-lineUNIX agent unattended
IntroductionPrerequisitesPermissionsInstalling via the web interfaceInstalling via the API
Moving the artifact repository in Linux
Moving the artifact repository in Windows
Connecting CloudBees CD/RO to a Microsoft SQL server
Installing the MySQL JDBC driver
IntroductionUninstalling CloudBees CD/RO on Linux, Unix, or macOSUninstalling CloudBees CD/RO on WindowsUninstalling the CloudBees Analytics Server on LinuxUninstalling the CloudBees Analytics Server on Windows
Signing in to CloudBees CD/RO
Introduction
Microservice applications
IntroductionArtifact stagingSnapshotsRollbackManaging dependencies
IntroductionApplications and processesCreating processesAdding process stepsProcess branchingPlugin process stepsManual steps and tasksExample: manual step with runtime parameters
IntroductionCreating environmentsCreating environment tier mapsInventory trackingEnvironment inventoryEnvironment reservationsEnvironment lockingModeling dynamic environmentsAutomated environment discoveryExample: dynamic environment with Amazon and Chef
IntroductionMaster Component ExamplesMaster components list
IntroductionApplication deploy optionsDeploying and troubleshooting applicationsDeployment packagesDeployment examplesDeploying applications with provisioned cloud resourcesExample: implementing deployment strategies
Property reference use case
Creating a project
Parameters
Full-stack dependency view
Configuration drift
Attaching credentials to processes
Developer task: creating custom plugins
Introduction
Release and Environment Reservations Calendar
Visibility and Status of Release Pipelines
Release Definition
Release Dashboard
Planned Versus Actual View
Path to Production View
Release Summary
IntroductionPipeline concepts
Pipeline stages and gates
Pipeline access control
Pipeline tasks
Entry and exit gates
Pipeline conditions
Pipeline start and end stages and stage skipping
Wait dependencies
Native CI integration
Event-based triggers
IntroductionAuthoring and running pipelines
Defining gate approvals
Pipeline objects and conditions
Pipeline stage summary
Credentials in pipelines
IntroductionPipeline examples
Example: Creating a manual task in a pipeline
Example: plugin pipeline tasks
Example: integrating test automation in release pipelines
Example: leveraging test data management and service virtualization in release pipelines
Example: Surfacing Jenkins build details in Flow
Signing in to CloudBees CD/RO
Guided Tutorials
Home page
Personas
Access control
My work dashboard
Object list layout
Object schedules
Event-based triggers
IntroductionPaginationSearching and filteringHierarchy menuProperty browserProjects in CloudBees CD/ROObject tags
IntroductionCleanupStalledJobClusterInfoTooleccertecconfigureecdaemonecproxyecremotefilecopyZKConfigtool
IntroductionThe default zone and gateways to remote zonesSetting agent environment variablesLicensesExternal Database ConfigurationConfiguring CloudBees CD/RO to Use an Alternate DatabaseConfiguring autostart for non-root/non-sudo Linux installationsUniversal access to the plugins directoryEnvironment proxy server configurationSystem health monitoringIncreasing file descriptors on LinuxAdjusting swappiness on LinuxSetting variables on Windows agent machinesConfiguring Kibana to work with CloudBees AnalyticsServer settings
Data Retention
IntroductionPerformance consequences of change trackingEstimating database growthBest practices for change trackingConfiguring change trackingSearching the change historyViewing the change historyModifying what you see in the change historyReverting changes to a tracked object and its tracked contentsExporting a previous state of a tracked object and its tracked contents
IntroductionSetting Email NotificationsSelecting and Editing Email Messages for Application or Microservice Processes
Producing audit reports
Configuration drift
IntroductionCreating configurationsManaging pluginsCreating pluginsManaging the plugin catalog
Self-Service Catalogs
IntroductionArchitecture of a CloudBees CD/RO ClusterResource, agent, and procedure considerationsSoftware for clusteringDependencies for clusteringConfiguring clusteringSeparating agents from flow serversPreparing your cluster resourcesInstalling and configuring a load balancerInstalling ZooKeeperConfiguring a multi-ZooKeeper clusterInstalling CloudBees CD/RO softwareConfiguring repository serversConfiguring machines to operate in clustered modeRunning a cluster in single-server modeAdding the configuration to ZooKeeperUploading configuration files to ZooKeeperGetting Information on the CloudBees CD/RO server cluster from ZooKeeperAdding a node to an existing clusterConfiguring web server propertiesConfiguring repository server propertiesConfiguring CloudBees CD/RO agentsConfiguring the cluster workspaceConfiguring CloudBees CD/RO repositoriesAdding trusted agents to clustersVerifying CloudBees CD/RO servicesAccessing CloudBees CD/RO with clusteringHealth check for the CloudBees CD/RO clusterAdditional Ways to improve a clusterInstalling the CloudBees Analytics server in cluster modeDisaster recovery
Introduction
Build-test automation
IntroductionScenario 1 - Creating a simple procedureScenario 2 - Creating a procedure that uses an SCMScenario 3 - Notification, scheduling, and reportingScenario 4 - Multi-agent build and test
IntroductionAutomation platform home pageCustomizing the automation platform UIConfiguring CloudBees CD/ROUsing CloudBees CD/RO in your environmentCloudBees CD/RO Installed tools
IntroductionArtifact managementAuthenticating users for ldap and active directoryAuto-discoveryDefect trackingElectricSentryJob step execution environmentPreflight buildsPostprocessorsReportsWorkflow overviewWorkspaces and disk space management
IntroductionIntrinsic propertiesProperty shortcutsProperty error codes
IntroductionAdding a link to a jobCalling a subprocedureChecking the outcome of preceding stepsConditional executionCustom parameter layoutsEmail notificationsExecuting tasks on all resources in a poolFactory proceduresPostp extensionPublishing and retrieving an artifactReserving a resource for the job step durationRunning steps in parallelStep timeouts and steps that always runStoring and retrieving properties in a jobWorking with properties stored in a procedure
Using special characters in object names
IntroductionDefining entriesCreate new or edit existing privileges
IntroductionArtifact detailsCreate new or edit existing artifactsArtifact versionsArtifact version detailsEdit an existing artifact versionRepositoriesCreate new or edit existing repositories
Database configuration
IntroductionCreate new or edit existing configurationsDefect tracking reports
IntroductionCreate new or edit existing email configurationsEmail notifiers
Event log
IntroductionJob configurationShortcutsJobs quick view
IntroductionJob step details
IntroductionView licenseImport license
IntroductionCreate new or edit existing procedureCreate new or edit existing stepsPublish artifact version stepsRetrieve artifact version stepsSend email stepsExtract preflight sources stepsCreate new or edit existing parameters
IntroductionCreate new or edit existing projectsProject detailsRun proceduresCreate new or edit existing schedulesCreate new or edit existing credentials
IntroductionNested Property Sheet
Reports
IntroductionResource poolsCreate new or edit existing poolsResource pool detailsZonesGateways
IntroductionSearch results
IntroductionEdit existing property settings
IntroductionCreate new or edit existing configurations
IntroductionUsersCreate new or edit existing local usersUser detailsEdit user settingsGroupsCreate new or edit existing groupsGroup detailsDirectory providersCreate new or edit existing directory providersSingle sign-onTest directory provider
IntroductionCreate new or edit exiting workflow definitionsWorkflow definition detailsRun workflowWorkflow detailsWorkflow logTransition workflow
IntroductionCreate new or edit existing workspacesWorkspace file

Configuring autostart services for Linux installations

7 minute readReference

Linux installations that you perform as a non-root user or without sudo permissions cannot automatically start the CloudBees CD/RO 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 CD/RO components as follows:

Setting Up Autostart Services

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

    <install_dir> is /opt/cloudbees/sda 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'
      ▼

  2. 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 CD/RO Web Server Services

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

    <install_dir> is /opt/cloudbees/sda 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'
      ▼

  2. 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-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 CD/RO Repository Server Services

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

    <install_dir> is /opt/cloudbees/sda 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'
      ▼

  2. 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-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 CD/RO Built-In Database Server Services

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

    <install_dir> is /opt/cloudbees/sda 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'

  1. 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-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 CD/RO Agent Services

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

    <install_dir> is /opt/cloudbees/sda 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'
      ▼

  2. 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-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 Analytics Server Services

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

Setting Up Autostart for Elasticsearch

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

    <install_dir> is /opt/cloudbees/sda 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'

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

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

    <install_dir> is /opt/cloudbees/sda 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'
      ▼

  2. 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-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 CD/RO components as follows:

Disabling Autostart for CloudBees CD/RO 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 CD/RO 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 CD/RO 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 CD/RO 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 CD/RO 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 Analytics Server Services

CloudBees Analytics 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.

Configuring CloudBees CD/RO to Use an Alternate Database
Universal access to the plugins directory