| Summary: | Error message: Failed to execute: 'control stop' for node.js | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Rich Hildred <rhildred> |
| Component: | Image | Assignee: | Paul Morie <pmorie> |
| Status: | CLOSED WORKSFORME | QA Contact: | libra bugs <libra-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.x | CC: | bparees, rhildred |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-10 14:39:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Rich Hildred
2013-12-12 03:35:13 UTC
Hi Rich- Please try force-stopping your app (rhc app force-stop <name of app>) and restarting. Hi Paul: I will have to try in a couple of hours, as I am in my office right now, away from rhc. I can ssh to my gear only. thanks Rich The force stop worked. My student, who's gear is in the same condition as mine doesn't have ruby or rhc. I see that there is a curl equivalent to do the force stop. curl -k -X POST https://openshift.redhat.com/broker/rest/domains/[Domain_ID]/applications/[App_Name]/events --user "[UserName]:[Password]" --data "event=force-stop" It seems unfortunate that I couldn't update my gear. Can you learn anything about the state of my machine, or that of my student. Is this just something that happens? Rich- Have you tried to git-push after force-stopping and restarting? Hi Again Paul: Yes I was able to successfully git push after I did the force start. I will try the curl on my student's machine this morning, and see if that gets him going. thanks Rich the pid file in question is nodejs/run/cartridge.pid on your gear. Is it possible you or your application deleted that file or directory? As an alternative to force stop, you can also ssh into the gear and recreate the pid file with the appropriate pid#. (rhc ssh <appname>) Rich, do you have any update on this? i'd be interested in seeing your app repository if you are still hitting this. Hi Ben: Sorry I didn't reply on the 6th. My gear is working well now. The curl -k -X POST https://openshift.redhat.com/broker/rest/domains/[Domain_ID]/applications/[App_Name]/events --user "[UserName]:[Password]" --data "event=force-stop" allowed me to stop it. An interesting thing that I noticed about the pid in nodejs/run/cartridge.pid is that it is the pid for node /opt/rh/nodejs010/root/us..... The actual pid for my server.js has that pid as it's parent. thanks Rich yes, we launch node under supervisor, so cartridge.pid contains the supervisor pid, not the node process pid, so that makes sense. I'm going to close this for now, but if you're able to reliably recreate it, please send along the repository for the app you're recreating it with and we'll investigate further. Thanks! |