Error updating Wazuh agent — Timeout and API usage

[Faber Andres Cubides]

Hello community,

I am trying to upgrade several Wazuh agents that are currently running version 4.10.1, while my Wazuh manager/console is on version 4.12. When attempting to upgrade the agents using agent_upgrade, I receive the following error:

Failed upgrades:
Agent 2633 status: Timeout reached while waiting for the response from the agent, check the result manually on the agent for more information


I also tried performing the upgrade through the API, but at first I received:

"Invalid authorization header"


After generating the token correctly, I was able to create the upgrade task, but the agent still does not upgrade.

My questions are:

What could be causing the timeout when trying to upgrade the agent?

Is there a specific log (both on the manager and on the agent) where I can check what is preventing the upgrade?

Is there any known issue when upgrading agents from 4.10 → 4.12 on Linux systems running kernel 4.18?

What would be the most reliable procedure to upgrade agents in this version range?

Thank you in advance for any guidance.

[root@btasaplseg16 usrapl]# curl -k -X GET "https://localhost:55000/agents/upgrade_result?agents_list=2633&pretty=true" -H  "Authorization: Bearer $TOKEN"
{
   "data": {
      "affected_items": [
         {
            "message": "Success",
            "agent": "2633",
            "task_id": 584,
            "node": "node01",
            "module": "upgrade_module",
            "command": "upgrade",
            "status": "Timeout reached while waiting for the response from the agent, check the result manually on the agent for more information",
            "create_time": "2025-11-20T15:40:04Z",
            "update_time": "2025-11-20T15:55:04Z"
         }
      ],
      "total_affected_items": 1,
      "total_failed_items": 0,
      "failed_items": []
   },
   "message": "All upgrade tasks were returned",
   "error": 0


[root@btasaplseg16 usrapl]# /u01/ossec/bin/agent_control -i 2633

Wazuh agent_control. Agent information:
   Agent ID:   2633
   Agent Name: btasaplclear01
   IP address: any
   Status:     Active

   Operating system:    Linux |btasaplclear01.rbm.com.co |4.18.0-553.81.1.el8_10.x86_64 |#1 SMP Thu Oct 16 14:01:33 EDT 2025 |x86_64
   Client version:      Wazuh v4.10.1
   Configuration hash:  ab73af41699f13fdd81903b5f23d8d00
   Shared file hash:    cb5dc59d195320bb20b6039a519a8c0e
   Last keep alive:     1763673253

   Syscheck last started at:  Thu Nov 20 14:34:57 2025
   Syscheck last ended at:    Thu Nov 20 14:35:05 2025

[Bony V John]

Hi,

Please allow me some time, I'm working on this and will get back to you with an update as soon as possible.

[Bony V John]

Hi,

The timeout issue can happen for several reasons, such as connectivity problems between the Wazuh manager and the agent during the upgrade, the agent taking too long to complete the upgrade, or a signature version mismatch.
To find the root cause, we need to check the ossec.log file on both the Wazuh agent and the manager to see if there are any errors or warnings related to this issue.

Run the following command on both the Wazuh manager and the agent server:

cat /var/ossec/logs/ossec.log | grep -iE "error|warn|wazuh-modulesd|agent-upgrade"

Please share the output with us for further analysis.

On the agent side, also check the current version of the agent:

/var/ossec/bin/wazuh-control info

Confirm whether it is still running the older version.

Please share your Wazuh agent ossec.conf file as well, as it will help us analyze the issue further.

Have you experienced this issue with only one agent?
Do any other agents on the same network face similar problems?

You can also refer to this Wazuh Reddit community discussion, which describes a similar issue.