Last Modified: May 07, 2025
Affected Product(s):
F5OS Velos
Opened: Jan 11, 2024 Severity: 4-Minor
The system may periodically log platform-monitor errors in the velos.log on the controller: <timestamp> controller-1 platform-monitor[8]: priority="Err" msg="Monitor Error Event" kind="service:monitor-error" error="Get \"http://localhost:10080/v3/qkviewd/health\": dial tcp [::1]:10080: connect: connection refused" interface="console-output" <timestamp> controller-1 platform-monitor[8]: priority="Err" msg="Monitor Error Event" kind="service:monitor-error" error="ReadyRequest failed for 'platform-hal' @ 'tcp://127.0.0.1:1046', Inner -> 'receive timeout'" interface="console-output" The VELOS system may also log these errors in the partition's velos.log: <timestamp> controller-1(p2) platform-monitor[8]: priority="Err" msg="Monitor Error Event" kind="service:monitor-error" error="HealthRequest failed for 'partition2_tcpdumpd_manager' @ 'tcp://127.0.0.1:3510', Inner -> 'receive timeout'" interface="console-output" <timestamp> 100.65.18.52 controller-2(p2) platform-monitor[9]: priority="Err" msg="Monitor Error Event" kind="service:monitor-error" error="HealthRequest failed for 'partition2_tcpdumpd_manager' @ 'tcp://127.0.0.1:3510', Inner -> 'receive timeout'" interface="console-output" The platform-monitor events normally only occur on tcpdump monitors. The log messages can occur even on an idle VELOS system.
The issue is transient and cosmetic.
VELOS system with partition enabled.
None.
None