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

ERROR3099 - Some Wazuh daemons are not ready yet in node "wazuh-manager-master" (wazuh-modulesd->failed) #816

Open
abel408 opened this issue Sep 11, 2024 · 3 comments

Comments

@abel408
Copy link

abel408 commented Sep 11, 2024

Environment:
Wazuh: 4.9.0
Kubernetes: v1.27.16
Ubuntu 22.04.4 LTS

I've followed the guide to install Wazuh with Kubernetes here: https://documentation.wazuh.com/current/deployment-options/deploying-with-kubernetes/kubernetes-deployment.html

After install, I am able to log into the dashboard initially, but after 10 or so minutes, I'm presented with the following:

INFO: Current API id [1513629884013] INFO: Checking current API id [1513629884013]... INFO: Current API id [1513629884013] has some problem: 3002 - Request failed with status code 400 INFO: Getting API hosts... INFO: API hosts found: 1 INFO: Checking API host id [1513629884013]... INFO: Could not connect to API id [1513629884013]: 3099 - ERROR3099 - Some Wazuh daemons are not ready yet in node "wazuh-manager-master" (wazuh-modulesd->failed) INFO: Removed [navigate] cookie ERROR: No API available to connect

This seems related to this comment: wazuh/wazuh#5068 (comment)

Restarting Wazuh or redeploying the master node seems to fix the issue, but only temporarily.

@aaniqtejani
Copy link

Im facing similar issue when deploying Wazuh through custom helm chart on AWS.

@stephane-segning
Copy link

Hello! I'm having 3 different setup & environments, totally different but still having this issue with version 4.8.2 and 4.9.2. The main thing, is that they're deployed using Kubernetes.

When doing tests with docker in single mode, no problem. When trying in multi-mode, error!

Steps to reproduce:

  1. Create a VM (it's better for tests isolation). Me I'm using Proxmox or Multipass, and AWS EKS.
  2. Clone the project from
  1. Configure the project as specified in the READMEs files and admire the Dashboard work for 2m, then fail because the above error in the manager.

Please any help would be appreciated.

@dedsxc
Copy link

dedsxc commented Nov 28, 2024

Facing the same issue with errors:

ERROR3099 - Some Wazuh daemons are not ready yet in node "wazuh-manager-master" (wazuh-modulesd->failed)

After digging a bit, I found this in logs

wazuh-modulesd:database: CRITICAL: Couldn't init inotify: Too many open files.

Solution: I increase the max_user_instances (default values is 128) by adding this initContainer to manager pod :

initContainers:
  - command:
    - /bin/sh
    - -c
    - sysctl -w fs.inotify.max_user_instances=512
    image: busybox
    name: set-sysctl
    securityContext:
      privileged: true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants