Skip to main content

Stop or remove components and servers

Distinguish the actions​

Stop stops a module while retaining its data; Start runs it again. Remove on an eligible module executes a removal plan. Remove this server in Servers deletes the saved panel connection after a confirmation ("Remove … from the list?"; for a scanner node of this server you also type its name); it neither uninstalls DerScanner nor stops remote processes. If DCP manages this node’s access to the queue, removing its entry also closes that access; a running scanner may stop receiving tasks.

Temporarily stop a module​

Select the correct server and module. Let running tasks finish or arrange their interruption. Select Stop, read the confirmation and check the resulting state. To resume service, select Start and check the state and a test task. An SSH connection failure does not mean that the module has stopped.

Remove an optional module​

  1. On the correct server, open the module's Remove action when available. For Builder, use Settings → Optional components.
  2. Read Remove …? and its plan: backup, containers, volumes, files and images to be removed. If needed, select Keep the data of the module (its volumes stay on this server) and wait for the revised plan. Retaining volumes is not an external backup. For Builder, read the separate consequences concerning its service and build directories.
  3. Confirm Remove, wait for the result and check the remaining module set and states. The result says, for example, "SCA is removed from this server; the rest of DerScanner keeps running" and names the backup made before the removal.

Core, required components and modules needed by other installed modules cannot be removed this way. The panel cannot remove SAST, DAST or SCA from a remote scanner node. To take SAST off a node, an administrator runs sudo dcp module remove sast --dry-run on that node, reads the plan, and then runs sudo dcp module remove sast --yes. For any other change of such a node's module set, uninstall its entire installation (below) and install the new set.

Uninstall a complete scanner node​

After preserving the required data, an administrator runs these commands with root privileges on the server being retired. Inspect the plan first:

dcp uninstall --dry-run

Check the server identity: this removes all its DerScanner modules, containers and volumes specified in the plan. To take a backup before proceeding:

dcp uninstall --host HOSTNAME --backup --yes

HOSTNAME is the exact name of the server expected by DCP. Docker remains, and existing backups are retained. After successful uninstallation, remove the connection through Servers → Remove this server and confirm. If the panel could not close the queue port of this server to the removed node, it says so and closes the port at the next start of this server. Deleting the connection first removes the panel's saved management access while leaving the product running.

Recovery​

If the backup fails, resolve data preservation before bypassing it. For partial removal, inspect the result, journal and remaining services before retrying. Recover deleted data using a compatible backup. Adding the server list entry again restores panel connectivity; it does not restore deleted modules or data.