Another error I can't parse….



  • I had these a few times over the last days in my notifications:

    07-20-13 19:56:41	[ There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: ]
    

    What's the meaning of that? Random glitch? Bug? Something wrong in my setup?



  • @rcfa:

    I had these a few times over the last days in my notifications:

    07-20-13 19:56:41	[ There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: ]
    

    What's the meaning of that? Random glitch? Bug? Something wrong in my setup?

    You don't mention versions or what ever so could I suggest this:

    http://lmgtfy.com/?q=DIOCXCOMMIT%3A+Device+busy - there are lots of hits, many from these forums.  Try reading those first and then posting back with some more information:

    Packages installed and snapshot version would be a good start.

    Cheers
    Jon



  • You have to give more information rather than just asking what it is.
    That means that the firewall device is busy doing some other transaction and cannot process your existing one.
    That means that your rules were not loaded at this time.

    This would happen for example when another daemon is doing some operation already adding/removing a rule, or some package is trying to update a table or so on….

    Can you check on your system log what was going on at the time?



  • @ermal:

    You have to give more information rather than just asking what it is.
    That means that the firewall device is busy doing some other transaction and cannot process your existing one.
    That means that your rules were not loaded at this time.

    This would happen for example when another daemon is doing some operation already adding/removing a rule, or some package is trying to update a table or so on….

    Can you check on your system log what was going on at the time?

    I'll see what I can do, when it happens again. The reason why I didn't provide more, because this happened to be in the notification area (the thing at the top of each page in the web adminstration interface), and in that place, there's not more information than that precise message I copied and pasted.
    Chances are, that by the time I notice that notification, whatever may have been in the syslog, got already pushed out of the view.