Jan-Otto Kröpke
d819362150
Every optional collector of the mixin now has alerts, generated only with that collector enabled in _config.collectors: clock source, disk drive status, page file usage, license status, scheduled task results, pending updates, Hyper-V WMI and replication health, failover cluster nodes, resources, groups and shared volumes, Storage Spaces pool and virtual disk health, DHCP scope exhaustion and DNS zone transfer failures. The alerts of the pagefile, diskdrive and license collectors join the memory, disk and system groups; the other collectors get a group of their own. New knobs: taskSelector, sharedVolumeSelector, pagefileUsageThreshold, dhcpScopeFreeWarningThreshold, dhcpScopeFreeCriticalThreshold and updatePendingDuration. The test configuration enables every optional collector and tests/optional.test.yaml covers the new alerts. Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
1.9 KiB
title
| title |
|---|
| WindowsClusterResourceFailed |
Meaning
The failover cluster reports the resource resource of type type in the
group resource_group as failed for five minutes. The alert needs the
mscluster collector and fires once per reporting node, named by the
instance label. A failed resource has exhausted its restart attempts on the
current node, or its group has reached its failover threshold.
Impact
The role that depends on the resource is down: a clustered disk, IP address, network name, file share, SQL Server instance or virtual machine. Other resources in the same group that depend on it are offline too.
Diagnosis
-
Inspect
windows_mscluster_resource_statefor the group andwindows_mscluster_resourcegroup_stateandwindows_mscluster_resource_owner_nodeto see where the group is and whether the whole group failed. -
On a cluster node, read the resource and the reason:
Get-ClusterResource -Name '<resource>' | Format-List * Get-ClusterResource -Name '<resource>' | Get-ClusterParameter Get-ClusterLog -TimeSpan 30 -Destination . Get-WinEvent -LogName System -FilterXPath "*[System[Provider[@Name='Microsoft-Windows-FailoverClustering'] and (EventID=1069 or EventID=1205)]]" -MaxEvents 20Event 1069 names the failed resource and its error code.
-
Check the dependency of the resource: a disk that is not reachable from the node, an IP address whose network is down, a network name whose computer object in Active Directory is missing or disabled, or an application whose service fails to start.
Mitigation
Fix the dependency, then bring the resource online with
Start-ClusterResource, or move the group to another node with
Move-ClusterGroup. Review the restart and failover thresholds of the
resource if it failed because of a transient problem. Confirm the resource
state returns to online and the group is online.