[
https://issues.apache.org/jira/browse/METRON-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622885#comment-15622885
]
ASF GitHub Bot commented on METRON-514:
---------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/323#discussion_r85796965
--- Diff: metron-deployment/roles/yaf/tasks/yaf.yml ---
@@ -48,7 +48,3 @@
- name: Install init.d service script
template: src=yaf dest=/etc/init.d/yaf mode=0755
-
--- End diff --
Sorry, late to the party. Had to expand the 'thingie' to see that prior
conversation.
If I remember correctly, the original reason that was added was because if
you just deploy and then run 'service yaf start' on CentOS 7, Systemd would
fail the service immediately. Doing the `enable` made Systemd aware of the
older SysV script, so that when we start it later in the deployment, it works.
But this was probably not the best way to do it, as this has the effect of
starting the service on boot, which is not what we want.
I'm good with taking this out (as you have it), since your testing has been
successful without it.
> Snort kafka topic fails to get any data on a setup running for several days
> ---------------------------------------------------------------------------
>
> Key: METRON-514
> URL: https://issues.apache.org/jira/browse/METRON-514
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> After a cluster has been running for a while, data will suddenly stop being
> written to the snort Kafka topic. Other topics like yaf and bro continue to
> work. The difference between those sensors and snort is that snort logs are
> fed into Kafka with Flume.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
