+++ This bug was initially created as a clone of Bug #1479928 +++ Description of problem: Since the release of the v3.4 of the logging stack, Kibana has been running with v4.x of the nodejs runtime. This version is different from that which is distributed with the Kibana download. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. os rsh $KIBANA_POD 2. ps -ef | grep node 3. with the binary found in 2: node --version Actual results: v4.7.3 Expected results: v6.X Additional info: This maybe contributing to the OOM issues we have with Kibana. Regardless, we should be using the same version as the officially released product
It's fixed, verified with kibana 3.5.0-31, nodejs runtime is now v6.x : # oc rsh logging-kibana-1-9ncs4 Defaulting container name to kibana. sh-4.2$ env | grep VER KIBANA_VER=4.6.4 NODEJS_VERSION=6 sh-4.2$ ps -ef | grep node 1000050+ 11 1 0 06:09 ? 00:00:00 /bin/bash /usr/bin/nodescl-node /usr/share/kibana/src/cli 1000050+ 12 11 0 06:09 ? 00:00:00 scl enable rh-nodejs6 -- node /usr/share/kibana/src/cli 1000050+ 16 13 6 06:09 ? 00:00:02 node /usr/share/kibana/src/cli 1000050+ 37 26 0 06:09 ? 00:00:00 grep node sh-4.2$ /usr/bin/nodescl-node --version v6.9.1 Test env: # openshift version openshift v3.5.5.31.19 kubernetes v1.5.2+43a9be4 etcd 3.1.0 Images tested with: logging-kibana 3.5.0-31 9b248fecf2b4 9 hours ago 613.8 MB
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2670