-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Wazuh Windows agent remote upgrade error version v4.3.8 #15089
Comments
Hello @khangcnttspkt ! It seems that something happened during the upgrade, and that folder is now empty when it shouldn't be. As a workaround, you could try to create again the required folders, to allow the agent to create the databases and properly run:
Regards. |
Hi @pereyra-m , Here are my logs:
After that, windows service recreate with path default "C:\Program Files (x86)\ossec-agent", how I remote upgrade my wazuh-agent with custom path "C:\Program Files (x86)\wazuh-agent" like previous version. |
Hello again @khangcnttspkt . I was making some tests but when I install the Windos agent in a custom location and perform a remote upgrade, the process is successful. Was the agent able to start after creating the corresponding folders? |
Hi @pereyra-m , Here are my upgrade.log file
I remote upgrade success, but it install in "C:\Program Files (x86)\ossec-agent" and Windows service replace with "C:\Program Files (x86)\ossec-agent" path. If I unistall wazuh-agent and fresh install again with version v4.3.4 with custom path, I can success remote upgrade without errror. But with wazuh-agent was installed, I remote upgrade failed, I try to remote upgrade with many windows server in my system but same error. |
Hello again @khangcnttspkt ! I'm still making tests about your issue. When I install the agent in a custom location it is always upgraded successfully without changing the path.
But about the errors you have in the rest of the servers, did you update the CA in the agents? See issue #14715 for more details. Regards. |
Hi every body,
I install wazuh-agent version 4.3.4 on windows with path "C:\Program Files (x86)\wazuh-agent",
After remote uprade to v4.3.8, agent auto install with path default "C:\Program Files (x86)\ossec-agent",
And then all data on queue is empty => wazuh-agent service on client start failed.
with logs
2022/10/07 13:39:59 wazuh-agent: ERROR: Couldn't create SQLite database 'queue/fim/db/fim.db': unable to open database file (14)
2022/10/07 13:39:59 wazuh-agent: CRITICAL: (6698): Creating Data Structure: sqlite3 db. Exiting.
2022/10/07 13:39:59 wazuh-agent: INFO: Received exit signal. Starting exit process.
2022/10/07 13:39:59 wazuh-agent: INFO: Set pending exit signal.
2022/10/07 13:39:59 wazuh-modulesd:syscollector: INFO: Stop received for Syscollector.
2022/10/07 13:39:59 wazuh-agent: INFO: Exit completed successfully.
2022/10/07 13:39:59 wazuh-agent: INFO: (1314): Shutdown received. Deleting responses.
2022/10/07 13:39:59 wazuh-modulesd:osquery: INFO: Module disabled. Exiting...
Before version v4.3.8 I remote upgrade with no error.
The text was updated successfully, but these errors were encountered: