Last Modified: Feb 13, 2019
See more info
Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3
12.0.0, 11.6.0 HF4, 11.5.1 HF6
Opened: Oct 14, 2014
Related AskF5 Article: K15960
After updating a key/certificate in place and synchronizing the configuration, TMM may log critical-level messages about loading a key, certificate, or chain.
In 11.5.0 and later, this message indicates an issue that impacts traffic to affected virtual servers: 01260000:2: Profile /Common/otters: could not load key/certificate. In versions earlier than 11.5.0, these messages can safely be ignored: -- 01260000:2: Profile /Common/otters-ssl: could not load key file. -- 01260000:2: Profile /Common/otters-ssl: could load neither certificate nor chain file
A certificate and/or key referenced by an SSL profile are deleted and then recreated, and then that is synchronized (via a full sync, not an incremental sync) to peer devices.
TMM still log critical-level messages, but the system function properly and traffic is not affected.