![Wazuh 是否可以为低于规定的最低硬件要求的单个代理工作?](https://linux22.com/image/781676/Wazuh%20%E6%98%AF%E5%90%A6%E5%8F%AF%E4%BB%A5%E4%B8%BA%E4%BD%8E%E4%BA%8E%E8%A7%84%E5%AE%9A%E7%9A%84%E6%9C%80%E4%BD%8E%E7%A1%AC%E4%BB%B6%E8%A6%81%E6%B1%82%E7%9A%84%E5%8D%95%E4%B8%AA%E4%BB%A3%E7%90%86%E5%B7%A5%E4%BD%9C%EF%BC%9F.png)
我很惊讶地发现 Wazuh 服务器要求规定 2gb 和 2 核是最低要求 - 但我想知道这些数字在多大程度上是为了支持多个代理而定制的。
是否有人使用低于规定的最低要求? 具体来说,我希望为单个 Linux 代理运行它。
答案1
假设您还要安装其他组件(Wazuh Indexer 和 Wazuh Dashboard),您是否要进行 All In One 安装?或者您将 Wazuh Server 组件安装在具有少于 2GB RAM 和 2 个 CPU 核心的不同主机上?
如果您的 Wazuh 服务器与 Wazuh Indexer 和 Wazuh Dashboard 位于不同的主机上,我会说,对于单个代理,仅使用 1GB RAM 和 1 CPU 是安全的,您还必须考虑所使用的操作系统,我在 CentOS7 中执行了大多数测试,只安装了最少的软件包。大约 5 个月前,我在具有 1GB RAM 和 1vCPU 的虚拟机上测试了 Wazuh Indexer,安装后它没有启动,可能配置 JVM 选项可以解决这个问题,但将 RAM 增加到 2GB 就可以让它工作了。
不同的组件需要不同的资源,您可能在文档中注意到了这一点,对于用于监控单个代理的 All In One 安装,我不会将 RAM 和 2vCPU 低于 2GB,在快速入门指南您可以找到推荐的值。
我刚刚用一台有 1GB RAM 和 1vCPU 的 CentOS7 机器进行了测试,有趣的是,我可以使用安装助手安装所有组件,性能不是最好的,但它可以工作,我仍然建议您将分配的资源增加到至少 2GB 和 2 个核心。
[root@wazuhserver ~]# bash wazuh-install.sh -a
10/11/2022 09:51:25 INFO: Starting Wazuh installation assistant. Wazuh version: 4.3.9
10/11/2022 09:51:25 INFO: Verbose logging redirected to /var/log/wazuh-install.log
10/11/2022 09:51:27 ERROR: Your system does not meet the recommended minimum hardware requirements of 4Gb of RAM and 2 CPU cores. If you want to proceed with the installation use the -i option to ignore these requirements.
[root@wazuhserver ~]# bash wazuh-install.sh -a -i
10/11/2022 09:53:47 INFO: Starting Wazuh installation assistant. Wazuh version: 4.3.9
10/11/2022 09:53:47 INFO: Verbose logging redirected to /var/log/wazuh-install.log
10/11/2022 09:53:50 WARNING: Hardware and system checks ignored.
10/11/2022 09:53:53 INFO: Wazuh repository added.
10/11/2022 09:53:53 INFO: --- Configuration files ---
10/11/2022 09:53:53 INFO: Generating configuration files.
10/11/2022 09:53:54 INFO: Created wazuh-install-files.tar. It contains the Wazuh cluster key, certificates, and passwords necessary for installation.
10/11/2022 09:53:54 INFO: --- Wazuh indexer ---
10/11/2022 09:53:54 INFO: Starting Wazuh indexer installation.
10/11/2022 09:55:13 INFO: Wazuh indexer installation finished.
10/11/2022 09:55:13 INFO: Wazuh indexer post-install configuration finished.
10/11/2022 09:55:13 INFO: Starting service wazuh-indexer.
10/11/2022 09:55:46 INFO: wazuh-indexer service started.
10/11/2022 09:55:46 INFO: Initializing Wazuh indexer cluster security settings.
10/11/2022 09:56:08 INFO: Wazuh indexer cluster initialized.
10/11/2022 09:56:08 INFO: --- Wazuh server ---
10/11/2022 09:56:08 INFO: Starting the Wazuh manager installation.
10/11/2022 09:57:16 INFO: Wazuh manager installation finished.
10/11/2022 09:57:16 INFO: Starting service wazuh-manager.
10/11/2022 09:57:37 INFO: wazuh-manager service started.
10/11/2022 09:57:37 INFO: Starting Filebeat installation.
10/11/2022 09:58:25 INFO: Filebeat installation finished.
10/11/2022 09:58:26 INFO: Filebeat post-install configuration finished.
10/11/2022 09:58:27 INFO: Starting service filebeat.
10/11/2022 09:58:27 INFO: filebeat service started.
10/11/2022 09:58:27 INFO: --- Wazuh dashboard ---
10/11/2022 09:58:27 INFO: Starting Wazuh dashboard installation.
10/11/2022 10:00:17 INFO: Wazuh dashboard installation finished.
10/11/2022 10:00:17 INFO: Wazuh dashboard post-install configuration finished.
10/11/2022 10:00:17 INFO: Starting service wazuh-dashboard.
10/11/2022 10:00:17 INFO: wazuh-dashboard service started.
10/11/2022 10:01:40 INFO: Initializing Wazuh dashboard web application.
10/11/2022 10:01:42 INFO: Wazuh dashboard web application initialized.
10/11/2022 10:01:42 INFO: --- Summary ---
10/11/2022 10:01:42 INFO: You can access the web interface https://<wazuh-dashboard-ip>
User: admin
Password: RlT.Fmrk2zvBgSUcHXXwb0?4YeK2t6aU
10/11/2022 10:01:42 INFO: Installation finished.