Unable to start Kiban

[Savagepony]

I am unable to start Kibana completely and the browser throws a message Kibana Server not yet ready. I am getting the error about the javascript heap out of memory as in the below screenshot. I am also getting the error "Browserslist: caniuse-lite is outdated. Please run next command npm update caniuse-lite browserslist" I understand this is a bug. My main concern is about the heap out of memory and not starting kibana.

an FYI I am using Searchguard Plugin

[Screenshot here]

**Kibana Version: kibana-6.5.4-linux-x86_64]

[jbudz]

@Savagepony kibana's running pretty close to the max memory limit in node. We have #19678 for tracking memory improvements

To get you running short term, can you try giving the process more memory?

NODE_OPTIONS=--max-old-space-size=4096 bin/kibana

I'm going to close this to keep discussions in the same place, but feel free to ping me here (or at #19678)

[Savagepony]

Hi Jonathan, Thanks for your reply, I have updated the NODE_OPTIONS one of the thread in elastic said the format of --max-old-space-size=4096 has been changed to "--max_old_space_size=4096" for the version 6.5.4 I have updated this configuration in /bin/Kibana file as in below screenshot.. Please let me know if this is the right file to update with this configuration. Even after this change it still throws me the same error below is the screenshot. /bin/kibana file: [image: image.png] Error: [image: image.png] Thanks Anish

[jbudz]

@Savagepony hey, the screenshots didn't upload unfortunately, so taking a guess :). You don't have to edit any files, it can be prefixed to the ./bin/kibana command

[Savagepony]

I tworked, Thank you so much Jonathan, you were a great help. Thanks Anish

…

On Tue, Mar 19, 2019 at 1:35 PM Jonathan Budzenski ***@***.***> wrote: @Savagepony <https://github.com/Savagepony> hey, the screenshots didn't upload unfortunately, so taking a guess :). You don't have to edit any files, it can be prefixed to the ./bin/kibana command — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33451 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AucMdaw9kO0irNI94f7_4EOp0b_JgEUFks5vYS37gaJpZM4b6y5Z> .

[Savagepony]

Jonathan, quick question did we give 4gb RAM for Kibana or is it the DISK space which we alloted? Thanks Anish

…

On Tue, Mar 19, 2019 at 3:40 PM Anish Reddy ***@***.***> wrote: I tworked, Thank you so much Jonathan, you were a great help. Thanks Anish On Tue, Mar 19, 2019 at 1:35 PM Jonathan Budzenski < ***@***.***> wrote: > @Savagepony <https://github.com/Savagepony> hey, the screenshots didn't > upload unfortunately, so taking a guess :). You don't have to edit any > files, it can be prefixed to the ./bin/kibana command > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#33451 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AucMdaw9kO0irNI94f7_4EOp0b_JgEUFks5vYS37gaJpZM4b6y5Z> > . >

[jbudz]

@Savagepony 4gb of RAM. It's a one time thing for the bundling process to rerun after a config charge, so you can remove it after. Disk should be fairly consistent at < 1 gb.

[Savagepony]

Thanks Jonathan, do you have any idea about the below error? I am getting this error on console in filebeats server while creating logging index Exiting: Couldn't connect to any of the configured Elasticsearch hosts. Errors: [Error connection to Elasticsearch https://localhost:9200: Get https://localhost :9200: dial tcp 127.0.0.1:9200: connectex: No connection could be made because the target machine actively refused it] I am following the instruction provided in the kibana under logs tab and under logs I selected elasticsearch logs and then it said "looks like you don have any logging indices" and then it gave an option setup instructions Your help is greatly appreciated. Thanks

…

On Fri, Mar 22, 2019 at 9:34 AM Jonathan Budzenski ***@***.***> wrote: @Savagepony <https://github.com/Savagepony> 4gb of RAM. It's a one time thing for the bundling process to rerun after a config charge, so you can remove it after. Disk should be fairly consistent at < 1 gb. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33451 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AucMdU3VqnrtM2fGOaZLKeHnpFcoKribks5vZOoMgaJpZM4b6y5Z> .

[jbudz]

That's a tough one, it could be several things. Are you able to access elasticsearch from the filbeat machine? It's running ES on localhost?

[Savagepony]

I tried to telnet to Elasticsearch on port 9200 from the filebeats server but it wouldn't connect. Is there any other way that I could test? Elasticsearch is on a different server (RHEL) and Filebeats on different server. I dont see anything on Elasticsearch logs nor in the Filebeats logs exceptht eh error message from my previous email. Thanks Anish

…

On Tue, Mar 26, 2019 at 9:40 AM Jonathan Budzenski ***@***.***> wrote: That's a tough one, it could be several things. Are you able to access elasticsearch from the filbeat machine? It's running ES on localhost? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33451 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AucMdSmWUhtmLKj_HzUhiRjNryMYf3Pjks5vajFggaJpZM4b6y5Z> .