Date
1 - 6 of 6
Problem deploying basic Apps on PWS
|
Juan Antonio Breña Moral <bren at juanantonio.info...>
Hi,
I am trying to deploy an Application on PWS and I think that the problem is something related with Diego. In previous weeks, I deployed without any problem to PWS but today, I receive the following message from CLI: 2015-10-29T15:32:18.28+0100 [HEALTH/0] OUT healthcheck failed 2015-10-29T15:32:18.29+0100 [HEALTH/0] OUT Exit status 1 2015-10-29T15:32:19.33+0100 [HEALTH/0] OUT healthcheck failed 2015-10-29T15:32:19.33+0100 [HEALTH/0] OUT Exit status 1 2015-10-29T15:32:19.33+0100 [CELL/0] ERR Timed out after 1m0s: health check never passed. 2015-10-29T15:32:19.34+0100 [CELL/0] OUT Exit status 0 2015-10-29T15:32:19.34+0100 [APP/0] OUT Exit status 255 2015-10-29T15:32:19.42+0100 [API/2] OUT App instance exited with guid f658 33a-03d8-4191-a463-ddb9e35b7215 payload: {"instance"=>"56f0ebf2-62a0-4bf1-5bda- b790d1af0f7", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) ccurred:\n\n* Exited with status 1\n* 2 error(s) occurred:\n\n* cancelled\n* ca celled", "crash_count"=>4, "crash_timestamp"=>1446129139379123812, "version"=>" 5bbb951-ebf7-4a58-a50f-e92e834d46ca"} Current manifest is: --- applications: - name: psldeploymanager4 memory: 512MB disk_quota: 512MB instances: 1 command: node ./index.js host: psldeploymanager4 path: . buildpack: https://github.com/cloudfoundry/nodejs-buildpack I am not sure if Diego needs some additional attribute. In local, the app runs nice and it was tested on a local instance and bluemix. Any clue? Many thanks in advance. Juan Antonio |
|
|
|
Nicholas Calugar
Hi Juan Antonio,
Support for PWS is available here: http://support.run.pivotal.io/home Is your application a worker (one that doesn't respond to http)? If so, you should disable the health check per http://support.run.pivotal.io/entries/105844873-Migrating-Applications-from-DEAs-to-Diego . Relevant snippet: Worker applications, those that are pushed with the *--no-route* option, will likely fail when run on Diego. This is because you must explicitly disable the port-based health check when running on Diego. This is done by running *cf set-health-check app-name* to none. Nicholas Calugar On Thu, Oct 29, 2015 at 7:39 AM Juan Antonio Breña Moral < bren(a)juanantonio.info> wrote: Hi, |
|
|
|
Juan Antonio Breña Moral <bren at juanantonio.info...>
Hi Nicholas,
many thanks for the doubt. I continue here: http://support.run.pivotal.io/entries/106222933-Problem-deploying-basic-Apps-on-PWS |
|
|
|
Charles Wu
We have seen this with some node apps. Does your app or buildpack reference
either of the following env variables VCAP_APP_HOST and VCAP_APP_PORT. http://support.run.pivotal.io/entries/105844873-Migrating-Applications-from-DEAs-to-Diego If your app references, you can adjust with the following: - *VCAP_APP_HOST* and *VCAP_APP_PORT* environment variables have been removed. *VCAP_APP_HOST* was always *0.0.0.0*, so you can safely use that in place of the environment variable. *VCAP_APP_PORT* is replaced by *PORT* and is set to *8080* by default. On Thu, Oct 29, 2015 at 8:21 AM, Juan Antonio Breña Moral < bren(a)juanantonio.info> wrote: Hi Nicholas, |
|
|
|
Juan Antonio Breña Moral <bren at juanantonio.info...>
Hi Charles,
You said the clue!!! Yesterday, I updated the development and I could deploy on PWS. From environments without Diego, the way to run a Node development is: var localPort = process.env.VCAP_APP_PORT|| 5000; With Diego the way is: var localPort = process.env.PORT || 5000; If the developer uses GO Cli, it is necessary to indicate the application that it uses Diego: cf push APP_XXX --no-start cf enable-diego APP_XXX cf start APP_XXX |
|
|
|
Charles Wu
You can also download the latest CLI.
Note all new apps deployed on PWS are defaulted to Diego as the app runner environment. The enable-diego is only needed to switch DEA deployed apps to use Diego. br, Charles On Fri, Oct 30, 2015 at 1:56 AM, Juan Antonio Breña Moral < bren(a)juanantonio.info> wrote: Hi Charles, |
|
|