Issue with Wazuh Kubernetes Deployment

240 views
Skip to first unread message

Heni Kamoun

unread,
Apr 25, 2024, 5:51:16 AM4/25/24
to Wazuh | Mailing List
root@ansible:~# kubectl logs wazuh-indexer-0 -n wazuh
Defaulted container "wazuh-indexer" out of: wazuh-indexer, volume-mount-hack (init), increase-the-vm-max-map-count (init)
i saw somoene here had the same problem  i changed   -Xms and -Xmx parameters to 
env:
            - name: OPENSEARCH_JAVA_OPTS
              value: '-Xms2g -Xmx2g -Dlog4j2.formatMsgNoLookups=true' root@ansible:~# cat /proc/sys/vm/max_map_count
262144 root@ansible:~# kubectl get pods -n wazuh
NAME                              READY   STATUS                   RESTARTS   AGE
wazuh-dashboard-d64f8cb69-5hh87   0/1     ContainerStatusUnknown   1          16h
wazuh-dashboard-d64f8cb69-8shx5   0/1     ContainerStatusUnknown   1          16h
wazuh-dashboard-d64f8cb69-dkmcw   0/1     ContainerStatusUnknown   1          16h
wazuh-dashboard-d64f8cb69-vktbg   1/1     Running                  0          16h
wazuh-indexer-0                   0/1     Pending                  0          16h
wazuh-manager-master-0            0/1     Pending                  0          16h
wazuh-manager-worker-0            0/1     Pending                  0          16h

Ujunwa Okonkwo

unread,
Apr 25, 2024, 7:25:52 AM4/25/24
to Wazuh | Mailing List
Hello Heni,

Please clarify on what the issue you are encountering, as your message seems incomplete.

Regards

Ujunwa Okonkwo

unread,
Apr 30, 2024, 8:03:29 AM4/30/24
to Wazuh | Mailing List
Hi,

It looks like you're encountering an issue with a Kubernetes pod running the Wazuh manager (wazuh-indexer) and trying to view its logs using kubectl logs. Also, the error message you provided indicates that the container "wazuh-indexer" defaulted and there are multiple containers in the pod (volume-mount-hack (init), increase-the-vm-max-map-count (init)).

If this is the issue you are having, try the following:
Use kubectl logs command with the specific container name (wazuh-indexer) to view the logs and check if the pod is healthy and running to fetch the logs successfully.
Inspect the parameters, if you need to adjust Java's heap memory settings
After modifying the pod configuration, apply the changes using kubectl apply -f

Please provide additional information for a more accurate resolution.

Regards,

Reply all
Reply to author
Forward
0 new messages