Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-22005

Log console: Unexpected EOF in pod log

XMLWordPrintable

    • devex #113 April 2016
    • 1
    • Hide

      ASSERT: Have an application on OpenShift and open log of an application pod.
      EXEC: Make sure there is a lot of entries in pod log.

      RESULT: Pod log went "out of memory".
      EXPECTED RESULT: Pod is streaming all the time (maybe beginning of log in console could be cut of to allow more output in console - it would happen continuously to ensure there is still enough place for log).

      Show
      ASSERT: Have an application on OpenShift and open log of an application pod. EXEC: Make sure there is a lot of entries in pod log. RESULT: Pod log went "out of memory". EXPECTED RESULT: Pod is streaming all the time (maybe beginning of log in console could be cut of to allow more output in console - it would happen continuously to ensure there is still enough place for log).

      I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.

      Last lines from console (output of application pod log)

      ...
�[0m�[33m09:27:29,845 WARN  [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSelector=application%3Deap-app]]
error: unexpected EOF

      I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.

            jcantril@redhat.com Jeffrey Cantrill
            mlabuda_jira Marián Labuda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: