can't install sg kibana 6.5.2 plugin

22 views
Skip to first unread message

Roman Kournjaev

unread,
Dec 10, 2018, 8:13:49 PM12/10/18
to Search Guard Community Forum
Is that a know issue ? 

FROM alpine:3.8

ARG KIBANA_VERSION
ENV KIBANA_VERSION=${KIBANA_VERSION}
ENV SG_VERSION=16
RUN apk --update add bash curl wget && \
   mkdir /opt && \
   apk add nodejs && \
   rm -rf /opt/kibana-${KIBANA_VERSION}-linux-x86_64/node && \
   mkdir -p /opt/kibana-${KIBANA_VERSION}-linux-x86_64/node/bin && \
   ln -sf /usr/bin/node /opt/kibana-${KIBANA_VERSION}-linux-x86_64/node/bin/node

   rm "/opt/kibana-${KIBANA_VERSION}-linux-x86_64/config/kibana.yml" && \
   rm -rf /var/cache/apk/*



 

Step 6/16 : RUN /opt/kibana-${KIBANA_VERSION}-linux-x86_64/bin/kibana-plugin install "https://oss.sonatype.org/content/repositories/releases/com/floragunn/search-guard-kibana-plugin/${KIBANA_VERSION}-${SG_VERSION}/search-guard-kibana-plugin-${KIBANA_VERSION}-${SG_VERSION}.zip" &&     rm "/opt/kibana-${KIBANA_VERSION}-linux-x86_64/config/kibana.yml" &&     rm -rf /var/cache/apk/*
 ---> Running in 6d192f9daf82
Transferring 2059942 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Optimizing and caching browser bundles...
The command '/bin/sh -c /opt/kibana-${KIBANA_VERSION}-linux-x86_64/bin/kibana-plugin install "https://oss.sonatype.org/content/repositories/releases/com/floragunn/search-guard-kibana-plugin/${KIBANA_VERSION}-${SG_VERSION}/search-guard-kibana-plugin-${KIBANA_VERSION}-${SG_VERSION}.zip" &&     rm "/opt/kibana-${KIBANA_VERSION}-linux-x86_64/config/kibana.yml" &&     rm -rf /var/cache/apk/*' returned a non-zero code: 137
make: *** [image_build] Error 137


6.5.1 obviously works 


Search Guard

unread,
Dec 11, 2018, 5:45:48 AM12/11/18
to Search Guard Community Forum
try with "--no-optimize" like


Another option is to give the process more memory with
NODE_OPTIONS="--max-old-space-size=8192"
(but its not working very good inside Docker)

Roman Kournjaev

unread,
Dec 11, 2018, 12:35:29 PM12/11/18
to search...@googlegroups.com
whats the meaning of `--no-optimize` , also the startup process of 6.5.1 with SG where it optimizes caches can take 30 min on kubernetes , is that also a known issue ?


--
You received this message because you are subscribed to a topic in the Google Groups "Search Guard Community Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/search-guard/NPrqyyMlh0c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/699516fc-eda9-4ae3-8d4b-be2799f98f12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

SG

unread,
Dec 11, 2018, 12:43:30 PM12/11/18
to search...@googlegroups.com
If you add "--no-optimize" when installing a plugin then the optimization process (that is: webpack) is postponed to the first start of kibana server.
This work, whyever, better in Docker. The whole thing ist that the optimization process is flaky and from Search Guard perspective we cannot do anything here.
The installation of other plugins in kibana is suffering as well from this.
> You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
> To post to this group, send email to search...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/CAPtxm6UC10oXowLfwGk_0atbDznryN5jm1p4qpdZbLeF_sZZjQ%40mail.gmail.com.

Roman Kournjaev

unread,
Dec 11, 2018, 1:20:58 PM12/11/18
to search...@googlegroups.com
This is strange whenever i had it turned on during the docker build the optimization process was still performed during the startup and took like 30 min.


Srinivas Karavadi

unread,
Feb 16, 2019, 2:06:29 AM2/16/19
to Search Guard Community Forum
May be too late , not sure how much RAM your Kibana instance has, to speed up the process 

export NODE_OPTIONS="--max-old-space-size=4096" .

and install the plugin

I had similar issues with X-Pack, the easy fix was to provide more heap to node process
Reply all
Reply to author
Forward
0 new messages