CiscoSecure ACS Solution Engine version 3.3.3 is not able to allocate CSAuth threads and displays the "Too busy to handle connection attempt" error message

Document

Wed, 11/18/2009 - 18:24
Jun 18th, 2009

Core issue

This problem occurs due to the presence of Cisco bug ID CSCsd40764.

With this error, the CiscoSecure ACS Solution Engine ceases to authenticate users. Error logs show events similar to this:

AUTH 02/13/2006 11:44:46 I 5081 0704 Done RQ1040, client 2, status 0
AUTH 02/13/2006 11:44:46 S 5100 0640 Listening for new TCP connection --------
AUTH 02/13/2006 11:44:46 E 5103 0640 AllocateThread returned -1 AUTH 02/13/2006 11:44:46 E 5103 0640 Too busy to handle connection attempt 253

The Too busy to handle connection attempt error message is displayed until the service is re-started. When the errors occur, no authentication attempts succeed. This issue is seen in environments where the CiscoSecure ACS Solution Engine authenticates to a remote agent. It is possible for the remote agent to tie up CSAuth authentication attempts. This is found in CiscoSecure ACS Solution Engine versions 4.0, and 3.3(3).

Resolution

As a workaround, perform either of these steps:

  • Reload the CiscoSecure ACS solution engine.

  • Reset the CSAuth service when the problem is observed.

Error

Too busy to handle connection attempt

Cisco Secure Access Control Server (ACS)

ACS Solution Engine Software version 3.3

Loading.

Actions

This Document

Related Content