agent_upgrade

The agent_upgrade program allows you to list outdated agents and upgrade them.

Note

In case of having a multi-node Wazuh cluster, agent_upgrade must be executed on the node where the agent is connected.

Note

Since v4.1.0, the upgrade procedure is performed by the Agent upgrade module and the agent_upgrade script can be executed on any node.

-h, --help

Display the help message.

-l, --list_outdated

Generates a list with all outdated agents.

-a AGENT_IDs, --agents AGENT_IDs

Agent IDs to upgrade.

-F, --force

Allows reinstall same version and downgrade version.

-s, --silent

Do not show output.

-v VERSION, --version VERSION

Version to install.

-r REPOSITORY, --repository REPOSITORY

Specify a repository URL.

-f FILE, --file FILE

Custom WPK filename.

-x EXECUTE, --execute EXECUTE

Executable filename in the WPK custom file. By default it will try to launch upgrade.sh.

Note

By default, the timeout will be the maximum allowed by the agent with the execd.max_restart_lock option in internal_options.conf.

Examples

  • List outdated agents:

# /var/ossec/bin/agent_upgrade -l
ID    Name                               Version
002   VM_Debian9                         Wazuh v3.13.2
003   VM_Debian8                         Wazuh v3.13.2
009   VM_WinServ2016                     Wazuh v3.10.1

Total outdated agents: 3
  • Upgrade agent:

# /var/ossec/bin/agent_upgrade -a 002
Upgrading...

Upgraded agents:
    Agent 002 upgraded: Wazuh v3.13.2 -> 4.3.1
  • Downgrade agent using a custom repository:

# /var/ossec/bin/agent_upgrade -a 002 -dF -v v4.0.0 -r http://mycompany.wpkrepo.com/
Upgrading...

Upgraded agents:
    Agent 002 upgraded: Wazuh v3.13.2 -> 4.0.0
  • Install custom WPK file:

# /var/ossec/bin/agent_upgrade -a 002 -d -f /root/upgrade_openscap_debian.wpk -x install.sh
Upgrading...

Upgraded agents:
    Agent 002 upgraded: Wazuh v3.13.2 -> 4.0.0

Note

When the agent finishes updating, it is automatically restarted to apply the new configuration.