Re: Problem deploying basic Apps on PWS

Nicholas Calugar

Hi Juan Antonio,

Support for PWS is available here:

Is your application a worker (one that doesn't respond to http)? If so, you
should disable the health check per

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)> wrote:


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
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
33a-03d8-4191-a463-ddb9e35b7215 payload:
b790d1af0f7", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2
ccurred:\n\n* Exited with status 1\n* 2 error(s) occurred:\n\n*
cancelled\n* ca
celled", "crash_count"=>4, "crash_timestamp"=>1446129139379123812,

Current manifest is:

- name: psldeploymanager4
memory: 512MB
disk_quota: 512MB
instances: 1
command: node ./index.js
host: psldeploymanager4
path: .

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

Join to automatically receive all group messages.