Bug ID 601378: Creating an ASM security policy with "Auto accept" language leads to numerous errors in asm log and restarts of 'pabnagd' and 'asm_config_server' daemons

Last Modified: Sep 13, 2023

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

Fixed In:
13.0.0, 12.1.2 HF1

Opened: Jun 24, 2016

Severity: 2-Critical

Symptoms

These errors can be observed in '/var/log/asm': ------------------------- The caller:[F5::ASMConfig::Entity::Charset::get_policy_encoding_type] did not pass in a value for 'encoding_name' to retrieve the 'encoding_type' for -- aborting. ASM subsystem error (asm_config_server.pl,): ASM Config server died unexpectedly ASM subsystem error: (asm_start,F5::NwdUtils::Nwd::log_failure): Watchdog detected failure for process. Process name: pabnagd, Failure: Insufficient number of threads. ASM subsystem error: (asm_start,F5::NwdUtils::Nwd::log_failure): Watchdog detected failure for process. Process name: asm_config_server.pl, Failure: Insufficient number of threads. -------------------------

Impact

ASM daemons restart, numerous errors in asm log.

Conditions

ASM provisioned. Create security policy with "Auto accept" language.

Workaround

None.

Fix Information

Creating an ASM security policy with "Auto accept" language no longer leads to numerous errors in asm log and restarts of 'pabnagd' and 'asm_config_server' daemons

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips