TAC has always better resorces to assit you, may be eng'r didn't get a chance to reply.
I have seen this issue couple of times in last week, looks like there is a problem with PATCH 5. Have you tried applying the patch 3 after removing patch 5? In not then please try, this may help you.
I personally came across this issue last week and we ended up reimaging and restoring the ACS database. You should gether the management and runtime longs to further investigate the issue. Do upload the same file to TAC case.
=====================================
## Steps to generate support bundle ##
=====================================
acs/acsadmin# acs-config
Escape character is CNTL/D.
Username: xxxx ( GUI ADMIN USERNAME)
Password: xxxx ( GUI ADMIN PASSWORD)
acs/acsadmin(config-acs)# debug-log mgmt level debug
acs/acsadmin(config-acs)# debug-log runtime level debug
At this point you need to duplicate the issue, please try to restart the runtime process couple of times to capture the issue.
acs support repository include-debug-logs
===========================================
## Steps To decrypt the ACS support bundle ##
===========================================
--> Copy the support bundle to ACS server repository.
--> Create repository On the ACS
--> From CLI go to acs-config mode and login with GUI admin credentials.
acs/acsadmin# acs-config
Escape character is CNTL/D.
Username: xxxx (GUI USERNAME)
Password: xxxx (GUI PASSWORD)
--> Run the decrypt-support-bundle command, to decrypt the support bundle.
acs/admin(config-acs)# decrypt-support-bundle
You might see ActiveMQ exception in the logs.
HTH
Regards,
Jatin
Do rate helpful posts-
~Jatin
