Last Modified: Nov 11, 2023
Known Affected Versions:
188.8.131.52, 17.0.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.1.8, 15.1.7, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
17.1.0, 16.1.4, 15.1.9
Opened: Aug 18, 2022 Severity: 2-Critical
1. --An excessive number log lines are seen in /var/log/gtm, which indicate a state change even though a state change has not occurred (eg, blue --> blue, green --> green), for example: /var/log/gtm: alert gtmd: 011a6006:1: SNMP_TRAP: virtual server ltm1 (ip:port=192.168.0.1:0) (Server /Common/vs1) state change blue --> blue () 2. If, on affected version, the GTM configuration contains virtual servers with a depends-on clause, the gtmd process can exit abnormally ("crash") and produce a gtmd core file. The process restarts immediately automatically, but may then exit and restart again every few seconds or minutes, and continues to do this indefinitely. In /var/log/user.log, many messages similar to the following may be seen notice logger: Started writing core file: /var/core/gtmd.bld0.0.6.core.gz for PID 26739 notice logger: Finished writing 35032053 bytes for core file: /var/core/gtmd.bld0.0.6.core.gz for PID 26739
- Flood of SNMP trap logs are seen - gtmd process exits abnormally, bringing down iquery connection and potentially impacting GTM monitoring
- For the excessive logging issue: A GTM server object exists with one or more virtual servers configured under it - For the gtmd crashing issue: One or more GTM server object's virtual-servers has a depends-on clause referring to another virtual-server.