Preview Tool

Cisco Bug: CSCup90024 - ACS 5 Runtime fails to load if ID name store contains certain string

Last Modified

Nov 27, 2020

Products (1)

  • Cisco Secure Access Control Server Solution Engine

Known Affected Releases


Description (partial)

ACS 5.x gets configured with an ID store name containing an underscore followed by a number, e.g. LDAP_2.

This seems to work, until services are stopped and restarted, at which point Runtime service fails to start, and goes into "Not Monitored" status.  The following appears in the Runtime log:

MessageBus,<timestamp>,ERROR,3034504080,MessageBusSender::connect: unable to connect to the management;exception=Connection refused,MessageBusSender.cpp:131
ConfigNotificationFlow<timestamp>,ERROR,3032968080,cntx=0000000005,ConfigNotificationFlow::onMBSendEventResponse: MB error, status=MB_NOT_CONNECTED, msg=, state=Sync,ConfigNotification
EventHandler,<timestamp>,ERROR,3032968080,Double registration of EventHandler (IDStoreEventDispatcher<LDAPIDStore>, with key: LDAP_2). Must unregister first,EventDispatcher.cpp:175
RT,<timestamp>,ERROR,3086739728,rt_daemon init failed,RTDaemon.cpp:276

Removing the underscore, e.g. changing name to HBEU2, allows services to restart successfully.  Put it back in, and it breaks again.  This was recreated by BU escalations engineer multiple times.

1) ACS 5.x
2) ID store name containing underscore followed by number, e.g. LDAP_2
3) Restart ACS services

Related Community Discussions

benefits of Cisco ACS 5.7
Hi Everyone, I am currently using Cisco ACS 5.4 with patch 7  only to manage users logging into network devices (i.e. TACACS+ and radius).  Cisco just releases 5.7 on May 12th.  Any benefits to upgrade from 5.4 patch 7 to ACS 5.7? on the release notes, I see this on 5.7:  Maximum Failed Attempts Count Policy  New Sub-Attributes for Service Type RADIUS IETF Attribute  Supporting SNMP Traps for Monitoring Disk Utilization  Log Message for CLI Administrator Account Locked Out  Establishing New Connection ...
Latest activity: May 20, 2015
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.