You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Michael Miklavcic (JIRA)" <ji...@apache.org> on 2018/01/12 16:11:00 UTC
[jira] [Created] (METRON-1400) Elasticsearch service check fails in
Ambari
Michael Miklavcic created METRON-1400:
-----------------------------------------
Summary: Elasticsearch service check fails in Ambari
Key: METRON-1400
URL: https://issues.apache.org/jira/browse/METRON-1400
Project: Metron
Issue Type: Bug
Reporter: Michael Miklavcic
This is service check, not to be confused with the status check. ie,
* service check = dropdown in Ambari service when you click "service actions"- there is an option labeled "service check" which does a more rigorous check on the service than simply an on/off check.
* status check = the green checkbox or red exclamation next to the service name in Ambari indicating if the thing is running.
{code}
I built a 12-node CentOS7 cluster with this fix. Noticed that ES service check failed with the following error:
stderr:
Traceback (most recent call last):
File "/var/lib/ambari-agent/cache/common-services/ELASTICSEARCH/5.6.2/package/scripts/service_check.py", line 77, in <module>
ServiceCheck().execute()
File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 329, in execute
method(env)
File "/var/lib/ambari-agent/cache/common-services/ELASTICSEARCH/5.6.2/package/scripts/service_check.py", line 35, in service_check
Logger.info("Running Elastic search service check", file=sys.stdout)
TypeError: info() got an unexpected keyword argument 'file'
stdout:
Command failed after 1 tries
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)