Bug ID 767941: Gracefully handle policy builder errors

Last Modified: Sep 13, 2023

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

Known Affected Versions:
13.1.1,,,,, 13.1.3,,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.0.0, 15.0.1,,,,

Fixed In:
15.1.0, 14.1.4,

Opened: Apr 03, 2019

Severity: 4-Minor


Policy Builder (pabnagd) restarts when it encounters an error, and logs errors to /var/log/asm: crit perl[24868]: 01310027:2: ASM subsystem error (asm_start,F5::NwdUtils::Nwd::log_failure): Watchdog detected failure for process. Process name: pabnagd, Failure: Insufficient number of threads (required: 2, found: 0).


Temporary loss of connectivity with ASM and Policy Builder.


This occurs when policy builder encounters an error.



Fix Information

The system now handles Policy Builder errors gracefully and reduces Policy Builder down time upon connectivity loss with ASM.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips