Skip to content
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

Cannot start node-red in IBM Cloud #32

Closed
Ayumu-walker opened this issue Jan 22, 2019 · 2 comments
Closed

Cannot start node-red in IBM Cloud #32

Ayumu-walker opened this issue Jan 22, 2019 · 2 comments

Comments

@Ayumu-walker
Copy link

v0.6.0

The same phenomenon as problem 26 also occurred on the IBM Cloud. The same fixes made the problem resolved. Is this correct as an official solution?
#26

@knolleary
Copy link
Contributor

If you get that error running in the IBM Cloud it means the starter has not been able to find the Cloudant database instance, so is falling back to localfilesystem and hitting the error.

You should not use localfilesystem on IBM Cloud - the filesystem is not persistent between application restarts. So whilst #26 does need addressing (and not using the change suggested as that will not work with later versions of Node-RED), your issue is whatever has meant it was unable to find cloudant.

@Ayumu-walker
Copy link
Author

Thank you so much for your answer!
After changing the Cloudant service name to include it in the application name, the deployment succeeded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants