-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual Bluemix deployment error #9
Comments
Hi, I assume you followed the instructions here: https://github.com/node-red/node-red-bluemix/blob/master/README.md#deploying-node-red-into-bluemix Do you have the staging logs for your app - that will show what actually got installed and hopefully why it doesn't appear to have installed the node-red module. As an alternative approach, you could use the Deploy To Bluemix enabled repository here: https://github.com/node-red/node-red-bluemix-starter |
Hey Nick Thanks for the link, I was using the instructions from the first link's readme.md. I'll also take a look at the bluemix-starter pack After a fresh redeploy just now, it got further but with a different error - i think this one might be Bluemix related (?) Logs:
|
Hi,
I've been experiencing problems in creating Node-Red boiler plate on Bluemix (have raised a ticket for it) - so I'm trying to do a manual deployment with this in the mean time instead.
It's failing with error of 'Can not find Node-red module', logs:
2016-03-15T17:19:40.726-0000[DEA/103]OUTStarting app instance (index 0) with guid f2eeaa9c-c331-4e18-8dd3-129af0418a47
2016-03-15T17:19:51.215-0000[App/0]ERRmodule.js:328
2016-03-15T17:19:51.215-0000[App/0]ERR throw err;
2016-03-15T17:19:51.215-0000[App/0]ERR ^
2016-03-15T17:19:51.216-0000[App/0]ERRError: Cannot find module '/home/vcap/app/node_modules/node-red/red.js'
2016-03-15T17:19:51.221-0000[App/0]ERR at Function.Module._resolveFilename (module.js:326:15)
2016-03-15T17:19:51.222-0000[App/0]ERR at Function.Module.runMain (module.js:442:10)
2016-03-15T17:19:51.222-0000[App/0]ERR at Function.Module._load (module.js:277:25)
2016-03-15T17:19:51.222-0000[App/0]ERR at startup (node.js:136:18)
2016-03-15T17:19:51.223-0000[App/0]OUT
2016-03-15T17:19:51.223-0000[App/0]ERR at node.js:966:3
2016-03-15T17:19:51.396-0000[DEA/103]ERRInstance (index 0) failed to start accepting connections
2016-03-15T17:19:51.423-0000[API/1]OUTApp instance exited with guid f2eeaa9c-c331-4e18-8dd3-129af0418a47 payload: {"cc_partition"=>"default", "droplet"=>"f2eeaa9c-c331-4e18-8dd3-129af0418a47", "version"=>"cb3061b2-27ad-4719-aab6-d4783709d6ca", "instance"=>"de4fdb8b28514b8d88d68f542de09bda", "index"=>0, "reason"=>"CRASHED", "exit_status"=>1, "exit_description"=>"failed to accept connections within health check timeout", "crash_timestamp"=>1458062391}
The text was updated successfully, but these errors were encountered: