Symptoms

The following message may be logged to /var/log/tmm* Can't process event 16, err: ERR_NOT_FOUND

Impact

Since the PEM policy is already applied to the session, the failure message is essentially cosmetic, but it can cause the tmm logs to grow in size if this is happening frequently.

Conditions

Applying a PEM policy to an existing session that already has that policy (eg, through an irule using 'PEM::subscriber config policy referential set xxxx'

Workaround

--

Fix Information

None

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips