Bug ID 586287: No way to control how aborted iRules log messages are generated and sent to /var/log/ltm.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Apr 08, 2016

Severity: 4-Minor

Symptoms

There is no way to control the rate at which aborted iRules log messages are generated and sent to /var/log/ltm rule-aborted log messages similar to the following: info tmm[19392]: 01220009:6: Pending rule /Common/abort_rule <HTTP_REQUEST_SEND> aborted for <IP address>

Impact

Many "pending rule aborted" messages in ltm log.

Conditions

Viewing ltm log messages.

Workaround

Syslog filter can be created to filter the unwanted log messages from /var/log/ltm. modify syslog { ... include " filter f_local0 { facility(local0) and not match (\"Pending rule /Common/_sys_APM_Exchange <HTTP_REQUEST> aborted for\"); }; " ... }

Fix Information

This release adds a bigdb variable to control how aborted iRules log messages are generated and sent to /var/log/ltm. The new option can be configured either via a sys db or using tmsh: sys db: tmm.tcl.rule.aborted.log.ratio tmsh: ltm global-settings rule rule-aborted-log-ratio The options are as follows: - 0 Logging is disabled. - 1 (default) every aborted iRule occurrence is logged. - > 1 only one in N aborted execution is logged, in addition to a message indicating how many previous log messages were suppressed.

Behavior Change

This release introduce a configuration option to control the rate at which aborted iRules log messages are generated and sent to /var/log/ltm. The option can be configured as follows: - 0 Logging is disabled - 1 (default) every aborted iRule occurrence is logged - > 1 only one in N aborted execution is logged, in addition to a message indicating how many previous log messages were suppressed. The new option can be configured either via a sys db or using tmsh: Sys db: tmm.tcl.rule.aborted.log.ratio tmsh: ltm global-settings rule rule-aborted-log-ratio

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips