Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitnami ELK #1514

Closed
ez7ezdt opened this issue Apr 29, 2024 · 5 comments
Closed

Bitnami ELK #1514

ez7ezdt opened this issue Apr 29, 2024 · 5 comments
Assignees
Labels
elk how-to How to issues reported by users solved stale 15 days without activity triage Triage is needed

Comments

@ez7ezdt
Copy link

ez7ezdt commented Apr 29, 2024

Describe your issue as much as you can

I have a running bitnami ELK stack running in Hyper-V in AZURE. I exported the VM to be able to run on a standalone PC. Everything worked except when i try to connect to elasticsearch via the web browser i get the message "Kibana server is not ready yet" I have spent days searching for a solution and nothing i do works. I ran the bndiagnostic-0.9.17-linux-x64.run to collect the data bundle, the message at the end said this.....

The diagnostic bundle was uploaded successfully to the Bitnami servers. Please copy the following code:

c3550208-6088-6730-2e43-b120b1afbeb8

And paste it in your Bitnami Support ticket.

Hopefully you can help.

Cheers

@ez7ezdt ez7ezdt added the how-to How to issues reported by users label Apr 29, 2024
@github-actions github-actions bot added the triage Triage is needed label Apr 29, 2024
@gongomgra
Copy link
Collaborator

Hi @ez7ezdt,

Thanks for using Bitnami. I checked your bndiagnostic information and it looks like your machine is running out of memory, which can cause that the services weren't properly initialized

-----------------------------------
Display amount of free and used memory in the system
-----------------------------------
Running: free -m
In: /opt/bitnami

Output:

              total        used        free      shared  buff/cache   available
Mem:           2938        2369         129           4         439         384
Swap:             0           0           0

-----------------------------------
Get the ctlscript status
-----------------------------------
Running: ./ctlscript.sh status
In: /opt/bitnami
Error: child process exited abnormally
Exitcode: 1

I also don't know how the export feature in Azure cloud work, but we provide a download link for a virtual-machine in our website. Can you give it a try?

https://bitnami.com/stack/elk/virtual-machine

You can get more information on how to get started and how to use the virtual-machine solution from our documentation website at https://docs.bitnami.com/virtual-machine/apps/elk/

@gongomgra gongomgra added the elk label Apr 29, 2024
@ez7ezdt
Copy link
Author

ez7ezdt commented Apr 29, 2024

Thanks for the prompt response. When i say i exported the VM from AZURE i actually copied the VM files frm Azure to my PC and then created a new VM in Hyper-V manager and switched out the .vhdx and .avhdx file.

I also increased the VM memory to 16Gig and had the same issue.

I have seen your updated VM's on your website but i needed this one in particular as it has a a unique dataset which was injested some time ago.

I will add more memory and upload the bndiagnostic file again if that's ok.

@gongomgra
Copy link
Collaborator

Hi @ez7ezdt,

Thanks for your message. As mentioned in my previous message, I'm afraid I don't know if that export/import method you used properly configured the machine on first boot. Kibana dashboard is password protected for security reasons. You can try to make it public following the steps in the next link

https://docs.bitnami.com/virtual-machine/apps/elk/configuration/disable-kibana-auth/

Can you also try to init our virtual-machine from scratch? I have found an official Elasticsearch tool to import and export data that may be of help for you

https://github.com/elasticsearch-dump/elasticsearch-dump

In case you need to run the bndiagnostic tool again, please run it with sudo so it gets access to all the required files.

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label May 17, 2024
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
elk how-to How to issues reported by users solved stale 15 days without activity triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants