Bug 990313 - [RFE] rhc tail command times out
[RFE] rhc tail command times out
Product: OpenShift Online
Classification: Red Hat
Component: Command Line Interface (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Fabiano Franz
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2013-07-30 17:19 EDT by Gerrit Hübbers
Modified: 2015-05-14 22:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-01-29 19:48:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gerrit Hübbers 2013-07-30 17:19:32 EDT
Description of problem:
(via forum discussion at https://www.openshift.com/forums/openshift/rhc-tail-myapp-first-logs-well-then-silently-stops-logging )

$ rhc --version
rhc 1.11.4

To my observation, the rhc tail command silently stops providing log messages even though new log messages are generated on the remote application.

# on my client shell
$ rhc tail myapp
(steady logging from remote application appears)
(some time later)
(logging still fine)
(some more time later)
(no more logging, but process still running)

When logging silently stops, no error messages are generated, and the rhc tail process is still running.

To an observer, it looks as if currently no new log messages are generated, even though in fact, they are generated. 

This behavior complicates remote debugging and remote activity observation. It requires to manually re-connect by terminating the logging process and running "rhc tail myapp" again from time to time.

A default usage of "rhc tail anyapp" expects to have logging go on indefinetly until requested explicitly to be terminated. Therefore, it is good if "rhc tail anyapp" logs indefinetly.

A current workaround is: 
$ rhc ssh myapp
# sshing to remote application, providing credentials

# on remote application
$ unset TMOUT
# no more logout after idle time

$ tail_all

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

Steps to Reproduce:
1. On local machine, run
   $ rhc tail myapp

Actual results:
After some time, no new logging messages appear, even though they are generated on the remote application.

Expected results:
Logging shall run indefinitely, until rhc tail process terminates.
Comment 1 Fabiano Franz 2013-12-18 12:44:40 EST
Please test and try to reproduce. This is probably already fixed in prod.
Comment 2 weiwei jiang 2013-12-19 01:05:23 EST
Tried on devenv_4154 and PROD with rhc-1.19.2, can not reproduce this issue, so verified this issue.

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