Date
1 - 5 of 5
Deploying CF to AWS is failing
|
Shetty, Daya <Daya.Shetty@...>
Hello,
Deploying CF using the minimal-aws.yml is failing in Started compiling packages Started compiling packages > rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4 Started compiling packages > haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613 Started compiling packages > buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4 Started compiling packages > buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3 Started compiling packages > buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157 Started compiling packages > buildpack_python/47881166ec20d60fa8c7dba7f53b8e1e251086f7 Failed compiling packages > haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613: execution expired (00:02:33) Failed compiling packages > buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: execution expired (00:02:33) Failed compiling packages > buildpack_python/47881166ec20d60fa8c7dba7f53b8e1e251086f7: execution expired (00:02:33) Failed compiling packages > buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3: execution expired (00:02:33) Failed compiling packages > rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4: execution expired (00:02:35) Failed compiling packages > buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4: execution expired (00:02:35) If it helps, I have attached the debug log of the failed task Thanks in advance -Daya The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. |
|
|
|
Gwenn Etourneau
What is the spec of the compile VM ?
On Wed, Jun 24, 2015 at 10:46 AM, Shetty, Daya <Daya.Shetty(a)bnymellon.com> wrote: Hello, |
|
|
|
Dmitriy Kalinin
Please include a stack trace from `bosh task X --debug` where X is the
Director task number that was included in the `bosh deploy` output. On Tue, Jun 23, 2015 at 6:48 PM, Gwenn Etourneau <getourneau(a)pivotal.io> wrote: What is the spec of the compile VM ? |
|
|
|
Aristoteles Neto <neto@...>
The dbg.log file was included in the original message Dmitry.
toggle quoted message
Show quoted text
I’d start by checking the BOSH director security group - it sounds like you’re getting a connect timeout error? D, [2015-06-23 22:38:14 #9260] [task:10] DEBUG -- DirectorJobRunner: SENT: hm.director.alert {"id":"08f3c0ca-34ea-40cb-a9bc-ebe5a28f69fc","severity":3,"title":"director - error during update deployment","summary":"Error during update deployment for 'cfDaya' against Director '3cc59fcd-7078-4255-9280-8cbd764f7f1d': #<HTTPClient::ConnectTimeoutError: execution expired>","created_at":1435099094} It may not be related to this but I too was having problems with ‘execution expired’ messages coming through whenever some of the other guys were deploying things but never when I did it. Turned out the issue was that they were deploying several environments simultaneously, which was causing the BOSH director to max out its CPU. After the execution expired, I’d then get a 404 when re-trying the deploy until I removed rendered_templates_archive entry for the affected VM. Perhaps that’s also worth a look? Regards, Neto On 24/06/2015, at 14:03, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:
Please include a stack trace from `bosh task X --debug` where X is the Director task number that was included in the `bosh deploy` output. |
|
|
|
Shetty, Daya <Daya.Shetty@...>
Dmitri,
The spec of the compile VM is amzn-ami-vpc-nat-pv-2014.09.1.x86_64-ebs. Neto, The security group for the Director has the following inbound rules.. The source IP was originally set to my corporate network IP but changed it to 0.0.0.0 later. Anything you see amiss. Also any suggestions on how to debug this because I don’t get any time to debug this on the newly spun VM’s as they are shutdown immediately. Thanks in advance -Daya All UDP UDP 0 - 65535 sg-9517f3f2 (cfdiego) Custom TCP Rule TCP 4443 0.0.0.0/0 SSH TCP 22 0.0.0.0/0 Custom TCP Rule TCP 25889 0.0.0.0/0 Custom TCP Rule TCP 6868 0.0.0.0/0 Custom TCP Rule TCP 25555 0.0.0.0/0 All TCP TCP 0 - 65535 sg-9517f3f2 (cfdiego) From: <Shetty>, Daya Shetty <Daya.Shetty(a)bnymellon.com<mailto:Daya.Shetty(a)bnymellon.com>> Date: Tuesday, June 23, 2015 at 6:46 PM To: "cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>" <cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org>> Subject: Deploying CF to AWS is failing Hello, Deploying CF using the minimal-aws.yml is failing in Started compiling packages Started compiling packages > rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4 Started compiling packages > haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613 Started compiling packages > buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4 Started compiling packages > buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3 Started compiling packages > buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157 Started compiling packages > buildpack_python/47881166ec20d60fa8c7dba7f53b8e1e251086f7 Failed compiling packages > haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613: execution expired (00:02:33) Failed compiling packages > buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: execution expired (00:02:33) Failed compiling packages > buildpack_python/47881166ec20d60fa8c7dba7f53b8e1e251086f7: execution expired (00:02:33) Failed compiling packages > buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3: execution expired (00:02:33) Failed compiling packages > rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4: execution expired (00:02:35) Failed compiling packages > buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4: execution expired (00:02:35) If it helps, I have attached the debug log of the failed task Thanks in advance -Daya The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. |
|
|