[
https://issues.apache.org/jira/browse/METRON-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883820#comment-15883820
]
ASF GitHub Bot commented on METRON-642:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/406
@DimDroll , yes, I just noticed in PR#405 that the comments were being
correctly cc'ed to Jira even tho the title was different. Don't know. Maybe
the received wisdom about the titles having to be exactly the same is wrong?
Perhaps it is sufficient to either (a) have the correctly hyphenated and
capitalized Jira key (METRON-nnn) at the beginning of the PR title, or (b) have
a link to the PR in the Jira?
Can anyone else out there give a more precise answer for the requirement?
Thanks.
> Correct path to ES gc log file
> ------------------------------
>
> Key: METRON-642
> URL: https://issues.apache.org/jira/browse/METRON-642
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Dima Kovalyov
> Priority: Minor
> Fix For: 0.3.1
>
>
> ==== First ====
> Currently in Metron Mpack es.ip in Metron configuration is set to: es_url.
> Which is incorrect and will fail, instead it should be replaced with:
> "es.ip": "<elasticsearch_master_hostname>",
> "es.port": "9300",
> But I do not know how to get elasticsearch_master_hostname. Also, value of
> es.port seems like can be defaulted to es_binary_port or even omitted as it
> is already specified in es_binary_port.
> This should be chanted in:
> https://github.com/apache/incubator-metron/blob/master/metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/configuration/metron-env.xml
> On line 208.
> ==== First ====
> ==== Second ====
> In file
> https://github.com/apache/incubator-metron/blob/master/metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/ELASTICSEARCH/2.3.3/configuration/elastic-sysconfig.xml
> On lines 93 and 95 symbols "/" is forgotten. e.g:
> ES_JAVA_OPTS="-verbose:gc -Xloggc:{{log_dir}}/elasticsearch_gc.log
> -XX:-CMSConcurrentMTEnabled
> should be:
> ES_JAVA_OPTS="-verbose:gc -Xloggc:{{log_dir}}/elasticsearch_gc.log
> -XX:-CMSConcurrentMTEnabled
> ==== Second ====
> ==== Third ====
> After ES install it will fail to start with error"
> {code}
> Likely root cause: java.nio.file.AccessDeniedException:
> /etc/elasticsearch/scripts
> {code}
> The reason for the is root permission on these files:
> {code}
> # ls -la /etc/elasticsearch
> ...
> -rwxr-x---. 1 root elasticsearch 2571 May 12 09:24 logging.yml
> drwxr-x---. 2 root elasticsearch 4096 May 17 11:49 scripts
> {code}
> I was not able to trace down origin of these files, so do not know how to fix
> it.
> ==== Third ====
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
