"V-383-50513-5778 Communication failure with managed host" appears when trying to refresh a Managed Host
book
Article ID: 100034147
calendar_today
Updated On:
Description
Error Message
V-383-50513-5778 Communication failure with managed host
Authorization Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
\r\n","STATE":"FAILED","PROGRESS":100}}
2017-06-05 17:33:03 [error] 23890 refresh_host: Rolling back job jobs::refresh_host
2017-06-05 17:33:03 [debug] 23890 refresh_host: Triggering appropriate discoveries
2017-06-05 17:33:03 [debug] 23890 refresh_host: Summarizing
2017-06-05 17:33:03 [debug] 23890 refresh_host: Final Packet = {"RESULT":{"UMI":"
V-383-50513-5778","ERROR":"Communication failure with managed host.","RETURNCODE":100,"TASKID":null,"RESULT":null,"NAME":"refresh_host"}}
Cause
This occurs if the version of the Managed Host (package VRTSsfmh) is earlier than the CS, and this issue
ONLY applies to a newly-installed 7.2 CS, not one that has been upgraded from a previous version and has 7.0 MHs already added.
The issue can be verified by the VRTSsfmh log from the MH, as shown below.
Excerpt from /var/opt/VRTSsfmh/logs/mhrun.log:
2017-06-05 17:33:03 [debug] 23890 refresh_host: Set HOST_CONFIG_MAPPING.State = [4], host_id [{0001b4b5-2f66-f150-0000-000000000000}], type [AGENT]
2017-06-05 17:33:03 [debug] 23890 refresh_host: json = {"JOB":{"ERROR":"Communication failure with managed host.","ISHIDDEN":0,"RETURNCODE":4,"NAME":"refresh_host","OUTPUT":"HTTP/1.1 401 Unauthorized\r\nWWW-Authenticate: Basic realm=\"cwxticm5\"\r\n\r\n 401 Authorization Required Authorization Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
\r\n","STATE":"FAILED","PROGRESS":100}}
2017-06-05 17:33:03 [error] 23890 refresh_host: Rolling back job jobs::refresh_host
2017-06-05 17:33:03 [debug] 23890 refresh_host: Triggering appropriate discoveries
2017-06-05 17:33:03 [debug] 23890 refresh_host: Summarizing
2017-06-05 17:33:03 [debug] 23890 refresh_host: Final Packet = {"RESULT":{"UMI":"V-383-50513-5778","ERROR":"Communication failure with managed host.","RETURNCODE":100,"TASKID":null,"RESULT":null,"NAME":"refresh_host"}}
Resolution
Upgrade the MH (package VRTSsfmh) to 7.2 and re-add the host to the CS.
If this is not possible, as a workaround, set up a manual trust:
-
On a Linux managed host, enter the following commands:
export EAT_HOME_DIR=/opt/VRTSsfmh
export EAT_DATA_DIR=/var/opt/VRTSsfmh/sec
/opt/VRTSsfmh/bin/vssatbin setuptrust -b CS_FQDN:14545 -s high
-
On a Windows managed host, enter the following commands:
set EAT_HOME_DIR=C:\Program Files\Veritas\VRTSsfmh
set EAT_DATA_DIR=C:\ProgramData\veritas\VRTSsfmh\sec
vssatbin setuptrust -b CS_FQDN:14545 -s high
Issue/Introduction
After adding the Managed Host (MH) successfully on a Veritas InfoScale Operations Manager (VIOM) 7.2 Central Server (CS), the MH is not refreshed and the error message "V-383-50513-5778 Communication failure with managed host" appears.
Was this article helpful?
thumb_up
Yes
thumb_down
No