Last Modified: Jun 19, 2025
Affected Product(s):
F5OS F5OS-C
Known Affected Versions:
F5OS-C 1.6.2
Fixed In:
F5OS-C 1.8.1
Opened: Dec 11, 2024 Severity: 2-Critical
In FIPS error state, the active controller triggers a sync to the errored controller which results into an infinite loop of waiting as the peer is unreachable. This dumps an enormous amount of logs in ccsync.log and consumes excessive memory.
Consumes high system memory and log files are rotated in no time leaving a huge dump of logs in ccsync.log
One active controller and one FIPS errored out controller.
- stop ccswatch.service - Recover FIPS errored controller - restart ccswatch.service
Added retries to wait for a finite time period before exiting to reduce log flood and memory usage.