|Pivotal Cloud Foundry||All|
After successfully deploying Elastic Runtime and Service Tiles via Ops Manager, you might need to run errands due to cases like the following:
- (Re)deploy Notification Service, Autoscaling Service, etc. after the first install.
- Run smoke-test upon Elastic Runtime or Service Tiles after install.
It is usually easier to debug problems when you run errands manually. By setting the "--keep-alive" flag, the errand VM will be kept alive for debug use; please refer the KB article How to run errands step-by-step for details.
Most of the above tasks can be done via Ops Manager, by selecting/deselecting errands, and then "Apply Change". However, it may take a longer time compared to running errands via BOSH command. This article discusses how to run BOSH errands directly.
- Log on to Ops Manager VM via Single SHell (SSH); there are other options like a jump box. The advantage in using Ops Manager VM is BOSH CLI and deployment manifest files are already available on the VM.
- List up all deployments with the "bosh deployments" command.
- Set current deployment to thetile which you want to execute errands:
bosh deployment /var/tempest/workspaces/default/deployments/<deployment name>.yml
- Execute the "bosh run errand' command", it will list up all available errands within the deployment:
(Here is example for running errand of Elastic Runtime)
$ bosh run errand
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
Choose an errand:
- Input the errand index you want to run and press "Enter".
Do not run errands such as "Unregister Broker" or "Destroy Broker". These are meant to be run when uninstalling tiles and running them will usually result in data loss. Because of this, we do not recommend that you run errands manually in production environments. If you have any questions or reservations about running a specific errand, please contact support before running the errand.