Skip to main content
Version: Deploy 22.1

Shut Down Deploy

Shut down Deploy using the CLI​

If you have administrative permissions, you can shut down the Deploy server using the command-line interface (CLI) command:

deployit.shutdown()

Shut down Deploy using a REST API call​

The following example uses the external curl command, which is available for both Unix-based systems and Microsoft Windows.

note

Replace admin:admin with your own credentials.

curl -X POST --basic -u admin:admin http://admin:admin@localhost:4516/deployit/server/shutdown
note

If you modify any file in the XL_DEPLOY_SERVER_HOME/conf directory, or modify the XL_DEPLOY_SERVER_HOME/ext/synthetic.xml or XL_DEPLOY_SERVER_HOME/ext/xl-rules.xml file, then you must restart the Deploy server for the changes to take effect. For xl-rules.xml. To change the default behavior, see scanning for rules.

Unclean shutdown​

If the server is not shut down cleanly, the next start-up may be slow because Deploy will need to rebuild indexes.

Lock files left by unclean shutdown​

If the server is not shut down cleanly, the following lock files may be left on the server:

  • XL_DEPLOY_SERVER_HOME/repository/.lock. Ensure that Deploy is not running before removing this file
  • XL_DEPLOY_SERVER_HOME/repository/index/write.lock XL_DEPLOY_SERVER_HOME/repository/workspaces/default/write.lock XL_DEPLOY_SERVER_HOME/repository/workspaces/security/write.lock. Server start-up will be slower after this file is removed because the indexes must be rebuilt.
  • XL_DEPLOY_SERVER_HOME/repository/version/db/db.lck XL_DEPLOY_SERVER_HOME/repository/version/db/dbex.lck
  • XL_DEPLOY_SERVER_HOME/repository/workspaces/default/db/db.lck XL_DEPLOY_SERVER_HOME/repository/workspaces/default/db/dbex.lck XL_DEPLOY_SERVER_HOME/repository/workspaces/security/db/db.lck XL_DEPLOY_SERVER_HOME/repository/workspaces/security/db/dbex.lck