-
Notifications
You must be signed in to change notification settings - Fork 13
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
redis-server stops around 24 hours #1
Comments
I think is something related with memory. I'm currently investigating this problem with guys from openshift on freenode... |
Are there any updates on this issue? I'm very interested in deploying Redis with my application. |
No update on this issue, I guess. |
@snitramodranoel @bjjay I forgot to update the bug, i solved with a trivial cron job that check if the redis-server is running or not. But anyway, I think the openshift team is already working on a cartridge for redis :) |
Greet! |
Thanks for the tip. Anyways, there's a poll about a redis cartridge on the OpenShift community web site. Maybe you guys already know about it. Let's spread the word and ask for votes ;) |
@razorinc I suppose the issue is due to how OpenShift is implemented with SELinux. I'm not an OpenShift developer, but I bet this will only be solved for real when a redis cartridge is out. That's my two cents. |
@snitramodranoel Leonardo, I don't think is SELinux itself, but for sure, when the cartdrige will come out, would be way more easy to use it :) //cc @marekjelen |
Still no cartridge it seems. To add more details to @razorinc's answer. Add cron cartridge to your app using procedure at https://openshift.redhat.com/community/blogs/getting-started-with-cron-jobs-on-openshift script file in .openshift/cron/hourly/redis-check.sh containing Then |
Corrected about script since Openshift fiddled with their enviroment variables see here |
Do you find this problem? I don't know why, redis-server process isn't existed, but the files redis.pid and redis.sock are still existed.
The text was updated successfully, but these errors were encountered: