Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question.
Don’t forget to select tags to help index your topic!
1. Describe your incident:
I have tried twice now to get graylog going. We have a staging proxmox environment where we are running this. It’s a VM with 24 gigs of DDR4 and 16 11th Gen Intel cores. It’ll usually install fine (docker or package based) but will slowly start to hard reset the VM leaving no logs behind as to why. Slowly it will get worse until the VM boots up and immediately gets reset by graylog. Never had this problem with any other VMs and disabling the service/killing the docker container results in no more resets. I want to know how/why/what in this software could possibly need to reset its host without any configurability as to when it happens.
2. Describe your environment:
- OS Information:
Proxmox VM running 22.04, 24GB ram 16 core - Package Version:
6.1 - Service logs, configurations, and environment variables:
There are none
3. What steps have you already taken to try and solve the problem?
Tried increasing data node heap to 8g, making a ram based disk cache, increasing core and memory
4. How can the community help?
Figure out why this might be happening.
Helpful Posting Tips: Tips for Posting Questions that Get Answers [Hold down CTRL and link on link to open tips documents in a separate tab]
they always say when all else fails, contact tech support because then you’ll figure it out on your own. The reason there was no logs in the guest VM is because without much warning our only AVX supporting proxmox node in pre-prod has 32 GB of ram and Having the VM set at 24 is fine until it actually needs it all, then the host server slams into its memory limit and kills the process which just so happens to be a live VM. I assume that as the open search grew it needed more ram on startup until it got so bad that it failed immediately. Ironically enough, lowering the ram to 14GB (so I can put the other VMs back on it as well) fixed the issue. heap is 10GB and jvm config is 2GB. I am going to leave this up so that if anyone loses a day worth of work on this exact same thing they might have a chance of figuring out what’s going on