Network Administrator

Some additional data: After 12 hours I'm up to about 3GiB of memory in use. The machine that most recently locked up showed OOM messages. The processes that were killed...

Thank you so much for looking into this! I'm just trying to understand your bug descriptions and have a couple questions: - Is `joold advertise` not working in the current...

> Yes; `ss-flush-asap true` is mandatory in Active/Active. Notice it's `true` by default, so you probably already have it. We actually had it off (we're doing active/passive but with two...

Sorry for the delay on this; had some other emergencies that kept getting in the way. I have checked out the issue410 branch from git and built jool from source....

And just to provide an update, memory usage is holding steady on the machines, with no mention of joold_nodes. We're still in light testing (students have not returned to campus),...

Update from today. Looks like we might still be leaking memory, but not in the same place (and not nearly as quickly, since I just noticed this after 1+ week...

I had a minute. ;-) Shutting down the jool instance and unloading the kernel modules did not release the memory. I'm rebooting this box now to recover the RAM and...

We're active/active so it's happening on both hosts. I'm trying to turn down journaling to make sure it's not just logging that's chewing up memory. I recompiled with the requested...

Sorry, I didn't realize I had to unload the module. When I did, there wasn't anything in dmesg about memory, just the unloading messages: ``` [Wed Aug 30 07:50:42 2023]...

OK, recompiled off that branch with the new commits. Been running for about 16 hours. I took a stats dump and then unloaded the module. Still not seeing any leak...