Centralized configuration

41 views
Skip to first unread message

Max Kirshin

unread,
Feb 19, 2026, 1:49:53 AM (5 days ago) Feb 19
to Wazuh | Mailing List
Hello Wazuh team and community
Please, help with issue faced during Centralized configuration implementation.
I've tried to push configuration and SCA policies using way described in "Download configuration files from remote location". I use Ubuntu, latest available Docker and Wazuh 4.14.3 single-node. I've added file "files.yml" and described it in docker-compose. This file seems to work: the group has been created and I've seen "2026/02/19 05:38:55 wazuh-remoted: INFO: Successfully parsed of yaml file: etc/shared/files.yml" in ossec.log.
But there are no files in the created group except ar.conf (and merged.mg that contains only ar.conf). Also, the attemp to view configuration agent.conf shows the error like permission or file lack.
There are these errors in the log:
2026/02/19 05:39:05 wazuh-remoted: ERROR: Cannot connect to the download module socket. External shared file download is not available.
2026/02/19 05:39:17 wazuh-remoted: ERROR: Couldn't open file 'var/download/agent.conf'
2026/02/19 05:39:18 wazuh-remoted: ERROR: Couldn't open file 'var/download/win_bitlocker.yml'.
For these files I use Github and it's permalink. I've checked with curl that they are available for downloading

Ian Yenien Serrano

unread,
Feb 19, 2026, 3:40:57 PM (5 days ago) Feb 19
to Wazuh | Mailing List
Hi Max, I'll look into it and let you know when I find out anything. In the meantime, could you send me the logs from before and after the error in case there's any more information?

Ian Yenien Serrano

unread,
Feb 20, 2026, 6:51:55 AM (4 days ago) Feb 20
to Wazuh | Mailing List
Can you verify that wazuh-modulesd is working?

You can test it by running: systemctl status wazuh-manager.


systemctl status wazuh-manager
● wazuh-manager.service - Wazuh manager
     Loaded: loaded (/usr/lib/systemd/system/wazuh-manager.service; enabled; preset: disabled)
     Active: active (running) since Fri 2026-02-20 11:44:15 UTC; 3min 34s ago
 Invocation: 88539c68010547fb9383bbc8672a5c94
      Tasks: 211 (limit: 36730)
     Memory: 2.8G (peak: 3.1G)
        CPU: 1min 29.257s
     CGroup: /system.slice/wazuh-manager.service
             ├─11834 /var/ossec/framework/python/bin/python3 /var/ossec/api/scripts/wazuh_apid.py
             ├─11835 /var/ossec/framework/python/bin/python3 /var/ossec/api/scripts/wazuh_apid.py
             ├─11836 /var/ossec/framework/python/bin/python3 /var/ossec/api/scripts/wazuh_apid.py
             ├─11839 /var/ossec/framework/python/bin/python3 /var/ossec/api/scripts/wazuh_apid.py
             ├─11842 /var/ossec/framework/python/bin/python3 /var/ossec/api/scripts/wazuh_apid.py
             ├─11885 /var/ossec/bin/wazuh-authd
             ├─11900 /var/ossec/bin/wazuh-db
             ├─11933 /var/ossec/bin/wazuh-execd
             ├─11952 /var/ossec/bin/wazuh-analysisd
             ├─11962 /var/ossec/bin/wazuh-syscheckd
             ├─11978 /var/ossec/bin/wazuh-remoted
             ├─12044 /var/ossec/bin/wazuh-logcollector
             ├─12086 /var/ossec/bin/wazuh-monitord
             └─12137 /var/ossec/bin/wazuh-modulesd

Reply all
Reply to author
Forward
0 new messages