Автор Тема: падает cluster service  (Прочитано 3825 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн anton.lazutkin

  • Начинающий
  • *
  • Сообщений: 49
  • Рейтинг: 0
  • Пол: Мужской
    • Просмотр профиля
  • Откуда: Брянск
падает cluster service
« : 12 сентября 2018, 17:18:27 »
всем привет. периодически падает служба кластера на нескольких серверах. в журнале вижу такую ошибку: The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.

но не могу понять, что является причиной падения.

Оффлайн Triangle

  • Модераторы
  • Олдфаг
  • *****
  • Сообщений: 7128
  • Рейтинг: 48
  • Пол: Мужской
  • Откуда: замкадыш
падает cluster service
« Ответ #1 : 12 сентября 2018, 18:44:52 »
Eventv ID? 1146?

Цитировать
Resolve
Check resource DLL
Check to see which resource DLL is causing the issue and report the problem to the resource vendor. Consider configuring the resource to run in its own Resource Monitor. Note that while a problem with a resource DLL will not stop the Cluster service from running, it can prevent other resource DLLs from running unless the resource runs in its own Resource Monitor.

If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering."

To perform these procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Configuring a resource to run in its own Resource Monitor
To configure a resource to run in its own Resource Monitor:

To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
Click the clustered service or application that contains the resource you want to configure.
Right-click the resource, and then click Properties.
Click the Advanced Policies tab.
Select Run this resource in a separate Resource Monitor.
Opening Event Viewer and viewing events related to failover clustering
To open Event Viewer and view events related to failover clustering:

If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
Verify
To perform this procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Verifying that the Cluster service is started on all the nodes in a failover cluster
To verify that the Cluster service is started on all the nodes in a failover cluster:

To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then click Nodes.
View the status for each node. If a node is Up, the Cluster service is started on that node.
Another way to check whether the Cluster service is started is to run a command on a node in the cluster.

Using a command to check whether the Cluster service is started on a node
To use a command to check whether the Cluster service is started on a node:

On the node that you are checking, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

Type:

CLUSTER NODE /STATUS

If the node status is Up, the Cluster service is started on that node.
Тетрис научил нас жизненно важному пониманию, успехи исчезают, ошибки накапливаются.