KBEC-00237 - How to completely disable the agent on the CloudBees CD (CloudBees Flow) Server

Article ID:360032829292
2 minute readKnowledge base


Your CloudBees CD (CloudBees Flow) server only has CloudBees CD (CloudBees Flow) server running on it and no one should be able to run any steps on the CloudBees CD (CloudBees Flow) Server. No user or admin should be able to on purpose or accidentally consume CloudBees CD (CloudBees Flow) Server resources in an enterprise environment.

The Problem

As distributed, the local agent runs steps on the CloudBees CD (CloudBees Flow) Server, which may effect its performance and memory usage.

Full Solution to move and disable the local agent

  1. In the CloudBees CD (CloudBees Flow) GUI, go to Cloud > Resource.

  2. Find the resource called "local".

  3. Change resource’s "Agent Host Name" to some other resource in your network.

  4. Stop the CloudBees CD (CloudBees Flow) Server resource.

    1. on Linux, from the command-line

       /etc/init.d/commanderAgent Stop
    2. on Windows, use the services panel

  5. Disable the service start on system restart.

    1. on Linux, use chkconfig to disable CloudBees CD (CloudBees Flow) Agent

    2. on Windows, disable the service on restart

Side effects to be aware of

  1. On host enable licenses, the CloudBees CD (CloudBees Flow) Server agent did not count in your host license so disabling this agent has no effect on your agent count.

  2. These changes will not survive an upgrade.

  3. Most CloudBees CD (CloudBees Flow) Servers have a CloudBees CD (CloudBees Flow) Web Server on the same host. Starting with CloudBees CD (CloudBees Flow) 4.2, the agent, local to the Web Server is used to display the log files. If you disable the local agent you must move the Web Server by installing a CloudBees CD (CloudBees Flow) Web Server with CloudBees CD (CloudBees Flow) Agent on another host.