July 2, 2012 at 2:05 am
Hi Folks.
I have a singularity 8 node cluster. As of now we are facing an issue with one of the node while trying to fail over the services on to it. When we try to failover, the services come back online on to the next preferred node and does not go to the preferred node. Then I logged in with that particular node name(Node 7) and saw that SQL Agent is in stopped state and is manual. So I tried starting it but had no luck on that either. It says "Cannot start the SQL Agent".
OS Version: Windows 2008 R2.
Service Pack 1
Below are few error that I captured while doing this activity. Please give me your expert input to resolve my production issue.
Cluster Error Logs:
Error 1: "Cluster resource 'SQL IP Address 1 (ServerName)' in clustered service or application 'SQL Server (ServerName)' failed.”
Error 2: "The Cluster service failed to bring clustered service or application 'SQL Server (ServerName)' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.”
Event Viewer Logs:
"1) FCB::Open failed: Could not open file E:\ServerName\Data\MSSQL\MSSQL10_50.ServerName\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2) FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\ServerName\Data\MSSQL\MSSQL10_50.ServerName\MSSQL\DATA\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
3) LogWriter: Operating system error 21(The device is not ready.) encountered.
4) The log for database 'master' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
5) SQL Server failed to communicate with filter daemon launch service (Windows error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it). Full-Text filter daemon process failed to start. Full-text search functionality will not be available."
July 2, 2012 at 8:37 am
looks like disk issues.
Which nodes does the instance come online on?
Have you checked that all required storage has been presented to all the nodes that are participating in the clustered instance?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 4, 2012 at 2:22 am
The services come online on all the nodes except node 7. I found the bottle neck. Its the corrupted NIC drives not allowing the services to communicate with the node. We fixed it anyways.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply