Bug ID 1298333: Apmd logs "Following rule xxx, Access policy result xxx" generic log messages while no log-setting applied to the policy

Last Modified: Jun 28, 2025

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6

Opened: May 16, 2023

Severity: 4-Minor

Symptoms

APM continues to log some generic log messages even though the policy has no log-setting applied. Following are an example: ------------ notice apmd[20728]: 01490115:5: ::e4df4c50f5494cb3f02bd48710072c2d: Following rule 'fallback' from item 'va_status1468' to terminalout 'Out' notice apmd[20728]: 01490115:5: ::e4df4c50f5494cb3f02bd48710072c2d: Following rule 'fallback' from item 'va_status1400' to terminalout 'Out' notice apmd[20728]: 01490005:5: ::e4df4c50f5494cb3f02bd48710072c2d: Following rule 'Out' from item 'epc_auth_account_check' to ending 'Allow' notice apmd[20728]: 01490102:5: ::e4df4c50f5494cb3f02bd48710072c2d: Access policy result: LTM+APM_Mode ------------

Impact

Unwanted log messages are logged to /var/log/apm

Conditions

When an iRule is generating the APM session attached to the virtual server

Workaround

Use the following steps: A) Open /etc/syslog-ng/syslog-ng.conf B) Add one more line in "filter f_apm" like below: ======= filter f_apm { facility(local1) and message(": 0149[0-9a-fA-F]{4}:"); facility(local0) and not message (": 0149[0-9a-fA-F]{4}:"); // add this line }; ======== C) Save the file D) bigstart restart syslog-ng

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips