manifest file issue

[chaoMaster]

the buildpack address error on manifest.yml
so I delete this line, and rebuild this app.
the log is as follows:

2017-04-12T22:04:54.72+0800 [API/0] OUT Updated app with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 ({"route"=>"b09e24d1-224c-4d3c-8968-fca1ba246c17"})
2017-04-12T22:05:23.13+0800 [API/0] OUT Created app with guid 95192d61-7fed-419a-a629-c1643ff4e2e7
2017-04-12T22:06:01.32+0800 [DEA/2] OUT Got staging request for app with id 95192d61-7fed-419a-a629-c1643ff4e2e7
2017-04-12T22:06:03.10+0800 [STG/2] OUT -----> Downloaded app package (268K)
2017-04-12T22:06:04.25+0800 [STG/0] OUT
2017-04-12T22:06:04.25+0800 [STG/0] OUT -----> IBM SDK for Node.js Buildpack v3.11-20170303-1144
2017-04-12T22:06:04.25+0800 [STG/0] OUT Based on Cloud Foundry Node.js Buildpack v1.5.24
2017-04-12T22:06:04.25+0800 [STG/0] OUT -----> Creating runtime environment
2017-04-12T22:06:04.26+0800 [STG/0] OUT NPM_CONFIG_LOGLEVEL=error
2017-04-12T22:06:04.26+0800 [STG/0] OUT NPM_CONFIG_PRODUCTION=true
2017-04-12T22:06:04.27+0800 [STG/0] OUT NODE_ENV=production
2017-04-12T22:06:04.27+0800 [STG/0] OUT NODE_MODULES_CACHE=true
2017-04-12T22:06:04.27+0800 [STG/0] OUT -----> Installing binaries
2017-04-12T22:06:04.28+0800 [STG/0] OUT engines.node (package.json): unspecified
2017-04-12T22:06:04.28+0800 [STG/0] OUT engines.npm (package.json): unspecified (use default)
2017-04-12T22:06:04.29+0800 [STG/0] OUT Resolving node version (latest stable) via 'node-version-resolver'
2017-04-12T22:06:04.70+0800 [STG/0] OUT Installing IBM SDK for Node.js (4.8.0) from cache
2017-04-12T22:06:06.23+0800 [STG/0] OUT Using default npm version: 2.15.11
2017-04-12T22:06:06.23+0800 [STG/0] OUT -----> Restoring cache
2017-04-12T22:06:06.47+0800 [STG/0] OUT Skipping cache restore (new runtime signature)
2017-04-12T22:06:06.48+0800 [STG/0] OUT -----> Building dependencies
2017-04-12T22:06:06.48+0800 [STG/0] OUT Installing node modules (package.json)
2017-04-12T22:06:07.03+0800 [STG/0] OUT -----> Installing App Management
2017-04-12T22:06:07.09+0800 [STG/0] OUT WARN: App Management cannot be installed because the start script cannot be found.
2017-04-12T22:06:07.09+0800 [STG/0] OUT To install App Management utilities, specify your 'node' start script in 'package.json' or 'Procfile'.
2017-04-12T22:06:07.09+0800 [STG/0] OUT -----> Caching build
2017-04-12T22:06:07.10+0800 [STG/0] OUT Clearing previous node cache
2017-04-12T22:06:07.10+0800 [STG/0] OUT Saving 2 cacheDirectories (default):
2017-04-12T22:06:07.10+0800 [STG/0] OUT - node_modules (nothing to cache)
2017-04-12T22:06:07.10+0800 [STG/0] OUT - bower_components (nothing to cache)
2017-04-12T22:06:07.33+0800 [STG/0] OUT -----> Build succeeded!
2017-04-12T22:06:07.74+0800 [STG/0] OUT └── (empty)
2017-04-12T22:06:07.75+0800 [STG/0] ERR
2017-04-12T22:06:10.52+0800 [STG/2] OUT -----> Uploading droplet (14M)
2017-04-12T22:06:13.10+0800 [DEA/2] OUT Starting app instance (index 0) with guid 95192d61-7fed-419a-a629-c1643ff4e2e7
2017-04-12T22:06:16.75+0800 [API/0] OUT Updated app with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 ({"diego"=>false})
2017-04-12T22:06:27.91+0800 [API/0] OUT Updated app with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 ({"state"=>"STARTED"})
2017-04-12T22:07:57.87+0800 [API/0] OUT App instance exited with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 payload: {"cc_partition"=>"default", "droplet"=>"95192d61-7fed-419a-a629-c1643ff4e2e7", "version"=>"2dd71bf3-dc91-4bdc-8f42-22c7e8dbbe42", "instance"=>"53929815eab846eca234ccb41fb1ea5c", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"app instance exited", "crash_timestamp"=>1492006092}
2017-04-12T22:08:09.31+0800 [DEA/2] OUT Starting app instance (index 0) with guid 95192d61-7fed-419a-a629-c1643ff4e2e7
2017-04-12T22:08:50.23+0800 [API/0] OUT App instance exited with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 payload: {"cc_partition"=>"default", "droplet"=>"95192d61-7fed-419a-a629-c1643ff4e2e7", "version"=>"2dd71bf3-dc91-4bdc-8f42-22c7e8dbbe42", "instance"=>"53929815eab846eca234ccb41fb1ea5c", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1492006152}
2017-04-12T22:08:50.33+0800 [API/0] OUT App instance exited with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 payload: {"cc_partition"=>"default", "droplet"=>"95192d61-7fed-419a-a629-c1643ff4e2e7", "version"=>"2dd71bf3-dc91-4bdc-8f42-22c7e8dbbe42", "instance"=>"9a4946d5716949048fb4b61f1a480980", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1492006140}
2017-04-12T22:08:50.46+0800 [API/0] OUT App instance exited with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 payload: {"cc_partition"=>"default", "droplet"=>"95192d61-7fed-419a-a629-c1643ff4e2e7", "version"=>"2dd71bf3-dc91-4bdc-8f42-22c7e8dbbe42", "instance"=>"9a4946d5716949048fb4b61f1a480980", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1492006140}
2017-04-12T22:08:57.78+0800 [DEA/1] OUT Starting app instance (index 0) with guid 95192d61-7fed-419a-a629-c1643ff4e2e7
2017-04-12T22:09:00.72+0800 [DEA/1] ERR Instance (index 0) failed to start accepting connections
2017-04-12T22:09:12.20+0800 [DEA/2] ERR Instance (index 0) failed to start accepting connections
2017-04-12T22:09:50.91+0800 [API/0] OUT App instance exited with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 payload: {"cc_partition"=>"default", "droplet"=>"95192d61-7fed-419a-a629-c1643ff4e2e7", "version"=>"2dd71bf3-dc91-4bdc-8f42-22c7e8dbbe42", "instance"=>"fe55afccd8bd41ba92f5e86fa49e08be", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1492006202}
2017-04-12T22:09:59.22+0800 [DEA/0] OUT Starting app instance (index 0) with guid 95192d61-7fed-419a-a629-c1643ff4e2e7
2017-04-12T22:10:02.56+0800 [DEA/0] ERR Instance (index 0) failed to start accepting connections
2017-04-12T22:10:20.59+0800 [API/0] OUT App instance exited with guid 95192d61-7fed-419a-a629-c1643ff4e2e7 payload: {"cc_partition"=>"default", "droplet"=>"95192d61-7fed-419a-a629-c1643ff4e2e7", "version"=>"2dd71bf3-dc91-4bdc-8f42-22c7e8dbbe42", "instance"=>"fe55afccd8bd41ba92f5e86fa49e08be", "index"=>0, "reason"=>"CRASHED", "exit_status"=>127, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1492006202}

-----> Downloaded app package (268K)

-----> IBM SDK for Node.js Buildpack v3.11-20170303-1144
Based on Cloud Foundry Node.js Buildpack v1.5.24
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NPM_CONFIG_PRODUCTION=true
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version (latest stable) via 'node-version-resolver'
Installing IBM SDK for Node.js (4.8.0) from cache
Using default npm version: 2.15.11
-----> Restoring cache
Skipping cache restore (new runtime signature)
-----> Building dependencies
Installing node modules (package.json)
-----> Installing App Management
WARN: App Management cannot be installed because the start script cannot be found.
To install App Management utilities, specify your 'node' start script in 'package.json' or 'Procfile'.
-----> Caching build
Clearing previous node cache
Saving 2 cacheDirectories (default):
- node_modules (nothing to cache)
- bower_components (nothing to cache)
-----> Build succeeded!
└── (empty)

-----> Uploading droplet (14M)

0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 failing
FAILED
Start unsuccessful