Search Engine: Elastic

Article ID: 130861, created on May 23, 2017, last review on May 23, 2017

  • Applies to:
  • Operations Automation 6.0

Symptoms

All Windows service nodes are unavailable.

When opening the General screen for any of the nodes, the message is shown:

Host is not functioning

When trying to communicate with a service node, netstat shows a communication issue on the Management Node itself, it is impossible to connect to a certain port:

C:\>netstat -ano | findstr 8382
  TCP    192.168.10.12:53679   192.168.10.12:8382    SYN_SENT        13772

Port 8382 is listened by WinHostControl SC:

[root@core ~]# ps aux | grep WinHost | grep -v grep
pemuser  18338  0.0  0.0 111240     8 ?        Ssl  May11   0:00 /usr/local/pem/bin/SoLoader --sc_id=82 --sc="WinHostControl:/usr/local/pem/libexec/WinHostControl.so.6.0.5.21" --sc_port=8382 --props-file="/usr/local/pem/etc/pleskd.props" --interfaces=SDK::HostControl::HandleRemoveHostRequest,WinHostControl,SDK::WPE::ProcessWPERequest,SDK::HostControl::PerformHostOperations,SDK::RemoveHostObserver,SDK::InstallAgentObserver,SDK::TaskProcessor::ExecuteTask

Cause

WinHostControl SC unavailability, the exact cause is to be determined in each particular case.

Resolution

Kill the SC process to restore its functionality:

# kill -9 18338

In few minutes it will be restarted by the watchdog service, and the connectivity to service nodes will gradually be restored.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF