Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
My app is http://carpool-carpooler.rhcloud.com/ if that's helpful.
Hi, Can you please provide more informations? Like the error message you get from OpenShift when you are trying to SSH into your app or what you get back when you are doing app restart?
Hello and thank you for your response! When I try to ssh in, it appears to connect, but trying to run any command produces: rhcsh> ls bash: fork: retry: Resource temporarily unavailable bash: fork: retry: Resource temporarily unavailable bash: fork: retry: Resource temporarily unavailable bash: fork: retry: Resource temporarily unavailable ^C^C^Cmobash: fork: Resource temporarily unavailable rhcsh> mongo bash: fork: retry: Resource temporarily unavailable bash: fork: retry: Resource temporarily unavailable ^C^C^Cbash: fork: retry: Resource temporarily unavailable bash: fork: retry: Resource temporarily unavailable bash: fork: Resource temporarily unavailable rhcsh> When I try to restart the application using the web interface it tells me that an error occurred and I should try refreshing the page. Oddly enough, I can get to a couple of my web pages. When I try to access a page that uses mongo (one of my test pages) it hangs. Any suggestions are welcome. Thanks! I do not know if it's connected, but the issues seemed to start when I added the Openshift Metrics cartidge.
Also you should be able to remove the cartridge with the client tools. The command would be: rhc cartridge remove metrics-0.1 -a carpool
Alternatively you can try to use 'force-stop' action to free some processes. rhc force-stop carpool This will stop the application. You can start it again using: rhc app start carpool
Does the commands mentioned above help?
ping? :-)
Thank you for your time on this, I got frustrated and deleted the gear and started over. If I hit this issue again I will try these solutions. Thanks again! (In reply to Michal Fojtik from comment #7) > ping? :-)