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

    Setup pfSync causes an instant crash pfsense 2.7

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    9 Posts 3 Posters 634 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.
    • C
      cwager990
      last edited by

      Has anyone had any issues getting ha setup, I have tried to follow the steps detailed in the documentation and the second it click save to apply pfsync pfsense crashes.

      This the latest version of pfsense running in a KVM based virtual machine.

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @cwager990
        last edited by

        @cwager990 2.7.2 is the latest.
        https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

        Define "crash"? What do the logs show at that time?

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        C 2 Replies Last reply Reply Quote 0
        • C
          cwager990 @SteveITS
          last edited by

          @SteveITS I'll have to clone it and do it again to get the log.

          By crash I mean exactly that a hard crash box crashed reboots and then shows a notice saying a crash occurred.

          1 Reply Last reply Reply Quote 0
          • C
            cwager990 @SteveITS
            last edited by

            @SteveITSG Here is a text file with the crash info in it any ideas would be great. crashinfo.txt

            K 1 Reply Last reply Reply Quote 0
            • K
              kprovost @cwager990
              last edited by

              @cwager990 Does that happen consistently?

              The backtrace shows we're panicing trying to export a state and we dereference a NULL pointer. Very early on in the export function in fact.
              That might happen if the state has been unlinked and its keys have been removed. There may be race conditions that allow that to happen, but that'd be very very rare occurrences, not consistent panics.

              So: does this happen every time you turn on pfsync, and is the backtrace and register dump always the same?

              C 1 Reply Last reply Reply Quote 0
              • C
                cwager990 @kprovost
                last edited by

                @kprovost Hi, yes this happens every single time without fail it blows up the same way every single time. Both nodes are KVM/QEMU Virtual machines hosts are identical in every respect I have even tried with both Virtual Machines on the same host. Same result every single time.

                K 1 Reply Last reply Reply Quote 0
                • K
                  kprovost @cwager990
                  last edited by

                  @cwager990 And presumably the backtrace is identical every time?

                  Can you post or otherwise share the state table?
                  The pfctl -ss -vvv output is what I'm after.

                  While you're gather information include /tmp/rules.debug too.

                  There has to be something very odd with at least one of your states, but I don't have any idea how that could be happening, especially so consistently.

                  C 2 Replies Last reply Reply Quote 0
                  • C
                    cwager990 @kprovost
                    last edited by

                    @kprovost Hi, I have attached both the requested files. rules.debug.txt states.txt

                    Thanks

                    1 Reply Last reply Reply Quote 0
                    • C
                      cwager990 @kprovost
                      last edited by

                      @kprovost I have now got this working, I have no idea what I did differently but on two newly built virtual machines I have it working.

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