Closed bhudlemeyer closed 7 years ago
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
I went in and modified the tempest-web configuration in this file:
/home/tempest-web/tempest/web/config/thin.production.yml
from its default setting of 30min (1800 sec) to
socket: /tmp/tempest-web.sock
rackup: config.ru
threaded: true
timeout: 60000 (just to ensure we didnt hit anything)
Restarted ops man and the export succeded. So appears to be a hard coded timeout in ops manager I was actually hitting.
Hi Brandon,
Thanks for sharing your workaround for this issue.
Can you give us some more detail about the size of the generated installation file and the approximate length of time it eventually took for your export to succeed?
Thanks,
@acrmp && @kkallday
root@0883eb78-3397-40c8-696e-f1ea857a781c:/tmp/build/0f36ad4e/opsmgr-settings# ls -lh
total 11G
-rw-r--r-- 1 root root 11G Jul 5 20:20 installation.zip
-r-------- 1 root root 3.3K Jul 6 13:15 key
root@0883eb78-3397-40c8-696e-f1ea857a781c:/tmp/build/0f36ad4e/opsmgr-settings#
Took roughly 33 to 35min. So right out side the timeout window basically. If needed I can do another test using time again to get an exact time range.
As a note I have the following tiles deployed in my test system
Unfortunately, since this constraint is on the Ops Manager server side there's nothing we can do from the perspective of om
. We have given this feedback to the Ops Manager team and they are going to consider bumping the timeout. Thanks for letting us know about this!
Kevin & @joshzarrabi
export-installation with opsman 1.11.3.0 is returning unexpected response
Can export from opsman gui successfully without issue.