Bug 872658 - Error Message (shell request failed on channel 0) which using ssh on terminal
Summary: Error Message (shell request failed on channel 0) which using ssh on terminal
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OKD
Classification: Red Hat
Component: oc
Version: 2.x
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-02 16:51 UTC by Rahul Wagh
Modified: 2015-05-15 02:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-03 00:10:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Error message : - shell request failed on channel 0 (109.34 KB, image/png)
2012-11-02 16:51 UTC, Rahul Wagh
no flags Details
Application status on openshift - STOPPED (114.67 KB, image/png)
2012-11-02 16:52 UTC, Rahul Wagh
no flags Details

Description Rahul Wagh 2012-11-02 16:51:48 UTC
Created attachment 637172 [details]
Error message : - shell request failed on channel 0

Description of problem:Getting error message on terminal with the following command
Command : - ssh 99388394a17f4f4c9790c2b4fd452b66.com


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.rhc setup 
To connect to openshift.redhat.com enter your OpenShift login (email or Red Hat login id): |rahul.wagh17| rahul.wagh17
Password: ***********
Note :- working fine no issue

2.rahul@rahul-Inspiron-N4010:~$ rhc domain show
Password: ***********

Note : -working fine no issue

3.rahul@rahul-Inspiron-N4010:~$ ssh 99388394a17f4f4c9790c2b4fd452b66.com
shell request failed on channel 0

Note : - getting the above error
  
Actual results:


Expected results:
Should be able to login into the DIY account using ssh command

Additional info:
The application status in the openshift account is STOPPED
Please find the attached screenshot for the same.

Comment 1 Rahul Wagh 2012-11-02 16:52:36 UTC
Created attachment 637173 [details]
Application status on openshift - STOPPED

Comment 2 Mike McGrath 2012-11-02 21:59:55 UTC
Re-assigning to Jhonce

Jhon, is this something we can have watchman track and correct?  If it's not bug worthy can you open a user story?

This happens because you ran out of process space and we don't handle that very well (yet).  If you issue a force-stop to the app then a start, that should fix it.  If not email me and I'll hit it with a bigger hammer.

Comment 3 Jhon Honce 2012-11-02 23:34:26 UTC
What method would you recommend for Watchman to determine a gear is in this state?


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