[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user anandsubbu commented on the issue: https://github.com/apache/metron/pull/894 +1 thank you @mmiklavc. Spun up a 12-node Centos 7 cluster with the latest fix and validated the following: * Did 'Stop All Services' -> no issues seen with ES and Kibana services stop any longer. * Kerberized the cluster -> the process completed successfully and all services came up fine. The issues reported in the JIRA ticket now stand resolved. ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user cestella commented on the issue: https://github.com/apache/metron/pull/894 I'm +1 on this at this point, but suggest we wait until @anandsubbu gives his +1. ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user anandsubbu commented on the issue: https://github.com/apache/metron/pull/894 > I'd like to treat this as distinct from the status check if that seems reasonable to you. I have to admit, I didn't even know the service check piece existed until now. Sure, it makes sense to address this as a separate issue. ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/894 fwiw, this service check also fails in full dev. Git history shows me as creating the file because I moved the entire directory (5.6.2 name change) as part of the ES upgrade, but this code hasn't been touched since September 2016 per `git log --follow`. I'm creating another ticket for it. https://issues.apache.org/jira/browse/METRON-1400 ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/894 Oh, I see what that is. This appears to be a neglected piece of code. ES has this but Kibana does not, for instance. The metainfo.xml allows you to add "commandScript" items that are listed in the service drop-down menu. But this is distinct from the status check which provides the green checkbox vs red exclamation appearing next to a service name in the Ambari services list. This is ES  This is Kibana  I'd like to treat this as distinct from the status check if that seems reasonable to you. I have to admit, I didn't even know the service check piece existed until now. ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/894 @anandsubbu did this ever work with CentOS 7 from Apache master? I didn't touch that service_check.py file, and furthermore I see there are hardcoded ports for ES. ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/894 ### Testing 1. Spin up full dev 2. Check that ES and Kibana are up as normal 3. Try the following operations - all should succeed without error in Ambari - Restart Kibana - Restart ES - Stop Kibana - Stop ES - Start Kibana - Start ES ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/894 Eureka, I think we got it. Thanks @cestella for the tag team session on digging through the Ambari source. ---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/894
Upon investigation, this looks ok. But there is a permissions issue with
the service script. We have some environments that don't have this issue so I'm
looking for an appropriate place to correct this.
```
INFO 2018-01-10 19:51:59,540 PythonReflectiveExecutor.py:65 - Reflective
command failed with exception:
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
line 57, in run_file
imp.load_source('__main__', script)
File
"/var/lib/ambari-agent/cache/common-services/ELASTICSEARCH/5.6.2/package/scripts/elastic_master.py",
line 94, in
Elasticsearch().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/ELASTICSEARCH/5.6.2/package/scripts/elastic_master.py",
line 82, in status
raise ExecutionFailed(err_msg, rc, out, err)
ExecutionFailed: Execution of 'service elasticsearch status' returned 126
```
```
[elasticsearch@node1 ambari-agent]$ service elasticsearch status
env: /etc/init.d/elasticsearch: Permission denied
```
---
[GitHub] metron issue #894: METRON-1326: Metron deploy with Kerberos fails on Ambari ...
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/894 full dev still runs Ambari 2.4.2.0, so this approach may not work across 2.4 -> 2.5. ES and Kibana services are running, but they show as stopped in the Ambari UI.  ---
