PF wedged/busy on reboot or fw reload since 2.3.0 continues on 2.3.1

[cciechad]

I see this alert every time the FW reboots or the PF is reloaded. I'm not sure on how to troubleshoot further. I was wondering if anyone could point me in the right direction.

pf_busy

PF was wedged/busy and has been reset. @ 2016-05-19 08:09:26

Filter Reload

There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2016-05-19 08:09:27

Thanks,

Chad

[Gertjan]

and 2.3.4 - p1 == latest version.

pf_busy

    PF was wedged/busy and has been reset. @ 2017-09-27 17:07:01

Filter Reload

    There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2017-09-27 17:07:02

Before I used a bridge device (using pppoe).
Since a couple of months I'm using a new device - a VDSL router supplied by my ISP, so now my WAN is setup as a dhcp-client - obtaining 192.168.10.11 every time.

Still, on every reboot (a couple of times a year, mostly because I did something stupid) I have these two notices : "PF was wedged/busy"
Is this some leftover in my config.xml ?
Is it "normal" ?

edit : I inspected "/tmp/rules.debug" but found nothing suspect … / don't know what to look for.

If nothing explains it, I'll accept : https://forum.pfsense.org/index.php?topic=117145.msg651479#msg651479

edit : packages : VPN-Client (one VPN-server activated) - Avahi - NUT

[nycfly]

I started getting this pair of messages on reboot after I enabled Suricata inline mode. I've just been ignoring them.

[fireix]

I have started seeing this for first time in 2.4.0-RELEASE (amd64) on two pfSense-units.

One is completely new from Netgear and one is on Supermicro-hardware. Both running 2.4.0.

[Guest]

Ignore it, it's log jabber and is nothing to worry about. I usually see it when I force update  pfblocker or I'm making rule change and applying them and not waiting for them to complete before applying something else.