Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    New messages after update to 2.4.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    14 Posts 4 Posters 1.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      esquire1968
      last edited by

      Hi!

      After reconnection with the internet I get always the same error messages:

      pf_busy
      
      PF was wedged/busy and has been reset.	@ 2017-10-27 05:10:58
      
      Filter Reload
      
      There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2017-10-27 05:10:59
      

      Unfortunately I found no solution in the web. Please could you explain me the messages or give me a solution.

      Thanks!

      Thomas

      1 Reply Last reply Reply Quote 0
      • BBcan177B
        BBcan177 Moderator
        last edited by

        @esquire1968:

        pf_busy
        
        PF was wedged/busy and has been reset.	@ 2017-10-27 05:10:58
        
        Filter Reload
        
        There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2017-10-27 05:10:59
        

        PiBa has a PR to hopefully fix that issue…

        See here:
            https://github.com/pfsense/pfsense/pull/3857

        "Experience is something you don't get until just after you need it."

        Website: http://pfBlockerNG.com
        Twitter: @BBcan177  #pfBlockerNG
        Reddit: https://www.reddit.com/r/pfBlockerNG/new/

        1 Reply Last reply Reply Quote 0
        • E
          esquire1968
          last edited by

          Thanks for your answer! Unfortunately it doesn't work. When pfBlockerNG is deactivated, I get no error message after reboot.

          T.

          1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan
            last edited by

            Humm.

            Not using pfBlockerNG  - using 2.4.1-RELEASE (amd64) on a :

            Intel(R) Pentium(R) 4 CPU 3.20GHz
            Current: 2800 MHz, Max: 3200 MHz
            2 CPUs: 1 package(s) x 2 hardware threads 
            (from 2005 .....)
            

            Applied the patch https://github.com/pfsense/pfsense/pull/3857

            My pfSense still sings on boot :

            PF was wedged/busy and has been reset.....
            There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]....
            

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            1 Reply Last reply Reply Quote 0
            • P
              PiBa
              last edited by

              Can you try increasing the 'while ($pfctl_try < 10) {' to maybe 100 ? That would give it 20 seconds to settle its current activity..

              Do you use any other packages like maybe ntop? Or anything else 'special' configured like aliases with url lists?

              1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan
                last edited by

                @PiBa:

                Can you try increasing the 'while ($pfctl_try < 10) {' to maybe 100 ? That would give it 20 seconds to settle its current activity..

                Will try that tomorrow.
                @PiBa:

                Do you use any other packages like maybe ntop? Or anything else 'special' configured like aliases with url lists?

                Noop.
                Avahi - NUT - Cron (but nothing added to the cron list) - ACME.

                edit : Wait : I installed "munin-node" years ago. Runs every 5 minutes some perl and shell scripts (but nothing that touches pf I guess).
                I'll ditch it by doing a complete clean re-install (switch to ZFS while doing so). Will report back.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                1 Reply Last reply Reply Quote 0
                • E
                  esquire1968
                  last edited by

                  @PiBa:

                  Do you mean 'while ($pfctl_try < 10) {' set to 100 in the original filter.inc or in the modified one?

                  I've the following packages installed:

                  bandwidthd
                  Cron
                  freeradius3
                  nut
                  openvpn-client-export
                  pfBlockerNG
                  RRD_Summary	
                  Service_Watchdog
                  snort
                  

                  Thomas

                  1 Reply Last reply Reply Quote 0
                  • P
                    PiBa
                    last edited by

                    @esquire1968, In the 'patched' one, the original doesnt have the 'try loop'.

                    1 Reply Last reply Reply Quote 0
                    • E
                      esquire1968
                      last edited by

                      No changes! The same errors after setting '> 100'.  :(

                      1 Reply Last reply Reply Quote 0
                      • P
                        PiBa
                        last edited by

                        '< 100' right? you shouldn't change the <> sign. or did you mean you tried bigger numbers as well? just checking.. if so then we should try and figure out what is keeping pf busy / wedging it.. not really sure what path to investigate yet though..

                        Can you 'trigger' the problem while pfSense is running? Can you run "lsof /dev/pf" while its in that process? what processes have the pf device open?

                        1 Reply Last reply Reply Quote 0
                        • GertjanG
                          Gertjan
                          last edited by

                          @PiBa :
                          The filter reload (mine - as the others here) return :
                          " ….  pfctl: DIOCXCOMMIT ..." as a part of the notification.

                          Your patch is trying 10 times IF it detected a return 'error' lines that contains

                          strstr($_grbg, "DIOCADDALTQ: Device busy")
                          

                          because it returns "…DIOCXCOMMIT " -> also known as "something else"  ;)
                          So, the "try 10 times" is never executed, the flow will break out right away.

                          When I changed

                          if (strstr($_grbg, "DIOCADDALTQ: Device busy")) {
                          

                          for

                          if (strstr($_grbg, "DIOCXCOMMIT : Device busy")) {
                          

                          is were no more notifications for me.

                          @IpBa : Thanks !!

                          Edit : when I added <developerspew>to the config.xml - below <pfsense><system>- , I actually saw that a second try was needed to put the rules in place :

                          pf was busy but succeeded after 2 tries @ 2017-10-31 11:51:44

                          This means (to me) that some race conditions exists ones during boot - and that the problem isn't actually a real one</system></pfsense></developerspew>

                          No "help me" PM's please. Use the forum, the community will thank you.
                          Edit : and where are the logs ??

                          1 Reply Last reply Reply Quote 0
                          • P
                            PiBa
                            last edited by

                            Thanks Gertjan,
                            In my reproduction i'm sure it said 'DIOCADDALTQ' when i managed to reproduce 'something similar' and i guess i didn't look close enough at the actual message provided, i have changed my pull-request to include 'DIOCXCOMMIT'. Should be working for both cases now.

                            p.s. its without the space character before the colon right.?.

                            1 Reply Last reply Reply Quote 0
                            • GertjanG
                              Gertjan
                              last edited by

                              @PiBa:

                              p.s. its without the space character before the colon right.?.

                              "strstr" to "DIOCXCOMMIT" will do ^^

                              No "help me" PM's please. Use the forum, the community will thank you.
                              Edit : and where are the logs ??

                              1 Reply Last reply Reply Quote 0
                              • E
                                esquire1968
                                last edited by

                                @Gertjan

                                Fantastic! Changing DIOCADDALTQ to DIOCXCOMMIT works!

                                Cheers
                                Thomas

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.