Arch Linux (@archlinux.org.web.brid.gy)

zabbix >= 7.4.1-2 may require manual intervention Starting with `7.4.1-2`, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared `zabbix` user account (as originally intended by upstream and done by other distributions): * zabbix-server * zabbix-proxy * zabbix-agent _(also used by the`zabbix-agent2` package)_ * zabbix-web-service This shared `zabbix` user account is provided by the newly introduced `zabbix-common` _split_ package, which is now a dependency for all relevant `zabbix-*` packages. The switch to the new user account is handled automatically for the corresponding main configuration files and `systemd` service units. However, **manual intervention may be required** if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example: * `PSK` files used for encrypted communication * Custom scripts for metrics collections or report generations * `sudoers` rules for metrics requiring elevated privileges to be collected * ... Those should therefore be updated to refer to and / or be owned by the new `zabbix` user account, otherwise some services or user parameters may fail to work properly, or not at all. Once migrated, you may remove the obsolete user accounts from your system. https://archlinux.org/news/zabbix-741-2-may-requires-manual-intervention/