Details
-
Bug
-
Status: Done
-
Major
-
Resolution: Done
-
0.4.2
-
None
Description
The Metron service check can often use the incorrect hostname when checking the Alerts UI, Management UI, and REST services.
Ambari can run the service check on any node in the cluster, not just the node the service is actually running on. The service check code currently uses the hostname on which the service check is running. If the service is not actually installed on that host, the service check will incorrectly fail.
The service check code should be updated to find the hostname where the service is installed and use that hostname.
For example, here is a log of a service check that is looking on the wrong host for the Metron REST service.
2017-12-08 17:11:30,433 - Checking connectivity to REST application 2017-12-08 17:11:30,434 - Checking HTTP connectivity; host=hcpua-10.openstacklocal, port=8082, user=metron cmd=curl -sS --max-time 3 hcpua-10.openstacklocal:8082 2017-12-08 17:11:30,434 - Execute['curl -sS --max-time 3 hcpua-10.openstacklocal:8082'] {'logoutput': False, 'tries': 3, 'user': 'metron', 'try_sleep': 5} 2017-12-08 17:11:30,471 - Retrying after 5 seconds. Reason: Execution of 'curl -sS --max-time 3 hcpua-10.openstacklocal:8082' returned 7. curl: (7) Failed to connect to hcpua-10.openstacklocal port 8082: Connection refused 2017-12-08 17:11:35,519 - Retrying after 5 seconds. Reason: Execution of 'curl -sS --max-time 3 hcpua-10.openstacklocal:8082' returned 7. curl: (7) Failed to connect to hcpua-10.openstacklocal port 8082: Connection refused
Attachments
Issue Links
- links to