Bug ID 689415: APM configuration snapshots missing due to APMD's failure to detect TMM state transition

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3

Fixed In:

Opened: Oct 19, 2017

Severity: 3-Major


User failed to log in with the following error message displayed on logon page: Access policy configuration has changed on gateway. Please login again to comply with new access policy configuration. In the /var/log/apm, there are error messages indicating configuration snapshots were found missing and the attempt to recreate them failed. -- err apmd[14462]: 01490259:3: Exception occurred for memcache operation: AccessPolicyProcessor/ProfileAccess.cpp line:430 function: resetTimeout - Config snapshot could not be found -- notice apmd[14462]: 01490165:5: Access profile: /Common/my_access_profile initialized with configuration snapshot catalog: /.0/tmm.session.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -- notice apmd[14462]: 01490166:5: Current snapshot ID: 1506842644 retrieved from session db for access profile: /Common/my_access_profile -- err apmd[14462]: 01490000:3: AccessPolicyProcessor/ProfileAccess.cpp func: "snapshotConfigVariables()" line: 358 Msg: EXCEPTION AccessPolicyProcessor/ProfileAccess.cpp line:298 function: snapshotConfigVariables - Config variable snapshot: Couldn't create catalog key (/.0/tmm.session.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx./Common/my_access_profile.1506842645)


APM end users will not be able to log in.


1. APMD detects TMM restart 2. APMD then recreates configuration snapshots when TMM becomes ready. 3. TMM restarts and becomes ready again. 4. APMD checks TMM status again but concludes that TMM is still down.


Restart APMD to recover when there is configuration snapshot.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips