October 10, 2005 at 2:28 am
We have Windows Server 2003, SQL Server 2000 Ent. SP4 on both sql server nodes
After weekend I came to work and saw that both virtual sql server instances sit on one node(2). When I checked sql server logs of that instance which failed to another node(2) I saw next errors:
----------------------------------------------------------------------------------------------------------
2005-10-09 01:18:12.63 spid55 WARNING: Failed to reserve contiguous memory of Size= 65536.
2005-10-09 01:18:12.63 spid55 Buffer Distribution: Stolen=1195 Free=35340 Procedures=2780
Inram=0 Dirty=9307 Kept=0
I/O=0, Latched=163, Other=200431
2005-10-09 01:18:12.63 spid55 Buffer Counts: Commited=249216 Target=249216 Hashed=209901
InternalReservation=411 ExternalReservation=29380 Min Free=128 Visible= 249216
2005-10-09 01:18:12.63 spid55 Procedure Cache: TotalProcs=256 TotalPages=2780 InUsePages=922
2005-10-09 01:18:12.63 spid55 Dynamic Memory Manager: Stolen=3623 OS Reserved=1008
OS Committed=986
OS In Use=984
Query Plan=2743 Optimizer=0
General=1508
Utilities=85 Connection=105
2005-10-09 01:18:12.63 spid55 Global Memory Objects: Resource=1117 Locks=64
SQLCache=64 Replication=2
LockBytes=2 ServerGlobal=24
Xact=49
2005-10-09 01:18:12.63 spid55 Query Memory Manager: Grants=1 Waiting=0 Maximum=185706 Available=155974
2005-10-09 01:18:13.07 spid55 WARNING: Failed to reserve contiguous memory of Size= 65536.
2005-10-09 01:18:13.07 spid55 Buffer Distribution: Stolen=1785 Free=34853 Procedures=2677
Inram=0 Dirty=9307 Kept=0
I/O=0, Latched=163, Other=200431
2005-10-09 01:18:13.07 spid55 Buffer Counts: Commited=249216 Target=249216 Hashed=209901
InternalReservation=411 ExternalReservation=28932 Min Free=128 Visible= 249216
2005-10-09 01:18:13.07 spid55 Procedure Cache: TotalProcs=254 TotalPages=2677 InUsePages=842
2005-10-09 01:18:13.07 spid55 Dynamic Memory Manager: Stolen=3662 OS Reserved=1008
OS Committed=986
OS In Use=984
Query Plan=2720 Optimizer=0
General=1533
Utilities=122 Connection=105
2005-10-09 01:18:13.07 spid55 Global Memory Objects: Resource=1117 Locks=64
SQLCache=64 Replication=2
LockBytes=2 ServerGlobal=24
Xact=49
2005-10-09 01:18:13.07 spid55 Query Memory Manager: Grants=1 Waiting=0 Maximum=185706 Available=155974
2005-10-09 01:18:19.11 logon Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
2005-10-09 01:18:19.24 logon Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
2005-10-09 01:48:02.89 logon Login failed for user 'vidmantasg'.
2005-10-09 07:40:04.82 logon Login failed for user 'u nerius'.
2005-10-09 10:01:54.67 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:05:59.72 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:05:59.72 spid11 ERROR: Launch of System Task 'OnDemand' failed!
2005-10-09 10:07:44.95 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:45.95 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:46.97 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:48.11 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:49.11 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:50.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:51.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:52.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:53.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:54.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:55.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:56.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:57.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:58.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:07:59.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:00.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:01.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:02.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:03.12 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:04.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:05.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:06.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:07.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:08.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:09.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:10.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:11.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:12.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:13.22 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:14.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:15.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:16.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:17.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:18.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:19.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:20.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:21.23 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:22.25 server SQL Server could not spawn process_loginread thread.
2005-10-09 10:08:23.08 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
-------------------------------------------------------------------------------------------------------
I've tried manulally failover that sql server instance back to it's original location(first node), but it failover back again to the second node(2). The problem was solved after restarting the first node and then manual failover was successful. Any ideas what are causes of this? This event happens second time to me..
Thanks in advance
October 11, 2005 at 9:44 am
It looks to me that your server (node) ran out of memory. The reboot frees up the memory temporarily, but I'd check out the RAM on your cluster. You may also want to use performance monitor to watch the memory. Do you ever do failover tests? It may have alerted you to the issue sooner.... Hopefully you have the same amount of RAM on both nodes. It's possible that one of the nodes is just more active than the other... worth looking into.
Linda
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply