Error when installing the Wazuh Dashboard using the Installation Assistant #2111
Assignees
Labels
Comments
Update: investigation🟢 4.4.0 All-in-one, RHEL 8, 4GB 2 coresThe first test done using 4.4.0 passsed test logs on Red Hat 8🔴 4.4.0, All-in-one, RHEL 8 1GB 1 coreAnother test using 4.4.0 failed test logs on Red Hat 8🔴 4.4.0, All-in-one, Ubuntu 22 1GB 1 coreIt has also been replicated in an Ubuntu 22, also with 1GB and 1 core: 4.4.0 failed test logs in Ubuntu22🟢 4.4.0, Dashboard node, Ubuntu 22 1GB 1 coreWhen a dashboard node is especifically installed instead of an all-in-one the error is not replicated, as variable 4.4.0 passed test, no AIO🟢 4.3.10 All-in-one, RHEL 8, 4GB 2cores4.3.10 succesful test🔴 4.3.10, All-in-one, Ubuntu 22, 1GB 1 core4.3.10 failed test in ubuntu 22Comparison of the function where the error is in successful and failed runsSuccesful runFailed run |
Update: investigation and solutionTest with more verbose in Ubuntu 22, 1GB 1 coreInvestigationThe error has been followed until function SolutionThe solution consists on applying the same type of changes done by @davidcr01 in PR #2063, and improve the catching of errors in curl, not only in this specific function, but generally in all the files related to the unattended that weren't changed in the mentioned PR. |
Update: testing🟢 4.5.0 All-in-one, RHEL 8, 4GB 2cores4.5.0 all-in-one test passed🟢 4.3.10, Step-by-step, RHEL 8, 1GB 1 coreThe step by step installation has been tested in the step by step but the error is not replicated 4.3.10 successful step by step test🔴 4.5.0 All-in-one, Ubuntu 22, 1GB 1coresIn version 4.5.0, where the solution seen in previous commentaries has already been implemented, the error keeps appearing, which means the curl still doesn't pick up correctly the error. 4.5.0 all-in-one test failed |
Update: solutionsThe changes in the curl calls throughout the script still don't fix the error, as seen in the last test, because the The next solution is to create a retry structure, as it seems it is a timing error because of the fact that the step by step installation doesn't have this problem. When tried, this hipothesis has been proven, as, in the second retry, the token is correctly downloaded: After this error is removed, another error appears, which probably has the same base cause: This error not always appears, as seen in the following test using the same machine, where the installation finished succesfully: The execution of the function where the error appears is the following: After some tests with the script stopped it seems it is a timing problem,as at one point, the curl started working. In a different test, where the script was also stopped, the curl doesn't work at all, but all the rest of the tests done to the installation give the impression everything is correct: |
UpdateThe solution now done for the error in function With the current changes, this is the output of the installation: Another problem right now is that the script doesn't exit as it should, with the rollBack, it just stops executing at that point. |
UpdateAfter more tests, it has been discovered the problem didn't come from function Complete installationTestingThe new code has been tested successfully in the following systems, using less memory than the recommended to force it:
|
|
After being related to issue #2115, the priority of this issue has changed to Urgent and the base branch has been changed to 4.4, so a new Pull Request has been created: https://github.com/wazuh/wazuh-packages/pull/2117/checks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When installing the Wazuh dashboard using the installation assistant on Red Hat 8, it stops with two errors:
It has been also reproduced in a community question. It may have something to do with the merge of PR #1806, as it was explained by @miguelfdez99 in Slack that the error appeared when testing the PR.
For now, it has just appeared on Red Hat 8 using the all in one installation of the installation assistant, more testing is needed, especially to see if it happens on
4.4.0The text was updated successfully, but these errors were encountered: