[ 
https://issues.apache.org/jira/browse/METRON-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222470#comment-16222470
 ] 

ASF GitHub Bot commented on METRON-1261:
----------------------------------------

Github user ottobackwards commented on the issue:

    https://github.com/apache/metron/pull/805
  
    @JonZeolla.  Followed the steps, and in my monitor storm logs 'window' i 
have many of the following:
    
    ```bash
    [root@node1 ~]# tail -f 
/var/log/storm/workers-artifacts/indexing-*/*/worker.log | grep -i 
"org.elasticsearch.index.mapper.MapperParsingException: failed to parse"
    org.elasticsearch.index.mapper.MapperParsingException: failed to parse 
[ip_dst_addr]
    org.elasticsearch.index.mapper.MapperParsingException: failed to parse 
[ip_dst_addr]
    org.elasticsearch.index.mapper.MapperParsingException: failed to parse 
[ip_dst_addr]
    ```
    
    I don't know if I should expect these or not?


> Apply bro security patch
> ------------------------
>
>                 Key: METRON-1261
>                 URL: https://issues.apache.org/jira/browse/METRON-1261
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Jon Zeolla
>            Assignee: Jon Zeolla
>
> Bro released a 2.4.2 update with a security patch applied, so we should begin 
> using that by default.
> I have also updated METRON-1088, as it is to update bro from 2.4.x to 2.5.x, 
> but assumed we would be upgrading from 2.4.1.  That bigger upgrade is not 
> being done now because, last I visited it, there were dependency issues due 
> to our use of CentOS 6 in full-dev.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to