12-01-2010 08:11 AM - edited 03-12-2019 05:39 PM
Folks - our Windows server disk filled up. Cisco ACS 4.2 threw a fatal error and locked the database.
I've cleared up space on disk and reloaded server. ACS processes start, but sockets do not. It appears that database is still locked, and CSMON is shutting down the sockets.
Any ideas on how to unlock database and bring up GUI? Following are logs.
*********************************************
CSMon 11/28/2010 17:48:57 E 0092 0592 0x0 ODBC Operation faild with the following information: Message=[Sybase][ODBC Driver][Adaptive Server Anywhere]Disk full 'Fatal error: disk full C:\Program Files\CiscoSecure ACS v4.2\CSDB\ACS.log' -- transaction rolled back, SqlState=S1000, NativeError=-304
CSMon 11/28/2010 17:48:58 A 0191 0592 0x0 SL:getValue (dword)- execution failed
CSMon 11/28/2010 17:49:08 E 0092 0208 0x0 ODBC Operation faild with the following information: Message=[Sybase][ODBC Driver][Adaptive Server Anywhere]Connection was terminated, SqlState=S1000, NativeError=-308
CSMon 11/28/2010 17:49:08 A 0932 0208 0x0 SL:isKeyExist - execution failed
**********************************************
CSMon 11/29/2010 11:56:19 E 0092 1392 0x0 ODBC Operation faild with the following information: Message=[Sybase][ODBC Driver][Adaptive Server Anywhere]Connection was terminated, SqlState=S1000, NativeError=-308
CSMon 11/29/2010 11:56:19 A 0147 1392 0x0 SL:setValue (string) - execution failed
CSMon 11/29/2010 11:56:19 E 0092 1392 0x0 ODBC Operation faild with the following information: Message=[Sybase][ODBC Driver][Adaptive Server Anywhere]Connection was terminated, SqlState=S1000, NativeError=-308
CSMon 11/29/2010 11:56:19 A 0147 1392 0x0 SL:setValue (string) - execution failed
CSMon 11/29/2010 11:56:19 A 0429 1392 0x0 CSMon Shutdown: Stopping Notifications.
CSMon 11/29/2010 11:56:19 A 0501 1392 0x0 CSMon Shutdown, stopping Problem Monitoring.
CSMon 11/29/2010 11:56:19 A 0448 1392 0x0 CSMon Shutdown: Stopping Worker Threads.
CSMon 11/29/2010 11:56:19 A 0451 1392 0x0 CSMon Shutdown: Closing connection to CSAuth API.
CSMon 11/29/2010 11:56:21 A 0454 1392 0x0 CSMon Shutdown: Closing Mail and NTLog stuff.
CSMon 11/29/2010 11:56:21 A 0457 1392 0x0 CSMon Shutdown: Cleaning up Synchronisations stuff.
CSMon 11/29/2010 11:56:21 A 0280 1392 0x0 CSMon Shutdown: Closing Winsock.
CSMon 11/29/2010 11:56:23 A 0288 1392 0x0 ******************************************
CSMon 11/29/2010 11:56:23 A 0289 1392 0x0 * Shutdown Complete *
CSMon 11/29/2010 11:56:23 A 0290 1392 0x0 ******************************************
12-01-2010 08:22 AM
Hi. any idea why the disk filled up, did you install any new application on the ACS Server, such as SQL Server maybe?
thx
Serge
12-01-2010 08:24 AM
It was benign and resolved. We have enough disk space now.
12-01-2010 08:28 AM
i searched on tac db and found a similar case to your where the problem was customer installed an SQL server on the same machine of acs that ate all disk space and caused same error message as you pasted. that is why i was asking, did you install SQL server lately on that machine?
06-20-2012 05:14 PM
I ran into a similar issue. In my case, the services would not start after resolving the space issue and rebooting.
I was able to resolve the issue by renaming the acs.log (transaction log) file in the ...\CiscoSecure ACS v4.2\CSDB\ folder.
From there, I was able to restart the CSAuth service and all subsequent services.
The offending acs.log file was marked Read-Only and had a length of 0 bytes. Once started, the DB created a new file with a file size of 192KB.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide