Bug 787119 - Failed to thread dump ruby app with ruby client
Summary: Failed to thread dump ruby app with ruby client
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: oc
Version: 1.x
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Bill DeCoste
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-03 08:37 UTC by Xiaoli Tian
Modified: 2012-02-17 02:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-17 02:07:09 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Xiaoli Tian 2012-02-03 08:37:10 UTC
Description of problem:

Encountered" Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support" while trying to thread dump 
ruby app with ruby client

Version-Release number of selected component (if applicable):
rhc-cartridge-rack-1.1-0.85.12-1.el6_2.noarc
rhc-0.85.11-1.el6_2.noarch
Current stage


How reproducible:
Always

Steps to Reproduce:
1.Create a ruby app with rhc app create -a appstage0 -t ruby-1.8 
2.Try to thread dump it with rhc app threaddump -a appstage0
  
Actual results:
Failed to thread dump but said the application is stopped(see debug info below)

Expected results:
Thread dump ruby app successfully

Additional info:

Debug info via #rhc app threaddump -a appstage0 -d
DEBUG:
Application is stopped
Cartridge return code: 1

Exit Code: 1
broker_c: namespacerhloginsshapp_uuiddebugaltercartridgecart_typeactionapp_nameapi
api_c: placeholder
API version:    1.1.2
Broker version: 1.1.1

RESULT:
Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support.

But actually the app is active not stopped

Comment 1 Xiaoli Tian 2012-02-03 10:06:15 UTC
Very funny that after waiting for a long time(about 2 or 3 hours), this issue does not exist any more, we could thread dump ruby app successfully now with the same steps ,not sure the reason, leave the bug open for you to check if something wrong happened in stage during this period.

Comment 2 Alex Boone 2012-02-03 12:44:15 UTC
See comments for bug 786759, I suspect these are related.  Perhaps if the app hasn't been started to allow for a thread dump, we could provide a more friendly message to the client.

Comment 3 Bill DeCoste 2012-02-03 13:13:52 UTC
Good suggestion. I'll add details for the app not being started to the error message.

Comment 4 Bill DeCoste 2012-02-03 14:06:54 UTC
added "Application is stopped. Ruby/Rack applications must be started by accessing the URL for a thread dump" message to failure.

Comment 5 Meng Bo 2012-02-06 09:44:56 UTC
verified with rhc-cartridge-rack-1.1-0.86.1-1.el6_2.noarch on devenv_1581,
addition information can be found in the output.


Note You need to log in before you can comment on or make changes to this bug.