This article describes an issue observed after upgrading to FortiProxy version 7.4.11, where the Primary member in an HA environment may continuously generate event logs indicating that FortiProxy updates have failed. This behavior occurs only on the Primary device and persists after HA failover.
Scope
FortiProxy v7.4, v7.6.
Solution
A recurring system event log appears on the Primary HA unit:
logid="0100041001" logdesc="FortiProxy update failed" msg="Fortiproxy update now failed" level="critical"
Only the Primary unit logs the message.
The Secondary unit does not report this event.
The behavior occurs even after performing an HA failover.
This is only a cosmetic logging issue in FortiProxy v7.4.11. The update process completes normally, but the system incorrectly generates a failure event during the scheduled update task executed on the Primary unit.
The issue does not affect update functionality or FortiGuard connectivity.
The fix for this issue is scheduled to be included in FortiProxy releases v7.4.13 and v7.6.5.
