Indexer crash loop without providing error message #879
Comments
|
Possibly related to this? #839 |
|
Some further info on this. I've now brought my deployment manifests exactly in line with what is found here: https://github.com/wazuh/wazuh-kubernetes/tree/v4.9.1/wazuh I.e. I am generating certs using the code provided there, and am using all the hardcoded secrets as per the manifests. The only thing I have changed is the StorageClass, since in the example code it is not actually a valid resource. I have defined that as follows (in order to provision Azure Disks): apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: wazuh-storage
provisioner: disk.csi.azure.com
parameters:
skuName: Standard_LRS
cachingMode: ReadWrite
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: trueI am still get the exact same behaviour on the indexer (i.e. it restarts without any error message after around 60 seconds), so I can pretty much exclude the possibility that this is being caused by any custom configurations I have made. Have also tried #839 (since that seems to be a fix that should create more stability and prevent a crash loop if indexer-0 unexpectedly crashes) but that does not resolve it since the root reason for the crash still appears to be something else. |
|
Same problem here on v4.9.2
this message is now gone but still the same behavior Only changes (except masterkey) I made was also to change the storage class Here are also my logs
|
|
as mentioned here: wazuh/wazuh-packages#1511 still same behavior |
|
Ok found the problem: |
|
Yes, I also found this. I got stuck on the next thing soon after though.
…On Wed, 13 Nov 2024 at 11:58, Steve Berthold ***@***.***> wrote:
Ok found the problem:
in the generated manifests the ressource limits for the indexer are too
low (around 1.5Gi RAM).
Increased this to 4Gi and it works now!
—
Reply to this email directly, view it on GitHub
<#879 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGBE4OAKM25GFCDJHM7IVXL2AMWGNAVCNFSM6AAAAABQ6S3UUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZTGE4TOOJXGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I am deploying Wazuh based on the kubernetes manifests in this repo. I've made adjustments in order to generate secure credentials instead of using the hardcoded secrets, and also to generate TLS certs using certificate manager. But other than that the manifests are pretty much the same as the example ones provided.
I am deploying v4.9.1.
Dashboard and manager (master plus workers) start up correctly. But the indexer is in a crash loop. It starts up, runs for about 60 seconds and then restarts. It does not provide any error messages that would indicate the reason for the crash, which makes it extremely hard to debug.
There are a lot of warnings, but since those are unlikely to have anything to do with changes I've made, I assume they should not play any kind of important role here.
Here are the complete logs for one of the pods. Does any of this point to an obvious problem? Or does anyone have suggestions on how I could discover the root problem?
The text was updated successfully, but these errors were encountered: