Unclear to me why these are failing?

Robin

On Wed, Jul 15, 2015 at 03:55 -0500, [email protected] wrote:

> scripts.base.frameworks.logging.sqlite.wikipedia ... failed
>   % 'bro -r $TRACES/wikipedia.trace Log::default_writer=Log::WRITER_SQLITE' 
> failed unexpectedly (exit code -10)
>   % cat .stderr
>   1300475173.475401 <params>, line 1: packet_filter/Log::WRITER_SQLITE: 
> tablename configuration option not found. Defaulting to path packet_filter
>   1300475173.475401 <params>, line 1: weird/Log::WRITER_SQLITE: tablename 
> configuration option not found. Defaulting to path weird
>   1300475173.475401 <params>, line 1: http/Log::WRITER_SQLITE: tablename 
> configuration option not found. Defaulting to path http
>   1300475173.475401 <params>, line 1: dns/Log::WRITER_SQLITE: tablename 
> configuration option not found. Defaulting to path dns
>   1300475173.475401 <params>, line 1: conn/Log::WRITER_SQLITE: tablename 
> configuration option not found. Defaulting to path conn

(The messages about Log::WRITER_SQLITE are ok, I'm getting these here
locally as well even with the test passing.)

> scripts.policy.frameworks.intel.seen.certs ... failed
>   % 'cat intel.log > intel-all.log' failed unexpectedly (exit code 1)
>   % cat .stderr
>   1416942647.041795 warning in 
> /home/jenkins/workspace/CompileDefault/bro/scripts/base/misc/find-checksum-offloading.bro,
>  line 54: Your trace file likely has invalid IP checksums, most likely from 
> NIC checksum offloading.  By default, packets with invalid checksums are 
> discarded by Bro unless using the -C command-line option or toggling the 
> 'ignore_checksums' variable.  Alternatively, disable checksum offloading by 
> the network adapter to ensure Bro analyzes the actual checksums that are 
> transmitted.
>   cat: intel.log: No such file or directory



-- 
Robin Sommer * ICSI/LBNL * [email protected] * www.icir.org/robin
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Reply via email to