On Thu, Sep 6, 2018 at 3:40 PM Azoff, Justin S wrote:
>8842
> broker::topic+broker::internal_comma...@u32.bro/known/certs/<$>/data/clone
Thanks, there was an unintended forwarding loop in data store
communication. It's fixed in master now, but I've also just reverted
to generally
> On Sep 6, 2018, at 4:19 PM, Jon Siwek wrote:
>
> On Thu, Sep 6, 2018 at 3:14 PM Azoff, Justin S wrote:
>
>
>> I tested an almost stock local.bro (a few additional things disabled) and
>> saw the same thing.
>>
>> fa7fa5aa is fine, but with 452eb0cb everything is working really hard to do
On Thu, Sep 6, 2018 at 3:14 PM Azoff, Justin S wrote:
> I tested an almost stock local.bro (a few additional things disabled) and saw
> the same thing.
>
> fa7fa5aa is fine, but with 452eb0cb everything is working really hard to do
> something.
Thanks for that, I'll start looking into it,
On Thu, Sep 6, 2018 at 2:47 PM Azoff, Justin S wrote:
> I just got 2 clusters upgraded from
>
> fa7fa5aa to
> 452eb0cb
>
> And now everything is broken..
>
> cpu and memory are through the roof across the board, as well as network
> traffic, but it's not logging much.
>
> I may have created a
> On Sep 6, 2018, at 3:41 PM, Azoff, Justin S wrote:
>
> I just got 2 clusters upgraded from
>
> fa7fa5aa to
> 452eb0cb
>
>
> I may have created a message loop replacing the relay_rr stuff, but it's kind
> of hard to tell.
>
> I'll do some more testing but so far this is the first issue
> On Sep 5, 2018, at 6:35 PM, Jon Siwek wrote:
>
> There's no significant code changes/features planned to get added to
> the master branch from now until the 2.6-beta gets released (maybe in
> about a week). Until that happens, please help test the latest master
> branch and provide any
On Wed, Sep 5, 2018 at 5:43 PM Michael Dopheide wrote:
>
> To be clear, Cluster::relay_rr() is gone forever? I’ll need to rewrite some
> policies, but also update the blog to be correct.
Yes.
- Jon
___
bro-dev mailing list
bro-dev@bro.org
On Wed, Sep 5, 2018 at 6:47 PM Vern Paxson wrote:
>
> > I think the right solution for this is to introduce a new BroType called
> > a NamedType. A NamedType has an identifier, an underlying BroType, and a
> > set of attributes. When a NamedType is constructed ...
>
> Huh, turns out there's
