0

SQL Server 2012 running on a Windows 2012 Failover Cluster Instance.

(**The cluster contains only a single node. Yes, I know that's terrible. No, it wasn't my decision....)

The issue is that at seemingly random times overnight (our period of highest network activity) SQL Server will go down.

The SQL Server error logs point to the cluster ordering it to stop:

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.

The Cluster log appears to show that it's doing so because it claims SQL Server failed:

enter image description here

What I'd really be interested in finding is WHY the cluster thinks SQL Server failed. Have been poking through the various failover clustering logs in Event Manager and haven't found anything yet that indicates this. Any concrete proof I can bring back to the server team and say "this is because of network" or "this is because of quorum" or whatever the reason might be, would be greatly appreciated.

UPDATE

Discovered how to view "informational" entries in the cluster event log. Not sure if this is an indicator or not, but lots of entries mentioning "Netbios: Slow Operation".

I see an entry saying "Endpoint is up" 10 seconds before first entries discussing bringing the node offline.

Improve this question
3
  • What is your quorum configuration? I assume node majority--ie, the only voter is the one node in the WSFC? Also, try checking the Windows event log for additional information. If there is a network/system issue, you might find helpful information there.
    – AMtwo
    Commented Nov 7, 2016 at 17:56
  • Correct, Node majority. Just updated the original question with more info I found from the log.
    – Bob Pusateri
    Commented Nov 7, 2016 at 18:25
  • Have you generated cluster.log to see if it gives you any insight?
    – Ed Leighton-Dick
    Commented Nov 7, 2016 at 18:48

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .