SOLVED!!!!! pfr_update_stats: assertion failed spamming my opnsense

[Tismofied]

This is my System info:

Versions   OPNsense 23.7.1_3-amd64
FreeBSD 13.2-RELEASE-p2
OpenSSL 1.1.1v 1 Aug 2023
CPU type   Intel(R) Celeron(R) J4125 CPU @ 2.00GHz (4 cores, 4 threads)
8 Gig ddr4 ram

plugins :
os-adguardhome-maxit (installed)   1.10   
os-mdns-repeater (installed)   1.1      
os-nextcloud-backup (installed)   1.0_1   
os-sensei (installed)   1.14.3      
os-sensei-agent (installed)   1.14.3   
os-sensei-updater (installed)   1.14      
os-sunnyvalley (installed)   1.2_3   
os-theme-rebellion (installed)   1.8.8      
os-wireguard (installed)   1.13_7   

only adguardhome, mdns-repeater and theme-rebillion are running at the moment.

I keep getting pages of this error and was wondering what could be the cause?

[Tismofied]

Should I just ignore it since it is just a notice and not marked as an error?!

[franco]

Well, it's a kernel message which doesn't offer log levels.

The code in question is this:

https://github.com/opnsense/src/blob/4b4f06e3731c58e1e03790277d9e37f11ee1caa7/sys/netpfil/pf/pf_table.c#L2139-L2140

And it looks rather inconsequential to me. It was modified here:

https://github.com/opnsense/src/commit/032dff662c7559

Indicating that you seem to use pf debug log level?


Cheers,
Franco

[franco]

PS: Oh no we seem to have introduced this default logging level from "none" to "urgent".

[franco]

You can set the level back to none via Firewall: Settings: Advanced: Miscellaneous "Debug": "Don't generate debug messages".

And I'll see if we switch the default again.


Cheers,
Franco

[Tismofied]

That's it. I was about to ask where that setting was. Thank you sir!

I'll mark this solved.

[franco]

The fun part seems to be "urgent" is the default in pf(4) as well so https://github.com/opnsense/src/commit/032dff662c7559 wouldn't mute in the default case. This is rather odd.


Cheers,
Franco