PF was wedged/busy and has been reset - never fixed?



  • pf_busy

    PF was wedged/busy and has been reset. @ 2016-09-20 04:21:32
        PF was wedged/busy and has been reset. @ 2016-09-20 10:50:54
        PF was wedged/busy and has been reset. @ 2016-09-20 13:37:07
        PF was wedged/busy and has been reset. @ 2016-09-20 21:34:10
        PF was wedged/busy and has been reset. @ 2016-09-21 11:24:18
        PF was wedged/busy and has been reset. @ 2016-09-21 14:36:29
        PF was wedged/busy and has been reset. @ 2016-09-22 12:56:18
        PF was wedged/busy and has been reset. @ 2016-09-23 12:45:40
        PF was wedged/busy and has been reset. @ 2016-09-26 10:02:00
        PF was wedged/busy and has been reset. @ 2016-09-26 10:06:49
        PF was wedged/busy and has been reset. @ 2016-09-26 11:42:20
        PF was wedged/busy and has been reset. @ 2016-09-26 11:42:36

    Version 	2.3.1-RELEASE-p5 (amd64)
    built on Thu Jun 16 12:53:15 CDT 2016 FreeBSD 10.3-RELEASE-p3
    
    CPU Type 	Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz, 4 CPUs: 4 package(s) x 1 core(s)
    Hardware crypto 	AES-CBC,AES-XTS,AES-GCM,AES-ICM
    Uptime 	65 Days 20 Hours 55 Minutes 26 Seconds
    
    State table size 	31% (77019/250000) Show states
    MBUF Usage 	53% (14180/26584)
    Load average 	0.98, 0.98, 0.92
    CPU usage 	10%
    Memory usage 	26% of 2013 MiB
    SWAP usage 	0% of 4096 MiB
    
    

  • Rebel Alliance Global Moderator

    what version are you using?  When are you seeing that the issue where it was being seen on boot has been fixed.  But that seem more to error on reloading rules that have errors?

    What version of pfsense, what packages?

    this seems to point to fix being applied in 2.3.1 for boot issue.
    https://forum.pfsense.org/index.php?topic=111236.0



  • Packages: arping, FTP_Client_Proxy, Open-VM-Tools, openvpn-client-export and sudo

    As you can see the errors are from random times, and we have a huge uptime.. nothing to do with booting…
    It seems to happen when the firewall is most used.. (it's the gateway of a big network..)



  • There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-20 04:21:33
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-20 10:50:55
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-20 13:37:08
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-20 21:34:11
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-21 11:24:19
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-21 14:36:30
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-22 12:56:19
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-23 12:45:41
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-26 10:02:01
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-26 10:06:50
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-26 11:42:21
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-09-26 11:42:37

    It seems to happens when this "automatic" reload happens.. I wasn't changing any rules at these times



  • @johnpoz:

    this seems to point to fix being applied in 2.3.1 for boot issue.
    https://forum.pfsense.org/index.php?topic=111236.0

    2.3.2.-p1 AMD64.

    Having the same on boot:

    PF was wedged/busy and has been reset

    Together with:

    There were error(s) loading the rules: pfctl: DIOCADDALTQ: Device busy



  • And another when I enabled a new VLAN interface:

    PF was wedged/busy and has been reset. @ 2016-11-08 18:27:07

    At least: I pressed 'save' after enabling the new VLAN, the GUI looked like it hung, and this new alert showed.



  • my pfsense is same problem:

    pf_busy
    
    PF was wedged/busy and has been reset.	@ 2016-11-08 20:15:31
    PF was wedged/busy and has been reset.	@ 2016-11-09 15:28:03
    Filter Reload
    
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-11-08 20:15:32
    There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [0]: @ 2016-11-09 15:28:04
    
    Name	v-fw-pfsense-d01.localdomain
    System	pfSense	
    Version	2.3.2-RELEASE-p1 (amd64) 
    built on Tue Sep 27 12:13:07 CDT 2016 
    FreeBSD 10.3-RELEASE-p9
    Platform	pfSense
    CPU Type	Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
    16 CPUs: 2 package(s) x 8 core(s)
    Uptime	3 Days 03 Hours 30 Minutes 47 Seconds
    Current date/time	
    Thu Nov 10 12:02:17 CST 2016
    

    How to trace it? How to fix it?



  • Ive been getting this randomly over the last month and thought it was caused by PFBlockerNG

    https://forum.pfsense.org/index.php?topic=102470.msg667358#msg667358

    Rob