Red Hat Bugzilla – Bug 973601
App with mongo database cannot be restarted
Last modified: 2015-05-14 19:21:23 EDT
Created attachment 760058 [details]
The ppk file
Description of problem:
When I was triying to access my app (www.buscopubli.es) I have got an out of memory exception in Mongo. Since then I cannot access remtely to the application in order to restart both mongo and application. Obviously I cannot access via rch client
Version-Release number of selected component (if applicable):
Connect to email@example.com
Steps to Reproduce:
Connect to my remote machine
Restart can be done via rhc - what error do you see when you try to run 'rhc restart-app <name>'? If that fails, run rhc force-stop-app <name>. Please provide the output of both of those commands here.
Thx Clayton, it seems to be OK now, have you done anything? Anycase,i´ll take note about force-stop command.
It looks like the main process was wedged - we've continued to debug the issue and have restarted your app. There appears to be a broken gear in your app, operations will be investigating.
Rodgrigo, I'm trying to figure out how your application got into this state. Did you try to import a large file into the database or restore a dump with a lot of information?
Also, I noticed that you uploaded your SSH key as an attachment. Since this is a public bug, it's safe to assume your key is compromised since anybody could have downloaded it. I highly recommend deleting this key and removing it from your OpenShift applications. If you used this key anywhere else (like home or work), you will also want to remove it from your authorized_keys and generated a new key.
Thank you, I didn't realize about the secure problem. Any case,I only try to redeploy application in the cluster. It begun doing problems and I coudn't stop application. I don't remember to do any cpu or io intensive operation.
Just trying to execute rhc app stop and restart becouse it seem that the application wasn´t updating correctly.
Thx for the information....
Hi Rodrigo, do you have any more information you could share with us? Any more details about specific error messages you encountered? Were your issues with JBoss, or MongoDB, or both?