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

rhizome with forever? #129

Closed
tatecarson opened this issue Aug 27, 2016 · 7 comments
Closed

rhizome with forever? #129

tatecarson opened this issue Aug 27, 2016 · 7 comments

Comments

@tatecarson
Copy link

I'd like to use forever to run rhizome on EC2 so I don't have to use the terminal to start it before a performance, so there's less things to worry about. Forever runs your script using forever start app.js so I can't figure out how to get it to use rhizome config.js. forever rhizome config.js doesn't work. Have you ever used this? Maybe there's a way I can change the way rhizome is called back to start in order to use forever?

thanks again.

@sebpiq
Copy link
Owner

sebpiq commented Sep 10, 2016

hey! Sorry for slow answer. I also use forever, and I usually call the whole path for example forever node /path/to/rhizome/bin/rhizome.js config.js . To get the path to rhizome, you can run which rhizome

@sebpiq sebpiq closed this as completed Sep 10, 2016
@tatecarson
Copy link
Author

tatecarson commented Sep 10, 2016

I can't quite get it to work.
This starts rhizome fine:
node /usr/local/lib/node_modules/rhizome-server/bin/rhizome.js config.js

but this:
forever node /usr/local/lib/node_modules/rhizome-server/bin/rhizome.js config.js

throws

error:   Cannot start forever
error:   script /home/ubuntu/node does not exist.

Any idea why? That's obviously the correct path because it starts rhizome, but just doesn't work with forever in front of it.

thanks again.

@sebpiq
Copy link
Owner

sebpiq commented Sep 10, 2016

aah sorry my mistake. Here is probably what you should run forever start /usr/local/lib/node_modules/rhizome-server/bin/rhizome.js config.js

@tatecarson
Copy link
Author

tatecarson commented Sep 11, 2016

Hmm can you think of any reason why this wouldn't be working:
sudo ~/.nvm/versions/node/v4.4.2/bin/forever start /usr/local/lib/node_modules/rhizome-server/bin/rhizome.js config.js

It runs forever but doesn't start rhizome.

@sebpiq
Copy link
Owner

sebpiq commented Sep 11, 2016

Hmm no ... not really. What error message do you get?

@tatecarson
Copy link
Author

Unfortunately there is no error. Forever says it's started but it just doesn't start rhizome. This is what happens:

warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: /usr/local/lib/node_modules/rhizome-server/bin/rhizome.js

@sebpiq
Copy link
Owner

sebpiq commented Sep 11, 2016

then you have some other bug ... activate logging to see it :

 sudo ~/.nvm/versions/node/v4.4.2/bin/forever -a -l /tmp/rhizome.log start /usr/local/lib/node_modules/rhizome-server/bin/rhizome.js config.js

and check out what's in the log with :

tail -n 30 /tmp/rhizome.log

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