There were error(s) - pfctl: DIOCXCOMMIT: Device busy



  • Good Morning,

    I run in a serious problem with the PFSense, I get about once in a week a crash or hang in my VM PFsense. The time is always the reconnect time after 24 Hours. Now I see the first time a hint in the webinterface without a crash/hang:

    05-31-14 05:30:32
    [ There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: ]

    So here are the day before and the day after it from the syslog of the gateway:

    Jun 1 05:30:41 apinger: alarm canceled (config reload): Internet(82.135.118.20) *** Internetdown ***
    Jun 1 05:30:41 apinger: SIGHUP received, reloading configuration.
    Jun 1 05:30:18 apinger: ALARM: Internet(82.135.118.20) *** Internetdown ***
    May 31 05:30:43 apinger: alarm canceled (config reload): Internet(82.135.118.20) *** Internetdown ***
    May 31 05:30:43 apinger: SIGHUP received, reloading configuration.
    May 31 05:30:18 apinger: ALARM: Internet(82.135.118.20) *** Internetdown ***
    May 30 07:44:24 apinger: Starting Alarm Pinger, apinger(26685)
    May 29 16:38:02 apinger: Starting Alarm Pinger, apinger(25983)
    May 29 16:36:20 apinger: ALARM: Internet(82.135.118.20) *** Internetdown ***
    May 29 08:05:33 apinger: Starting Alarm Pinger, apinger(26907)
    May 29 05:30:31 apinger: alarm canceled (config reload): Internet(82.135.118.20) *** Internetdown ***
    May 29 05:30:31 apinger: SIGHUP received, reloading configuration.
    May 29 05:30:16 apinger: ALARM: Internet(82.135.118.20) *** Internetdown ***

    Logs on the resolver at reconnect time (only the actual day :()

    Jun 2 05:30:33 dnsmasq[52582]: read /etc/hosts - 28 addresses
    Jun 2 05:30:33 dnsmasq[52582]: using nameserver 192.168.1.6#53 for domain eso.local
    Jun 2 05:30:33 dnsmasq[52582]: ignoring nameserver 127.0.0.1 - local interface
    Jun 2 05:30:33 dnsmasq[52582]: using nameserver 8.8.4.4#53
    Jun 2 05:30:33 dnsmasq[52582]: using nameserver 8.8.8.8#53
    Jun 2 05:30:33 dnsmasq[52582]: reading /etc/resolv.conf
    Jun 2 05:30:28 dnsmasq[52582]: using nameserver 192.168.1.6#53 for domain eso.local
    Jun 2 05:30:28 dnsmasq[52582]: ignoring nameserver 127.0.0.1 - local interface
    Jun 2 05:30:28 dnsmasq[52582]: using nameserver 8.8.4.4#53
    Jun 2 05:30:28 dnsmasq[52582]: using nameserver 8.8.8.8#53
    Jun 2 05:30:28 dnsmasq[52582]: reading /etc/resolv.conf
    Jun 2 05:30:13 dnsmasq[52582]: using nameserver 192.168.1.6#53 for domain eso.local
    Jun 2 05:30:13 dnsmasq[52582]: ignoring nameserver 127.0.0.1 - local interface
    Jun 2 05:30:13 dnsmasq[52582]: using nameserver 8.8.4.4#53
    Jun 2 05:30:13 dnsmasq[52582]: using nameserver 8.8.8.8#53
    Jun 2 05:30:13 dnsmasq[52582]: reading /etc/resolv.conf
    Jun 2 05:19:23 dnsmasq[52582]: read /etc/hosts - 28 addresses

    And PPP syslog:

    Jun 2 05:30:30 ppp: [wan] 188.174.XXX.XXX -> 82.135.XXX.XXX
    Jun 2 05:30:30 ppp: [wan] IPCP: LayerUp
    Jun 2 05:30:30 ppp: [wan] IPCP: state change Ack-Sent –> Opened
    Jun 2 05:30:30 ppp: [wan] IPADDR 188.174.XXX.XXX
    Jun 2 05:30:30 ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
    Jun 2 05:30:30 ppp: [wan] IPADDR 188.174.XXX.XXX
    Jun 2 05:30:30 ppp: [wan] IPCP: SendConfigReq #3
    Jun 2 05:30:30 ppp: [wan] 188.174.XXX.XXX is OK
    Jun 2 05:30:30 ppp: [wan] IPADDR 188.174.XXX.XXX
    Jun 2 05:30:30 ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
    Jun 2 05:30:30 ppp: [wan] IFACE: Rename interface ng0 to pppoe0
    Jun 2 05:30:30 ppp: [wan] IFACE: Up event
    Jun 2 05:30:30 ppp: [wan] 020c:29ff:XXX:XXX -> 3e08:f6ff:XXX:XXX
    Jun 2 05:30:30 ppp: [wan] IPV6CP: LayerUp
    Jun 2 05:30:30 ppp: [wan] IPV6CP: state change Ack-Sent –> Opened
    Jun 2 05:30:30 ppp: [wan] IPV6CP: rec'd Configure Ack #1 (Ack-Sent)
    Jun 2 05:30:30 ppp: [wan] IPV6CP: state change Req-Sent –> Ack-Sent
    Jun 2 05:30:30 ppp: [wan] IPV6CP: SendConfigAck #1
    Jun 2 05:30:30 ppp: [wan] IPV6CP: rec'd Configure Request #1 (Req-Sent)
    Jun 2 05:30:30 ppp: [wan] IPADDR 0.0.0.0
    Jun 2 05:30:30 ppp: [wan] IPCP: SendConfigReq #2
    Jun 2 05:30:30 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jun 2 05:30:30 ppp: [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
    Jun 2 05:30:30 ppp: [wan] IPCP: state change Req-Sent –> Ack-Sent
    Jun 2 05:30:30 ppp: [wan] IPADDR 82.135.XXX.XXX
    Jun 2 05:30:30 ppp: [wan] IPCP: SendConfigAck #1
    Jun 2 05:30:30 ppp: [wan] 82.135.XXX.XXX is OK
    Jun 2 05:30:30 ppp: [wan] IPADDR 82.135.XXX.XXX
    Jun 2 05:30:30 ppp: [wan] IPCP: rec'd Configure Request #1 (Req-Sent)
    Jun 2 05:30:30 ppp: [wan] IPV6CP: SendConfigReq #1
    Jun 2 05:30:30 ppp: [wan] IPV6CP: state change Starting –> Req-Sent
    Jun 2 05:30:30 ppp: [wan] IPV6CP: Up event
    Jun 2 05:30:30 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jun 2 05:30:30 ppp: [wan] IPADDR 0.0.0.0
    Jun 2 05:30:30 ppp: [wan] IPCP: SendConfigReq #1
    Jun 2 05:30:30 ppp: [wan] IPCP: state change Starting –> Req-Sent
    Jun 2 05:30:30 ppp: [wan] IPCP: Up event
    Jun 2 05:30:30 ppp: [wan] IPV6CP: LayerStart
    Jun 2 05:30:30 ppp: [wan] IPV6CP: state change Initial –> Starting
    Jun 2 05:30:30 ppp: [wan] IPV6CP: Open event
    Jun 2 05:30:30 ppp: [wan] IPCP: LayerStart
    Jun 2 05:30:30 ppp: [wan] IPCP: state change Initial –> Starting
    Jun 2 05:30:30 ppp: [wan] IPCP: Open event
    Jun 2 05:30:30 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
    Jun 2 05:30:30 ppp: [wan_link0] Link: Join bundle "wan"
    Jun 2 05:30:30 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
    Jun 2 05:30:30 ppp: [wan_link0] LCP: authorization successful
    Jun 2 05:30:30 ppp: [wan_link0] CHAP: rec'd SUCCESS #1 len: 4
    Jun 2 05:30:30 ppp: [wan_link0] CHAP: sending RESPONSE #1 len: 51
    Jun 2 05:30:30 ppp: [wan_link0] CHAP: Using authname "XXXXXXXXXXXXXXX"

    So thats what I can give you now. I'm not sure how to find out where the real problem is.
    I found a simular problem in another thread https://forum.pfsense.org/index.php?topic=64665
    where it is thought to be a operation/rule problem.

    Could it be something like the Apinger in a loop or something else? Attached are the Services and Packages.

    Please help me out to find a solution for this.
    ![Bildschirmfoto 2014-06-02 um 09.24.52.png](/public/imported_attachments/1/Bildschirmfoto 2014-06-02 um 09.24.52.png)
    ![Bildschirmfoto 2014-06-02 um 09.24.52.png_thumb](/public/imported_attachments/1/Bildschirmfoto 2014-06-02 um 09.24.52.png_thumb)
    ![Bildschirmfoto 2014-06-02 um 09.25.04.png](/public/imported_attachments/1/Bildschirmfoto 2014-06-02 um 09.25.04.png)
    ![Bildschirmfoto 2014-06-02 um 09.25.04.png_thumb](/public/imported_attachments/1/Bildschirmfoto 2014-06-02 um 09.25.04.png_thumb)



  • This is another bug on 2.1.3, as I never got this before, and I always use a dedicated machine for pFsense, no VM at all.

    06-17-14 05:51:26	[ There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: ]
    


  • Hi Gradius,

    thank you for posting your information. Couse I really thought that might be something at my vm. I just deinstalled everything I'm not 100% sure that can couse such trouble. But I still get this error.

    Hope that the PFSense Team recognize this and fix it soon.



  • The only new thing I run now (compared to old versions) is Unbound.

    My complete package list:

    • pfBlocker
    • snort
    • squid
    • Unbound

Log in to reply