[Bro-Dev] [JIRA] (BIT-1180) Input framework subsiquient REREAD fails after file update

Bernhard Amann (JIRA) jira at bro-tracker.atlassian.net
Fri May 30 16:23:07 PDT 2014


    [ https://bro-tracker.atlassian.net/browse/BIT-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704#comment-16704 ] 

Bernhard Amann commented on BIT-1180:
-------------------------------------

For input streams that have re-read enabled, should we perhaps not really die on errors, but still try to re-read the file upon each change to it? So if there is one file version that has whatever error, and latter ones don't have it, we will pick up the new version, even if we failed before?

> Input framework subsiquient REREAD fails after file update 
> -----------------------------------------------------------
>
>                 Key: BIT-1180
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1180
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: Bro
>    Affects Versions: 2.2
>            Reporter: Aashish Sharma
>            Assignee: Bernhard Amann
>            Priority: High
>              Labels: input-framework
>             Fix For: 2.4
>
>
> I have a file that gets updated every hour and I am using it as a feed into bro using input framework. Every hour I write a list of IP addresses into this file. For many updates everything works fine but Occasionally,  I see the following error:
> Apr  6 05:00:09 Reporter::ERROR /feeds/Blacklist/CURRENT.24hrs_BRO/Input::READER_ASCII: could not read first line        (empty)
> After this failure/message,  any subsequent updates on the file are ignored by the input framework. 
> From visual inspection the file looks just fine and header/data (1 column of IP addresses) is there as expected but somehow input framework doesn't like it. It seems that every hour when update the file using a cron script, on a rare occasion the  file is empty for a minuscule duration after which this error starts. 
> for further REREADS data won't get updated into the tables anymore once the above Reporter::ERROR kicks in. 
> Please let me know if you need ways to reproduce this error condition or have more questions for me. 



--
This message was sent by Atlassian JIRA
(v6.3-OD-05-016#6325)


More information about the bro-dev mailing list