We lost bsnmpd on two firewalls 5 minutes apart, starting to narrow this down.
This doesn't look like the same issue as before, which was a FD leak. This looks like a straight up memory leak. Both bsnmpd's crashed in the middle of a tenable scan. Looking at another pair of our firewalls bsnmpd is taking up a boatload of memory:
10545 root 1 20 0 5446M 3015M select 4 14:12 0.03% bsnmpd
and
34784 root 1 20 0 5382M 2626M select 6 16:50 0.00% bsnmpd
So 3GB and 2.6GB ram resident. These two firewalls crashed maybe 15 days ago (when I last posted). We're also seeing the firewalls run out of swap space before the kill event, although a day or few before:
2>1 2025-04-18T14:01:06.988988-04:00 fw kernel - - - swap_pager: out of swap space
<2>1 2025-04-18T14:01:06.989098-04:00 - - - swp_pager_getswapspace(2): failed
<2>1 2025-04-19T04:00:28.371252-04:00 kernel - - - swp_pager_getswapspace(30): failed
Before the final kill
<3>1 2025-04-20T04:55:09.682953-04:00 kernel - - - pid 65139 (bsnmpd), jid 0, uid 0, was killed: failed to reclaim memory
While not fully conclusive, my guess is bsnmpd leaks memory during a tenable scan. I suppose we could prove this by kicking off a scan and looking at memory before/after. However I'm going to capture the status.php and open a support case.