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

    PfBlockerNG upgrade 2.0.17 -> 2.1.1_2

    Scheduled Pinned Locked Moved pfBlockerNG
    5 Posts 3 Posters 2.1k 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.
    • T
      tdi
      last edited by

      After successful upgrade pfBlockerNG menu item is missing from the Firewall menu (pfSense 2.3.2).
      I am able to access pfBlockerNG through main screen pfBlockerNG widget though.

      Second issue is that updating pfBlockerNG aborts on "Sync terminated during boot process" and there is no Sync option enabled.

      Any help is appreciated.
      Thanks

      1 Reply Last reply Reply Quote 0
      • RonpfSR
        RonpfS
        last edited by

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

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

        1 Reply Last reply Reply Quote 0
        • T
          tdi
          last edited by

          Thanks Ronpfs,
          upping memory up helped with the menu issue,

          However update/cron/reload always end up with "Sync terminated during boot process." - and that is all I get in pfBlocker log files.
          I have tried disabling dnsbl and most of the lists with no success.

          Thank You

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

            @tdi:

            However update/cron/reload always end up with "Sync terminated during boot process." - and that is all I get in pfBlocker log files.

            The pkg checks to see if the platform is booting, it does this by calling a pfSense function called platform_booting()

            So i assume that after reboot, there still remains a booting file in your firewall.
            If this file exists below, delete it, and it should resolve your issue:

            /var/run/booting
            

            I have seen this happen to one other user awhile back, so there is some underlying issue with the pfSense boot process that doesn't delete the booting file in all cases… Might just be a corner-case.

            "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
            • T
              tdi
              last edited by

              Spot on!

              After removing /var/run/booting everything works as expected.

              Thank you!

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