Pivotal Knowledge Base

Follow

Exporting installation via Ops Manager failed with error "500 An error occurred, Contact Pivotal Technical Support report the problem"

Environment

  • Pivotal Cloud Foundry® Ops Manager 1.2.x, 1.3.x, 1.4.0

Symptom 

When export installed products vis Ops Manager, sometimes the export process takes more than 10 minutes and finally fails with error:

500 An error occurred.
Contact Pivotal Technical Support report the problem.

Cause

When running the export, backend process on Ops Manager archives files such as stemcells, compiled packages, configurations, release packages into one .zip file. Some of those files are very large so that it takes longer to archive them. Especially on a virtual machine (Ops Manager VM) which has very limited RAM, it will take more time because of memory paging.

The current timeout setting is configured as 600s. However, in case of more than 2 or 3 services installed, it is not sufficient for export process to complete within 600s.

Resolution

Product Side
There are a few improvements on product side from Ops Manager v1.4.x:

  • By sharing stemcells between releases, carrying them in Ops Manager instead, export archive file size is shrunk.
  • Timeout of the export(and import) operation is changed from 600s to 1800s in Ops Manager v1.4.1.

Workaround
As temporary workaround if you are using Ops Manager less than v1.4.1, please manually configure timeout value or assign more resource to Ops Manager VM to improve performance. 

Configure bigger timeout value:

  1. SSH into Ops Manager VM with 'tempest' account.
  2. Stop Ops Manager process by issuing 'sudo service tempest-web stop'.
  3. Edit /home/tempest-web/tempest/web/config/thin.production.yml, change 'timeout' from 600 to 1800, save and quit.
  4. Start Ops Manager process by issuing 'sudo service tempest-web start'.
  5. Log in Ops Manager web console, re-run "Export Installation Settings".

Assign more system resource to Ops Manager which helps to improve performance significantly:

  1. Increase numbers of virtual CPU.
  2. Assign 4GB or 8GB RAM to Ops Manager VM if possible.

Comments

Powered by Zendesk