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

    2.1.2 Update: editing broken?

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    12 Posts 6 Posters 3.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.
    • D
      doktornotor Banned
      last edited by

      Sounds like autoconfigbackup package.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Update the autoconfigbackup package to 1.22.

        If you can't, first do this and then update the package:

        rm /etc/inc/crypt_acb.inc /usr/local/pkg/autoconfigbackup*
        

        Might reboot for good measure.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • JeGrJ
          JeGr LAYER 8 Moderator
          last edited by

          Thanks everybody. To those, that may encounter the same problem:

          After upgrading to 2.1.2 (coming from 2.1.1) the packages weren't updated or reinstalled (as I assumed wrong) and so autoconfbackup 1.21 still was running and effectively breaking the whole freakin' UI. Every save, delete or other config-safe-related button was broken.

          So after removing it (package removal didn't work as the textarea containing the status stayed empty and nothing was processing) with brute force (like jimp suggested by removing the pkg dir) and reinstalling it, everything is back to normal again.

          Note to self: don't upgrade the cluster remotely to safe working-time. Gets your pulse-rate up ;)

          Thanks to all and greets to the team for quick and great work so far!
          Jens

          Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

          If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

          1 Reply Last reply Reply Quote 0
          • A
            adam65535
            last edited by

            That does sound a bit worrysome that the main pfsense image depends on a package being updated first (during an upgrade of course).  If someone does not update autoconfigbackup again when/if the next release is out could they have the same issue?

            EDIT: Oh… never mind... I think the version check was for the autoconfigbackup package version which just forgot to get bumped in that one spot.  I don't think the main pfsense package version check would be an issue for the future.  I am just guessing though as I don't really understand the code :).

            1 Reply Last reply Reply Quote 0
            • P
              phil.davis
              last edited by

              Note the "rm" should be:

              rm /etc/inc/crypt_acb.php
              rm /usr/local/pkg/autoconfigbackup*
              

              (JimPs post had .inc and should have been .php)
              The post in the other thread about this has the correct crypt_acb.php file name.
              I'm sure JimP will quickly modify his post, then I can delete this.

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

              1 Reply Last reply Reply Quote 0
              • P
                phil.davis
                last edited by

                @adam65535:

                That does sound a bit worrysome that the main pfsense image depends on a package being updated first (during an upgrade of course).  If someone does not update autoconfigbackup again when/if the next release is out could they have the same issue?

                It was just a dumb bug in AutoConfigBackup that tested for "1.2" anywhere in the version string, which now matches "2.1.2". It only effected people who use AutoConfigBackup (hey, that's the paying customers) and JimP fixed it in 5 minutes after it was reported.
                From now, people who upgrade will get the correct AutoConfigBackup files installed and will never see this issue.

                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                1 Reply Last reply Reply Quote 0
                • A
                  adam65535
                  last edited by

                  Thanks for the info.  After looking at the commit in github I figured that as much and it looks like I edited my post the same time you posted your info.  Thanks for the clarification.

                  1 Reply Last reply Reply Quote 0
                  • A
                    adam65535
                    last edited by

                    @jimp:

                    Update the autoconfigbackup package to 1.22.

                    If you can't, first do this and then update the package:

                    rm /etc/inc/crypt_acb.inc and /usr/local/pkg/autoconfigbackup*
                    

                    Might reboot for good measure.

                    @phil.davis:

                    Note the "rm" should be:

                    rm /etc/inc/crypt_acb.php
                    rm /usr/local/pkg/autoconfigbackup*
                    

                    (JimPs post had .inc and should have been .php)
                    The post in the other thread about this has the correct crypt_acb.php file name.
                    I'm sure JimP will quickly modify his post, then I can delete this.

                    Doh!  I just deleted my custom 'and' file that was in my directory! ;)

                    1 Reply Last reply Reply Quote 0
                    • P
                      phil.davis
                      last edited by

                      And I thought this was something from the Australian Cricket Board.

                      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                      1 Reply Last reply Reply Quote 0
                      • F
                        Fmstrat
                        last edited by

                        I have a similar issue where my packages weren't installed. And of course I can't remember which packages I had. Is there a way to restart the upgrade process and get packages in?

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