April 21, 2010 at 9:14 am
Currently, we only have 1 Cluster (SQLCLU1). This weekend I was going to add a failover node; SQLCLU2. So as of today there was a failover node. Here are the errors I copied out of the event log:
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:4/21/2010
Time:9:14:28 AM
User:N/A
Computer:SQLCLUSTER1
Description:
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4b 4a 00 40 01 00 00 00 KJ.@....
0008: 0c 00 00 00 53 00 51 00 ....S.Q.
0010: 4c 00 56 00 53 00 65 00 L.V.S.e.
0018: 72 00 76 00 65 00 72 00 r.v.e.r.
0020: 31 00 00 00 00 00 00 00 1.......
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:4/21/2010
Time:9:14:28 AM
User:N/A
Computer:SQLCLUSTER1
Description:
[sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4b 4a 00 40 01 00 00 00 KJ.@....
0008: 0c 00 00 00 53 00 51 00 ....S.Q.
0010: 4c 00 56 00 53 00 65 00 L.V.S.e.
0018: 72 00 76 00 65 00 72 00 r.v.e.r.
0020: 31 00 00 00 00 00 00 00 1.......
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(3)
Event ID:19019
Date:4/21/2010
Time:9:14:28 AM
User:N/A
Computer:SQLCLUSTER1
Description:
[sqsrvres] OnlineThread: QP is not online.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4b 4a 00 40 01 00 00 00 KJ.@....
0008: 0c 00 00 00 53 00 51 00 ....S.Q.
0010: 4c 00 56 00 53 00 65 00 L.V.S.e.
0018: 72 00 76 00 65 00 72 00 r.v.e.r.
0020: 31 00 00 00 00 00 00 00 1.......
What is the main cause of these errors other than there is not a failover istalled yet?
Thanks, RonKin
April 22, 2010 at 3:52 am
Hi,
do you have any other error in the SQL error log or in the windows event logs at around the same time?
Seth
April 22, 2010 at 7:17 am
No logs with any information pertinent to the issue; the logs only showed activity until 7AM. After about 4 hours of researching the internet I came across a blog, which I share with you. The document stated ; ‘during SQL Maintenance there could be “a bulk load going on” at the same time’ I was trouble shooting the dotCMS backup failure around the time of failure. So, I'm about 90% sure that is what caused SQLCLUSTER1 to go down.
Thank you so much for your help.
KR,
RonKin
April 22, 2010 at 7:23 am
Glad you found the cause.
One thing I had problems with on a Cluster before - and it took months to sort out - was priority boost.
The cluster had been set to priority boost and this is a not recommended for Cluster servers.
This caused the cluster service to stop and start the SQL Service - about once a month.
I took priority boost off and haven't had any problems with this for about a year.
To set it to 0 you can run this
sp_configure 'priority boost',0;
go
reconfigure;
It will require a service restart to take affect.
Seth
April 22, 2010 at 7:29 am
Will do that. Thanks for your help and have a great afternoon.
RonKin
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply