search

ibm-watson-data-lab / parse-on-bluemix

A quick attempt to roll @ParsePlatform on @ibm-bluemix and see what happens
Apache License 2.0
3 stars 3 forks source link

I unable to install parse dashboard as CF app #3

Open gowridev opened 8 years ago

gowridev commented 8 years ago

I am unable to install parse dashboard in ibm bluemix. Could you please guide me. I am getting an error.

2016-03-29T12:57:55.23+0530 [API/7] OUT Updated app with guid 779b0b13-0bf2-4e4e-8259-100c597f1465 ({"name"=>"parse-dashboard", "command"=>"PRIVATE DATA HIDDEN", "memory"=>1024}) 2016-03-29T12:58:11.77+0530 [API/2] OUT Updated app with guid 779b0b13-0bf2-4e4e-8259-100c597f1465 ({"state"=>"STOPPED"}) 2016-03-29T12:58:16.81+0530 [DEA/112] OUT Got staging request for app with id 779b0b13-0bf2-4e4e-8259-100c597f1465 2016-03-29T12:58:28.26+0530 [API/0] OUT Updated app with guid 779b0b13-0bf2-4e4e-8259-100c597f1465 ({"state"=>"STARTED"}) 2016-03-29T12:58:28.78+0530 [STG/112] OUT -----> Downloaded app package (1.2M) 2016-03-29T12:58:29.10+0530 [STG/112] OUT -----> Downloaded app buildpack cache (444K) 2016-03-29T12:58:30.20+0530 [STG/0] OUT 2016-03-29T12:58:30.20+0530 [STG/0] OUT -----> IBM SDK for Node.js Buildpack v3.2-20160315-1257 2016-03-29T12:58:30.21+0530 [STG/0] OUT Based on Cloud Foundry Node.js Buildpack v1.5.4 2016-03-29T12:58:30.21+0530 [STG/0] OUT -----> Creating runtime environment 2016-03-29T12:58:30.23+0530 [STG/0] OUT NPM_CONFIG_LOGLEVEL=error 2016-03-29T12:58:30.23+0530 [STG/0] OUT NPM_CONFIG_PRODUCTION=true 2016-03-29T12:58:30.24+0530 [STG/0] OUT NODE_ENV=production 2016-03-29T12:58:30.24+0530 [STG/0] OUT NODE_MODULES_CACHE=true 2016-03-29T12:58:30.24+0530 [STG/0] OUT -----> Installing binaries 2016-03-29T12:58:30.27+0530 [STG/0] OUT engines.node (package.json): >=4.3 2016-03-29T12:58:30.27+0530 [STG/0] OUT engines.npm (package.json): unspecified (use default) 2016-03-29T12:58:30.28+0530 [STG/0] OUT Resolving node version >=4.3 via 'node-version-resolver' 2016-03-29T12:58:30.55+0530 [STG/0] OUT Installing IBM SDK for Node.js (4.3.2) from cache 2016-03-29T12:58:31.52+0530 [STG/0] OUT Using default npm version: 2.14.12 2016-03-29T12:58:31.81+0530 [STG/0] OUT -----> Restoring cache 2016-03-29T12:58:32.19+0530 [STG/0] OUT Loading 2 from cacheDirectories (default): 2016-03-29T12:58:32.19+0530 [STG/0] OUT - node_modules 2016-03-29T12:58:32.20+0530 [STG/0] OUT - bower_components (not cached - skipping) 2016-03-29T12:58:32.20+0530 [STG/0] OUT -----> Building dependencies 2016-03-29T12:58:32.20+0530 [STG/0] OUT Pruning any extraneous modules 2016-03-29T12:58:33.25+0530 [STG/0] OUT Installing node modules (package.json) 2016-03-29T12:58:34.33+0530 [STG/0] OUT -----> Installing App Management 2016-03-29T12:58:44.21+0530 [STG/0] OUT -----> Caching build 2016-03-29T12:58:44.23+0530 [STG/0] OUT Clearing previous node cache 2016-03-29T12:58:44.23+0530 [STG/0] OUT Saving 2 cacheDirectories (default): 2016-03-29T12:58:44.23+0530 [STG/0] OUT - node_modules 2016-03-29T12:58:44.39+0530 [STG/0] OUT - bower_components (nothing to cache) 2016-03-29T12:58:45.33+0530 [STG/0] OUT ├── basic-auth@1.0.3 2016-03-29T12:58:45.33+0530 [STG/0] OUT ├── commander@2.9.0 2016-03-29T12:58:45.33+0530 [STG/0] OUT ├── express@4.13.4 2016-03-29T12:58:45.33+0530 [STG/0] OUT ├── json-file-plus@3.3.0 2016-03-29T12:58:45.33+0530 [STG/0] OUT └── package-json@2.3.1 2016-03-29T12:58:45.34+0530 [STG/0] ERR 2016-03-29T12:58:50.05+0530 [STG/112] OUT -----> Uploading droplet (17M) 2016-03-29T12:58:55.57+0530 [DEA/112] OUT Starting app instance (index 0) with guid 779b0b13-0bf2-4e4e-8259-100c597f1465 2016-03-29T12:59:09.31+0530 [App/0] ERR 2016-03-29T12:59:09.31+0530 [App/0] OUT 2016-03-29T12:59:09.39+0530 [DEA/112] ERR Instance (index 0) failed to start accepting connections 2016-03-29T12:59:09.43+0530 [API/6] OUT App instance exited with guid 779b0b13-0bf2-4e4e-8259-100c597f1465 payload: {"cc_partition"=>"default", "droplet"=>"779b0b13-0bf2-4e4e-8259-100c597f1465", "version"=>"28c96cc5-c0c6-4288-b02b-8c31a3eb48b9", "instance"=>"2ac44c46deb942bc80fd1f566311c848", "index"=>0, "reason"=>"CRASHED", "exit_status"=>0, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1459236549} 2016-03-29T12:59:09.51+0530 [API/7] OUT App instance exited with guid 779b0b13-0bf2-4e4e-8259-100c597f1465 payload: {"cc_partition"=>"default", "droplet"=>"779b0b13-0bf2-4e4e-8259-100c597f1465", "version"=>"28c96cc5-c0c6-4288-b02b-8c31a3eb48b9", "instance"=>"2ac44c46deb942bc80fd1f566311c848", "index"=>0, "reason"=>"CRASHED", "exit_status"=>0, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1459236549}

ukmadlz commented 7 years ago

Just from looking it would appear that you haven't assigned the port & host to the app. These are needed for Bluemix to check the health of the app