re: Non-yielding IOCP Listener - Stack Dump analysis

Graham Kent [MSFT] — Tue, 12 Jan 2010 09:57:37 GMT

Hi, we would need to look at the dump produced to understand what was going on here. If you contact me through the email section at the top of the page we can discuss this offline.

re: Non-yielding IOCP Listener - Stack Dump analysis

bnvbxb — Thu, 07 Jan 2010 08:44:37 GMT

Hi,

I have a similar issue.Our Sql Server is hanging and following error is found in the log file..

Date,Source,Severity,Message

01/07/2010 08:58:28,spid4s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

01/07/2010 08:58:28,spid4s,Unknown,SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.

01/07/2010 08:58:18,Logon,Unknown,Login failed for user 'upgnetuser'. Only administrators may connect at this time. [CLIENT: 172.16.160.46]

01/07/2010 08:58:18,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:58:08,Logon,Unknown,Login failed for user 'UPP\MusthafaK'. Only administrators may connect at this time. [CLIENT: <named pipe>]

01/07/2010 08:58:08,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:58:07,Logon,Unknown,Login failed for user 'concept'. Only administrators may connect at this time. [CLIENT: <named pipe>]

01/07/2010 08:58:07,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:58:00,Logon,Unknown,Login failed for user 'upgnetuser'. Only administrators may connect at this time. [CLIENT: 172.16.160.46]

01/07/2010 08:58:00,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:57:59,spid12s,Unknown,Service Broker manager has shut down.

01/07/2010 08:57:35,Logon,Unknown,Login failed for user 'upgnetuser'. Only administrators may connect at this time. [CLIENT: 172.16.160.46]

01/07/2010 08:57:35,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:57:35,Logon,Unknown,Login failed for user 'UPP\prakashm'. Only administrators may connect at this time. [CLIENT: <named pipe>]

01/07/2010 08:57:35,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:57:21,Logon,Unknown,Login failed for user 'UPP\upsqlrs'. Only administrators may connect at this time. [CLIENT: 172.16.160.66]

01/07/2010 08:57:21,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:57:09,Logon,Unknown,Login failed for user 'UPP\upsqlrs'. Only administrators may connect at this time. [CLIENT: 172.16.160.66]

01/07/2010 08:57:09,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:57:00,Logon,Unknown,Login failed for user 'UPP\upsqlrs'. Only administrators may connect at this time. [CLIENT: 172.16.160.66]

01/07/2010 08:57:00,Logon,Unknown,Error: 18451<c/> Severity: 14<c/> State: 1.

01/07/2010 08:57:00,spid57,Unknown,The client was unable to reuse a session with SPID 57<c/> which had been reset for conection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

01/07/2010 08:57:00,spid57,Unknown,Error: 18056<c/> Severity: 20<c/> State: 23.

01/07/2010 08:57:00,spid53,Unknown,The client was unable to reuse a session with SPID 53<c/> which had been reset for conection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

01/07/2010 08:57:00,spid53,Unknown,Error: 18056<c/> Severity: 20<c/> State: 23.

01/07/2010 08:57:00,Logon,Unknown,Login failed for user 'UPP\upsqlrs'. [CLIENT: 172.16.160.66]

01/07/2010 08:57:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 23.

01/07/2010 08:57:00,Logon,Unknown,Login failed for user 'UPP\upsqlrs'. [CLIENT: 172.16.160.66]

01/07/2010 08:57:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 23.

01/07/2010 08:56:52,spid84,Unknown,Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.

01/07/2010 08:56:52,Server,Unknown,IO Completion Listener (0x15b4) Worker 0x00D0E0E8 appears to be non-yielding on Node 0. Approx CPU Used: kernel 0 ms<c/> user 0 ms<c/> Interval: 15171.

01/07/2010 08:56:52,Server,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.

01/07/2010 08:56:43,Server,Unknown,Stack Signature for the dump is 0x00000379

01/07/2010 08:56:43,Server,Unknown,* Short Stack Dump

01/07/2010 08:56:43,Server,Unknown,* -------------------------------------------------------------------------------

01/07/2010 08:56:43,Server,Unknown,* *******************************************************************************

01/07/2010 08:56:43,Server,Unknown,*

01/07/2010 08:56:43,Server,Unknown,* Non-yielding IOCP Listener

01/07/2010 08:56:43,Server,Unknown,*

01/07/2010 08:56:43,Server,Unknown,* 01/07/10 08:56:43 spid 0

01/07/2010 08:56:43,Server,Unknown,* BEGIN STACK DUMP:

01/07/2010 08:56:43,Server,Unknown,*

01/07/2010 08:56:43,Server,Unknown,* *******************************************************************************

01/07/2010 08:56:43,Server,Unknown,***Stack Dump being sent to D:\SQLData\MSSQL.1\MSSQL\LOG\SQLDump0009.txt

01/07/2010 08:56:43,Server,Unknown,**Dump thread - spid = 0<c/> PSS = 0x00000000<c/> EC = 0x00000000

01/07/2010 08:56:43,Server,Unknown,Using 'dbghelp.dll' version '4.0.5'

The Server has a 4gb RAM and max memory set for sql server is the default value '2147483647'.The SQL works fine for sometime when its restarted and goes back to hanging again.Please help me with a solution to solve this issue?can this be a memory issue when sql server is allocated with default value.?

Thanks,

bnvbxb