Guest

Preview Tool

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

Last Modified

Oct 31, 2016

Products (1)

  • Cisco Secure Access Control Server Solution Engine

Known Affected Releases

5.4(0.46.4)

Description (partial)

Symptom:
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
Flow.cpp:701
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
RT,<timestamp>,ERROR,3086739728

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.

Conditions:
1) ACS 5.x
2) ID store name containing underscore followed by number, e.g. LDAP_2
3) Restart ACS services
Bug details contain sensitive information and therefore require a Cisco.com 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.