pro-akim
commented
1 year ago Update
A new error is appearing when Manager is trying to be installed in the container:
TASK [roles/master-role : Install master] **************************************************************
fatal: [wazuh-master]: FAILED! => changed=true
cmd: ./install.sh
delta: '0:00:04.130157'
end: '2023-10-16 17:25:15.535975'
msg: non-zero return code
rc: 1
start: '2023-10-16 17:25:11.405818'
stderr: |-
Makefile:2515: warning: overriding recipe for target 'win32/ui_resource.o'
Makefile:2455: warning: ignoring old recipe for target 'win32/ui_resource.o'
Makefile:2518: warning: overriding recipe for target 'win32/auth_resource.o'
Makefile:2458: warning: ignoring old recipe for target 'win32/auth_resource.o'
Makefile:2515: warning: overriding recipe for target 'win32/ui_resource.o'
Makefile:2455: warning: ignoring old recipe for target 'win32/ui_resource.o'
Makefile:2518: warning: overriding recipe for target 'win32/auth_resource.o'
Makefile:2458: warning: ignoring old recipe for target 'win32/auth_resource.o'
In file included from /wazuh/src/data_provider/src/sysInfoLinux.cpp:15:
/wazuh/src/data_provider/src/packages/modernPackageDataRetriever.hpp: In static member function 'static void ModernFactoryPackagesCreator<true>::getPackages(const std::map<std::__cxx11::basic_string<char>, std::set<std::__cxx11::basic_string<char> > >&, std::function<void(nlohmann::json_abi_v3_11_2::basic_json<>&)>)':
/wazuh/src/data_provider/src/packages/modernPackageDataRetriever.hpp:53:18: error: cannot deduce template arguments for 'PYPI' from ()
PYPI().getPackages(paths.at("PYPI"), callback);
^
/wazuh/src/data_provider/src/packages/modernPackageDataRetriever.hpp:54:17: error: cannot deduce template arguments for 'NPM' from ()
NPM().getPackages(paths.at("NPM"), callback);
^
make[4]: *** [CMakeFiles/sysinfo.dir/build.make:167: CMakeFiles/sysinfo.dir/src/sysInfoLinux.cpp.o] Error 1
make[3]: *** [CMakeFiles/Makefile2:73: CMakeFiles/sysinfo.dir/all] Error 2
make[2]: *** [Makefile:95: all] Error 2
make[1]: *** [Makefile:1673: build_sysinfo] Error 2
make: *** [Makefile:791: server] Error 2
stderr_lines: <omitted>
stdout: |2-
Wazuh v4.7.0 (Rev. 40701) Installation Script - https://www.wazuh.com
You are about to start the installation process of Wazuh.
You must have a C compiler pre-installed in your system.
- System: Linux wazuh-master 5.19.0-1025-aws (debian 10.0)
- User: root
- Host: wazuh-master
-- Press ENTER to continue or Ctrl-C to abort. --
- Installation will be made at /var/ossec .
3- Configuring Wazuh.
3.1- Do you want e-mail notification? (y/n) [n]:
--- Email notification disabled.
3.2- Do you want to run the integrity check daemon? (y/n) [y]:
- Not running syscheck (integrity check daemon).
3.3- Do you want to run the rootkit detection engine? (y/n) [y]:
- Not running rootcheck (rootkit detection).
3.5- Active response allows you to execute a specific
command based on the events received.
By default, no active responses are defined.
- Default white list for the active response:
- 127.0.0.11
- Do you want to add more IPs to the white list? (y/n)? [n]:
3.6- Do you want to enable remote syslog (port 514 udp)? (y/n) [y]:
- Remote syslog enabled.
3.7 - Do you want to run the Auth daemon? (y/n) [y]:
- Running Auth daemon.
3.8- Do you want to start Wazuh after the installation? (y/n) [y]:
- Wazuh will start at the end of installation.
3.9- Setting the configuration to analyze the following logs:
-- /var/ossec/logs/active-responses.log
-- /var/log/dpkg.log
- If you want to monitor any other file, just change
the ossec.conf and add a new localfile entry.
Any questions about the configuration can be answered
by visiting us online at https://documentation.wazuh.com/.
--- Press ENTER to continue ---
4- Installing the system
DIR="/var/ossec"
- Running the Makefile
make build_sysinfo build_shared_modules build_syscollector
make[1]: Entering directory '/wazuh/src'
cd data_provider/ && mkdir -p build && cd build && cmake .. && make
cd shared_modules/dbsync/ && mkdir -p build && cd build && cmake .. && make
-- Configuring done
-- Configuring done
-- Generating done
-- Generating done
-- Build files have been written to: /wazuh/src/data_provider/build
-- Build files have been written to: /wazuh/src/shared_modules/dbsync/build
make[2]: Entering directory '/wazuh/src/data_provider/build'
make[2]: Entering directory '/wazuh/src/shared_modules/dbsync/build'
make[3]: Entering directory '/wazuh/src/shared_modules/dbsync/build'
make[3]: Entering directory '/wazuh/src/data_provider/build'
make[4]: Entering directory '/wazuh/src/shared_modules/dbsync/build'
make[4]: Entering directory '/wazuh/src/data_provider/build'
make[4]: Leaving directory '/wazuh/src/shared_modules/dbsync/build'
make[4]: Leaving directory '/wazuh/src/data_provider/build'
make[4]: Entering directory '/wazuh/src/data_provider/build'
[ 60%] Built target dbsync
make[4]: Entering directory '/wazuh/src/shared_modules/dbsync/build'
[ 7%] Building CXX object CMakeFiles/sysinfo.dir/src/sysInfoLinux.cpp.o
make[4]: Entering directory '/wazuh/src/shared_modules/dbsync/build'
make[4]: Leaving directory '/wazuh/src/shared_modules/dbsync/build'
make[4]: Leaving directory '/wazuh/src/shared_modules/dbsync/build'
[ 80%] Built target dbsync_example
[100%] Built target dbsync_test_tool
make[3]: Leaving directory '/wazuh/src/shared_modules/dbsync/build'
make[2]: Leaving directory '/wazuh/src/shared_modules/dbsync/build'
cd shared_modules/rsync/ && mkdir -p build && cd build && cmake .. && make
-- Configuring done
-- Generating done
-- Build files have been written to: /wazuh/src/shared_modules/rsync/build
make[2]: Entering directory '/wazuh/src/shared_modules/rsync/build'
make[3]: Entering directory '/wazuh/src/shared_modules/rsync/build'
make[4]: Entering directory '/wazuh/src/shared_modules/rsync/build'
make[4]: Leaving directory '/wazuh/src/shared_modules/rsync/build'
[ 37%] Built target rsync
make[4]: Entering directory '/wazuh/src/shared_modules/rsync/build'
make[4]: Leaving directory '/wazuh/src/shared_modules/rsync/build'
[100%] Built target rsync_test_tool
make[3]: Leaving directory '/wazuh/src/shared_modules/rsync/build'
make[2]: Leaving directory '/wazuh/src/shared_modules/rsync/build'
make[4]: Leaving directory '/wazuh/src/data_provider/build'
make[3]: Leaving directory '/wazuh/src/data_provider/build'
make[2]: Leaving directory '/wazuh/src/data_provider/build'
make[1]: Leaving directory '/wazuh/src'
Error 0x5.
Building error. Unable to finish the installation.
stdout_lines: <omitted>
PLAY RECAP *********************************************************************************************
localhost : ok=11 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
wazuh-master : ok=4 changed=1 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 
davidjiglesias
The following issue aims to run all
system testsfor the current release candidate, report the results, and open new issues for any encountered errors.System tests information
Instructions
To run tests in an AWS EC2 virtual environment, the following requirements will need to be met:
These requirements should be requested to the @wazuh/cicd team via https://github.com/wazuh/internal-devel-requests.
For further information, check https://github.com/wazuh/wazuh-qa/tree/master/tests/system/README.md
Test report procedure
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause. It must be included in the
Fixessection of the current release candidate main issue.Any expected fail or skipped test must have an issue justifying the reason. All auditors must validate the justification for an expected fail or skipped test.
An extended report of the test results must be attached as a zip or txt. This report can be used by the auditors to dig deeper into any possible failures and details.
Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
Conclusion WIP