Skip to Content
0
Former Member
Oct 16, 2014 at 01:57 PM

db error caused by dbcc memusage

83 Views

issue dbcc memusage and system is frozen, then got following error

00:00000:00000:2014/10/16 09:50:23.91 kernel secleanup: time to live expired on engine 1

00:00000:00009:2014/10/16 09:50:23.93 kernel Terminating the listener with protocol tcp, host myserver, port 4101 because the listener execution context is located on engine 1, which is not responding.

00:00000:00009:2014/10/16 09:50:23.93 kernel ************************************

00:00000:00009:2014/10/16 09:50:23.93 kernel curdb = 1 tempdb = 2 pstat = 0x200

00:00000:00009:2014/10/16 09:50:23.93 kernel lasterror = 0 preverror = 0 transtate = 1

00:00000:00009:2014/10/16 09:50:23.93 kernel curcmd = 0 program =

00:00000:00009:2014/10/16 09:50:23.93 kernel pc: 0x0000000000cd0847 upsleepgeneric+0x437()

00:00000:00009:2014/10/16 09:50:23.93 kernel pc: 0x0000000000cadcae listener_checkagain+0x1be()

00:00000:00009:2014/10/16 09:50:23.93 kernel pc: 0x0000000000cad938 listener+0x338()

00:00000:00009:2014/10/16 09:50:23.93 kernel pc: 0x0000000000cce388 kpstartproc+0x48()

00:00000:00009:2014/10/16 09:50:23.93 kernel end of stack trace, spid 10, kpid 1638425, suid 0

00:00000:00009:2014/10/16 09:50:23.93 kernel Started a new listener task with protocol tcp, host myserver, port 4101.

then system repair itself within 1-2 minutes.

dbcc memusage is fine on another staging server.

what's the possible reason for this? hardware?