GHOST CLEANUP locked up my system

  • I don't have any AutoShrink databases.

    According to SQL Response the Ghost Cleanup process started at 17:44 yesterday and is still going. Today it caused a block when I tried to detach a database. Now I can't reconnect to do anything. The rest of the system seemed fine until I did this detach, and I had done other detaches just minutes before. Am I stuck restarting the SQL Service?

  • Sorry, SQL Server 2005 SP 3 on Win 2003 (32bit)

  • I wasn't able to restart the services, SO I had to reboot the machine. It seems to be stuck on the SQL Agent. SQL Agent gave an error at startup as well, so I set the service to manual and rebooted again. So, currently the SQL Server service is working, and the SQL Agent is not running.

    When I try to connect to the Server from SSMS I get a msdb is rebuilding message. Should I panic yet?

  • My guess would be http://support.microsoft.com/kb/978430. Fixed in SP3 CU9.

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • Perhaps. But right now I can't recover the msdb, to even think about applying a patch. Restores just tell me the db is in Recovery, wait until it's finished. The Instmsdb.sql suggestions I ready don't work either, the instmsdb.sql script fails to create the new files, mostly file not found errors.

    Panic is starting to rise.

  • If you have a current backup of msdb you can try this:

    Restore the backup under a different name - Mymsdb

    stop the sql server and Agent services

    rename the msdb files so the problem database files are replaced with the restored files.

    Restart SQL Server Service.

    No guarantees, but I have seen it work. Also if it failes you can swap the files back again and you are no worse off.

    Leo

    Striving to provide a better service.

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

  • Dan Guzman - Not the MVP (5/18/2010)


    Restores just tell me the db is in Recovery, wait until it's finished.

    What does the error log say about msdb?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Nothing about msdb. It shows a checkdb, which completes without errors. There are 2 stack dumps, but they don't say what caused it.:

    **Dump thread - spid = 22, PSS = 0x0429A7D8, EC = 0x0429A7E0

    2010-05-18 21:24:12.50 spid22s ***Stack Dump being sent to d:\mssqldata\MSSQL\LOG\SQLDump0038.txt

    2010-05-18 21:24:12.50 spid22s * *******************************************************************************

    2010-05-18 21:24:12.50 spid22s *

    2010-05-18 21:24:12.50 spid22s * BEGIN STACK DUMP:

    2010-05-18 21:24:12.50 spid22s * 05/18/10 21:24:12 spid 22

    2010-05-18 21:24:12.50 spid22s *

    2010-05-18 21:24:12.50 spid22s * Location: "logmgr.cpp":5565

    2010-05-18 21:24:12.50 spid22s * Expression: !(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)

    2010-05-18 21:24:12.50 spid22s * SPID: 22

    2010-05-18 21:24:12.50 spid22s * Process ID: 6604

    2010-05-18 21:24:12.50 spid22s *

    2010-05-18 21:24:12.50 spid22s *

    2010-05-18 21:24:12.50 spid22s *

    2010-05-18 21:24:12.50 spid22s * MODULE BASE END SIZE

    2010-05-18 21:24:12.50 spid22s * sqlservr 01000000 02C24FFF 01c25000

    2010-05-18 21:24:12.50 spid22s * ntdll 7C800000 7C8C1FFF 000c2000

    2010-05-18 21:24:12.50 spid22s * kernel32 77E40000 77F41FFF 00102000

    2010-05-18 21:24:12.50 spid22s * MSVCR80 78130000 781CAFFF 0009b000

    2010-05-18 21:24:12.50 spid22s * msvcrt 77BA0000 77BF9FFF 0005a000

    2010-05-18 21:24:12.50 spid22s * MSVCP80 7C420000 7C4A6FFF 00087000

    2010-05-18 21:24:12.50 spid22s * ADVAPI32 7D1E0000 7D27BFFF 0009c000

    2010-05-18 21:24:12.50 spid22s * RPCRT4 77C50000 77CEEFFF 0009f000

    2010-05-18 21:24:12.50 spid22s * Secur32 76F50000 76F62FFF 00013000

    2010-05-18 21:24:12.50 spid22s * sqlos 344D0000 344D4FFF 00005000

    2010-05-18 21:24:12.50 spid22s * USERENV 76920000 769E1FFF 000c2000

    2010-05-18 21:24:12.50 spid22s * USER32 77380000 77410FFF 00091000

    2010-05-18 21:24:12.50 spid22s * GDI32 77C00000 77C48FFF 00049000

    2010-05-18 21:24:12.50 spid22s * WINMM 76AA0000 76ACCFFF 0002d000

    2010-05-18 21:24:12.50 spid22s * opends60 333E0000 333E6FFF 00007000

    2010-05-18 21:24:12.50 spid22s * NETAPI32 71C40000 71C96FFF 00057000

    2010-05-18 21:24:12.50 spid22s * IMM32 76290000 762ACFFF 0001d000

    2010-05-18 21:24:12.50 spid22s * psapi 76B70000 76B7AFFF 0000b000

    2010-05-18 21:24:12.50 spid22s * instapi 48060000 48069FFF 0000a000

    2010-05-18 21:24:12.50 spid22s * sqlevn70 4F610000 4F7B8FFF 001a9000

    2010-05-18 21:24:12.50 spid22s * rsaenh 68000000 68034FFF 00035000

    2010-05-18 21:24:12.50 spid22s * AUTHZ 76C40000 76C53FFF 00014000

    2010-05-18 21:24:12.50 spid22s * MSCOREE 33DA0000 33DE5FFF 00046000

    2010-05-18 21:24:12.50 spid22s * ole32 77670000 777A8FFF 00139000

    2010-05-18 21:24:12.50 spid22s * msv1_0 76C90000 76CB6FFF 00027000

    2010-05-18 21:24:12.50 spid22s * cryptdll 766E0000 766EBFFF 0000c000

    2010-05-18 21:24:12.50 spid22s * WS2_32 71C00000 71C16FFF 00017000

    2010-05-18 21:24:12.50 spid22s * WS2HELP 71BF0000 71BF7FFF 00008000

    2010-05-18 21:24:12.50 spid22s * iphlpapi 76CF0000 76D09FFF 0001a000

    2010-05-18 21:24:12.50 spid22s * kerberos 341D0000 34228FFF 00059000

    2010-05-18 21:24:12.50 spid22s * MSASN1 34230000 34241FFF 00012000

    2010-05-18 21:24:12.51 spid22s * schannel 76750000 76777FFF 00028000

    2010-05-18 21:24:12.51 spid22s * CRYPT32 34260000 342F2FFF 00093000

    2010-05-18 21:24:12.51 spid22s * COMRES 77010000 770D5FFF 000c6000

    2010-05-18 21:24:12.51 spid22s * XOLEHLP 34340000 34345FFF 00006000

    2010-05-18 21:24:12.51 spid22s * MSDTCPRX 34350000 343C8FFF 00079000

    2010-05-18 21:24:12.51 spid22s * OLEAUT32 77D00000 77D8AFFF 0008b000

    2010-05-18 21:24:12.51 spid22s * msvcp60 343D0000 34434FFF 00065000

    2010-05-18 21:24:12.51 spid22s * MTXCLU 34440000 34458FFF 00019000

    2010-05-18 21:24:12.51 spid22s * VERSION 77B90000 77B97FFF 00008000

    2010-05-18 21:24:12.51 spid22s * WSOCK32 71BB0000 71BB8FFF 00009000

    2010-05-18 21:24:12.51 spid22s * CLUSAPI 34460000 34471FFF 00012000

    2010-05-18 21:24:12.51 spid22s * RESUTILS 34480000 34492FFF 00013000

    2010-05-18 21:24:12.51 spid22s * mswsock 71B20000 71B60FFF 00041000

    2010-05-18 21:24:12.51 spid22s * DNSAPI 76ED0000 76EF9FFF 0002a000

    2010-05-18 21:24:12.51 spid22s * winrnr 76F70000 76F76FFF 00007000

    2010-05-18 21:24:12.51 spid22s * WLDAP32 76F10000 76F3DFFF 0002e000

    2010-05-18 21:24:12.51 spid22s * rasadhlp 76F80000 76F84FFF 00005000

    2010-05-18 21:24:12.51 spid22s * security 62840000 62843FFF 00004000

    2010-05-18 21:24:12.51 spid22s * msfte 62F00000 63159FFF 0025a000

    2010-05-18 21:24:12.51 spid22s * dbghelp 63160000 63274FFF 00115000

    2010-05-18 21:24:12.51 spid22s * WINTRUST 76BB0000 76BDBFFF 0002c000

    2010-05-18 21:24:12.51 spid22s * imagehlp 76C10000 76C37FFF 00028000

    2010-05-18 21:24:12.51 spid22s * dssenh 68100000 68126FFF 00027000

    2010-05-18 21:24:12.51 spid22s * hnetcfg 63550000 635A9FFF 0005a000

    2010-05-18 21:24:12.51 spid22s * wshtcpip 71AE0000 71AE7FFF 00008000

    2010-05-18 21:24:12.51 spid22s * NTMARTA 77E00000 77E20FFF 00021000

    2010-05-18 21:24:12.51 spid22s * SAMLIB 7E020000 7E02EFFF 0000f000

    2010-05-18 21:24:12.51 spid22s * ntdsapi 766F0000 76703FFF 00014000

    2010-05-18 21:24:12.51 spid22s * xpsp2res 635F0000 638B4FFF 002c5000

    2010-05-18 21:24:12.51 spid22s * CLBCatQ 777B0000 77832FFF 00083000

    2010-05-18 21:24:12.51 spid22s * sqlncli 638C0000 63AE6FFF 00227000

    2010-05-18 21:24:12.51 spid22s * COMCTL32 77530000 775C6FFF 00097000

    2010-05-18 21:24:12.51 spid22s * comdlg32 762B0000 762F8FFF 00049000

    2010-05-18 21:24:12.51 spid22s * SHLWAPI 7D180000 7D1D1FFF 00052000

    2010-05-18 21:24:12.51 spid22s * SHELL32 7C8D0000 7D0CEFFF 007ff000

    2010-05-18 21:24:12.51 spid22s * comctl32 77420000 77522FFF 00103000

    2010-05-18 21:24:12.51 spid22s * SQLNCLIR 63AF0000 63B22FFF 00033000

    2010-05-18 21:24:12.51 spid22s * dbghelp 64580000 64694FFF 00115000

    2010-05-18 21:24:12.51 spid22s *

    2010-05-18 21:24:12.51 spid22s * Edi: 63D3C8E8: 0014CAC8 000D0928 7C829F79 00000000 7C829E37 00000000

    2010-05-18 21:24:12.51 spid22s * Esi: 00000000:

    2010-05-18 21:24:12.51 spid22s * Eax: 63D3C7CC: 000042AC 00000000 00000000 77E4BEF7 00000000 7C827739

    2010-05-18 21:24:12.51 spid22s * Ebx: 0000003F:

    2010-05-18 21:24:12.51 spid22s * Ecx: 63D3CE3C: 00000000 00010007 00000000 004E004C 0014CACC 63D3C7FC

    2010-05-18 21:24:12.51 spid22s * Edx: 0000003D:

    2010-05-18 21:24:12.51 spid22s * Eip: 77E4BEF7: 10C2C95E 01093D00 840FC000 00000095 F29DE950 9090FFFF

    2010-05-18 21:24:12.51 spid22s * Ebp: 63D3C81C: 63D3C860 021B2C8C 000042AC 00000000 00000000 00000000

    2010-05-18 21:24:12.51 spid22s * SegCs: 7813001B: 00000000 00000000 00000000 00000000 00000000 00000000

    2010-05-18 21:24:12.51 spid22s * EFlags: 00000246:

    2010-05-18 21:24:12.51 spid22s * Esp: 63D3C7C8: 0429A7D8 000042AC 00000000 00000000 77E4BEF7 00000000

    2010-05-18 21:24:12.51 spid22s * SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000 00000000

    2010-05-18 21:24:12.51 spid22s * *******************************************************************************

    2010-05-18 21:24:12.51 spid22s * -------------------------------------------------------------------------------

    2010-05-18 21:24:12.51 spid22s * Short Stack Dump

    2010-05-18 21:24:12.52 spid22s 77E4BEF7 Module(kernel32+0000BEF7)

    2010-05-18 21:24:12.52 spid22s 021B2C8C Module(sqlservr+011B2C8C)

    2010-05-18 21:24:12.52 spid22s 021B6BA0 Module(sqlservr+011B6BA0)

    2010-05-18 21:24:12.52 spid22s 02053ABA Module(sqlservr+01053ABA)

    2010-05-18 21:24:12.52 spid22s 015AD89F Module(sqlservr+005AD89F)

    2010-05-18 21:24:12.52 spid22s 010B0556 Module(sqlservr+000B0556)

    2010-05-18 21:24:12.52 spid22s 021D5116 Module(sqlservr+011D5116)

    2010-05-18 21:24:12.52 spid22s 021E531A Module(sqlservr+011E531A)

    2010-05-18 21:24:12.52 spid22s 0210D679 Module(sqlservr+0110D679)

    2010-05-18 21:24:12.52 spid22s 020F9807 Module(sqlservr+010F9807)

    2010-05-18 21:24:12.52 spid22s 021038B4 Module(sqlservr+011038B4)

    2010-05-18 21:24:12.52 spid22s 02103483 Module(sqlservr+01103483)

    2010-05-18 21:24:12.52 spid22s 01008D8D Module(sqlservr+00008D8D)

    2010-05-18 21:24:12.52 spid22s 01008EB3 Module(sqlservr+00008EB3)

    2010-05-18 21:24:12.52 spid22s 01008BC3 Module(sqlservr+00008BC3)

    2010-05-18 21:24:12.52 spid22s 0146BF50 Module(sqlservr+0046BF50)

    2010-05-18 21:24:12.52 spid22s 0146BE70 Module(sqlservr+0046BE70)

    2010-05-18 21:24:12.52 spid22s 0146B920 Module(sqlservr+0046B920)

    2010-05-18 21:24:12.54 spid22s 0146BABD Module(sqlservr+0046BABD)

    2010-05-18 21:24:12.54 spid22s 781329BB Module(MSVCR80+000029BB)

    2010-05-18 21:24:12.56 spid22s 78132A47 Module(MSVCR80+00002A47)

    2010-05-18 21:24:12.57 spid22s Stack Signature for the dump is 0x936F109C

  • I get this message between the two stack dumps:

    Error: 17066, Severity: 16, State: 1.

    2010-05-18 21:24:13.30 spid22s SQL Server Assertion: File: <"logmgr.cpp">, line=5565 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

    2010-05-18 21:24:13.32 spid23s Using 'dbghelp.dll' version '4.0.5'

    2010-05-18 21:24:13.33 spid22s Error: 3624, Severity: 20, State: 1.

    2010-05-18 21:24:13.33 spid22s A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

    2010-05-18 21:24:13.33 spid23s

    but the checkdb commands right before this (also in between the stack dumps) are different every time, and always say complete without errors

  • Might be time to contact CSS at this point. Those look nasty.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • this is useful , please check http://support.microsoft.com/kb/981273

  • GilaMonster (5/18/2010)


    Might be time to contact CSS at this point. Those look nasty.

    Past the time to be on the phone with Microsoft I think . . .

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply