[Bro] stdout.log does not work?

Hongda Li hongdal at g.clemson.edu
Tue Jan 12 18:58:09 PST 2016


Hello, Community.

I've a problem with stdout.log.

I add some "print" statements in bro scripts (e.g.,
detect-bruteforcing.bro).
When I start Bro from the command line:
    *bro -i eth2 local *
it prints outputs of the print statements on to the stdout.

However, I start Bro from the broctl:
    *[BroControl] > start*
*    [BroControl] > exit*
then I go to "logs/current/" and try to see the outputs of the print
statements:
    *cat stdout.log*
the only results that I can see are:
    *max memory size         (kbytes, -m) unlimited*
*    data seg size           (kbytes, -d) unlimited*
*    virtual memory          (kbytes, -v) unlimited*
*    core file size          (blocks, -c) unlimited*

I expected that I can read the outputs of the print statements in the
*stdout.log*.

The content of /logs/stderr.log looks like (only one line):
    *listening on eth2, capture length 8192 bytes*
This error message also appears as I start Bro by command line.
I don't think this makes any difference.

I have no idea what is going wrong.

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/bro/attachments/20160112/9768e56e/attachment-0001.html 


More information about the Bro mailing list