Forum Discussion
Failed due to ASMConfig exception
Hi!
My devices is reporting a new messages:
Oct 4 22:06:19 F5_TEST01[28304]: dcc|ERR|Oct 04 22:06:19.657|28304| [tsconfd::ASMCONFIG_CALL, update mcp logging profile] Failed due to ASMConfig exception
I didn't find nothing about this warning, can be a bug..is it true?
So, This message was cause because I've created a new security polity (the process wasn't completed never) and lost the communication with the device (this device was like died).
Curerntly My device has 350 Virtual Servers and 17 security policies. The model is 4200 with BIG-IP v11.6.0 (Build 6.0.442)
The performance is good, CPU is over 40% and memory (TMM Memory used is 20%) (Other Memory used is 80%) (swap used ir 40%)
Could you help me, please???? What I can check???
Thanks!
- Chris_Grant
Employee
I am assuming that ASM is working normally other than this message. If that is the case, you should contact support about tracking down the root cause of this message.
If ASM is not starting you may wish to begin with this article:
https://support.f5.com/csp/article/K14194 Troubleshooting the BIG-IP ASM MySQL database
You may also be able to simply issue:
bigstart restart asm
or reboot the appliance.
If none of these help, you will want to reach out to support.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com