Symptoms

APD and APMD might crash when a file check agent is added to an access policy. The issue can happen for any file check agent: Windows File, Linux File, or Mac File.

Impact

A daemon, APD or APDM, cannot start because it crashes during initialization of the affected agent. You can confrm the presence of the issue by To confirm, please searching apm log file for either of the following SIGABRT messages: -- notice apd[<pid>]: 01490000:5: ** SIGABRT **. -- notice apmd[<pid>]: 01490000:5: ** SIGABRT **.

Conditions

A file check agent (Windows / Mac / Linux) is added to an access policy.

Workaround

None.

Fix Information

In 11.5.0 and later, a Windows File, Mac File, or Linux File agent can be added to an access policy without causing APD or APDM to crash.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips