[Bro] out of memory after a couple days?
gary at doit.wisc.edu
Wed Dec 4 21:55:08 PST 2013
It normally has a healthy diet of 7-8Gbps and 1Mpps of traffic to
consume, and other than some initial growing pains (not enough proxies)
it has mostly just worked, although sometimes when it has stopped
receiving traffic, such as during network maintenance / code upgrades to
the load-balancer it has complained and started killing processes.
On 12/4/2013 10:31 PM, Seth Hall wrote:
> On Dec 4, 2013, at 10:34 PM, Mike Patterson <mike.patterson at uwaterloo.ca> wrote:
>> I think you’re definitely running into a memory leak. I’ve had 2.2 processes try to grab up to 100GB of RAM. 8 workers, 96GB of RAM, but the box splits time with another 8 snort workers. My late 2.1 release (september 21 IIRC) was quite a bit more stable.
> I think there is some particular traffic that you guys are running into that's causing it. A few other people have encountered that too but we haven't been able to nail down what it is yet.
> Seth Hall
> International Computer Science Institute
> (Bro) because everyone has a network
Office of Campus Information Security
More information about the Bro