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

    Unable to upgrade from 22.05.b.20220523.0600

    Scheduled Pinned Locked Moved
    Plus 22.05 Development Snapshots (Retired)
    2
    8
    653
    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.
    • S
      swampkracker
      last edited by swampkracker

      I have been staying current with development snapshots until now. Upgrading from 22.05.b.20220523.0600 from the WebUI proceeds as though all is well. After the reboot, no upgrade occurred.

      Running from the console, I see the following:

      Migrating /cf to ZFS dataset /dev//cf.../dev//cf: No such file or directory
      done.
      Migrating /var/db/pkg to ZFS dataset /dev//var_db_pkg.../dev//var_db_pkg: No such file or directory
      done.
      Updating repositories metadata...
      Updating pfSense-core repository catalogue...
      pkg-static: https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/meta.txz: No address record
      repository pfSense-core has no meta file, using default settings
      pkg-static: https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/packagesite.pkg: No address record
      pkg-static: https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-core/packagesite.txz: No address record
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg-static: https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/meta.txz: No address record
      repository pfSense has no meta file, using default settings
      pkg-static: https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/packagesite.pkg: No address record
      pkg-static: https://firmware.netgate.com/beta/packages/pfSense_plus-master_amd64-pfSense_plus_devel/packagesite.txz: No address record
      Unable to update repository pfSense
      Error updating repositories!
      ERROR: Unable to compare version of pfSense-repo

      Migrating /var/db/pkg to ZFS dataset /dev//var_db_pkg.../dev//var_db_pkg: No such file or directory
      ZFS has never been used on this install of pfSense, so that is a problem.

      Suggestions?

      1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        I'm not sure about the ZFS lines, I haven't seen those here, but No address record would be from a lack of DNS. The firewall itself isn't able to resolve the hostnames of the update servers. Either that or it doesn't have a default route or working outbound connectivity.

        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
        • S
          swampkracker
          last edited by

          My internet service has been strange lately, so loss of DNS may have happened in the previous attempt.

          Here is another attempt without the "No address record" errors...

          Updating pfSense-core repository catalogue...
          Fetching meta.conf: . done
          Fetching packagesite.pkg: . done
          Processing entries: .. done
          pfSense-core repository update completed. 14 packages processed.
          Updating pfSense repository catalogue...
          Fetching meta.conf: . done
          Fetching packagesite.pkg: .......... done
          Processing entries: .......... done
          pfSense repository update completed. 538 packages processed.
          All repositories are up to date.

          The following 7 package(s) will be affected (of 0 checked):

          Installed packages to be UPGRADED:
          openvpn: 2.6.0_6 -> 2.6.0_7 [pfSense]
          pfSense: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense]
          pfSense-base: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]
          pfSense-default-config: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]
          pfSense-kernel-pfSense: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]
          pfSense-pkg-System_Patches: 2.0_4 -> 2.0_5 [pfSense]
          pfSense-rc: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]

          Number of packages to be upgraded: 7

          **** WARNING ****
          Reboot will be required!!
          Proceed with upgrade? (y/N) y

          Removing vital flag from php74... done.
          Downloading upgrade packages...
          Updating pfSense-core repository catalogue...
          pfSense-core repository is up to date.
          Updating pfSense repository catalogue...
          pfSense repository is up to date.
          All repositories are up to date.
          Checking for upgrades (7 candidates): ....... done
          Processing candidates (7 candidates): ....... done
          Checking integrity... done (0 conflicting)
          The following 7 package(s) will be affected (of 0 checked):

          Installed packages to be UPGRADED:
          openvpn: 2.6.0_6 -> 2.6.0_7 [pfSense]
          pfSense: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense]
          pfSense-base: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]
          pfSense-default-config: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]
          pfSense-kernel-pfSense: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]
          pfSense-pkg-System_Patches: 2.0_4 -> 2.0_5 [pfSense]
          pfSense-rc: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]

          Number of packages to be upgraded: 7

          Downloading pkg...

          No packages are required to be fetched.
          Integrity check was successful.

          Upgrading pfSense-rc...
          Checking integrity... done (0 conflicting)
          The following 1 package(s) will be affected (of 0 checked):

          Installed packages to be UPGRADED:
          pfSense-rc: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]

          Number of packages to be upgraded: 1
          [1/1] Upgrading pfSense-rc from 22.05.b.20220523.0600 to 22.05.b.20220524.0600...
          ===> Setting net.pf.request_maxcount=400000
          [1/1] Extracting pfSense-rc-22.05.b.20220524.0600: ......... done

          Upgrading pfSense kernel...
          Checking integrity... done (0 conflicting)
          The following 1 package(s) will be affected (of 0 checked):

          Installed packages to be UPGRADED:
          pfSense-kernel-pfSense: 22.05.b.20220523.0600 -> 22.05.b.20220524.0600 [pfSense-core]

          Number of packages to be upgraded: 1
          [1/1] Upgrading pfSense-kernel-pfSense from 22.05.b.20220523.0600 to 22.05.b.20220524.0600...
          [1/1] Extracting pfSense-kernel-pfSense-22.05.b.20220524.0600: .......... done
          ===> Keeping a copy of current kernel in /boot/kernel.old
          Removing unnecessary packages... done.
          System is going to be upgraded. Rebooting in 10 seconds.

          Output of pkg after the reboot:

          [22.05-BETA][root@pfSense.localdomain]/root: pkg info | grep -i pfsense
          check_reload_status-0.0.11 run various pfSense scripts on event.
          pfSense-22.05.b.20220523.0600 Meta package to install pfSense required ports
          pfSense-Status_Monitoring-1.7.11_4 pfSense Status Monitoring
          pfSense-base-22.05.b.20220523.0600 pfSense core files
          pfSense-default-config-22.05.b.20220523.0600 pfSense default config
          pfSense-kernel-pfSense-22.05.b.20220523.0600 pfSense kernel (pfSense)
          pfSense-pkg-System_Patches-2.0_4 pfSense package System_Patches
          pfSense-pkg-WireGuard-0.1.6_2 pfSense package WireGuard (EXPERIMENTAL)
          pfSense-pkg-nut-2.7.4_10 Network UPS Tools
          pfSense-pkg-openvpn-client-export-1.6_4 pfSense package openvpn-client-export
          pfSense-rc-22.05.b.20220523.0600 pfSense rc script and rc.initial shell
          pfSense-repo-22.05.b.20220524.0600 Setup pfSense pkg(8) repositories
          pfSense-upgrade-1.0_22 pfSense upgrade script
          php74-pfSense-module-0.81 Library for getting useful info
          [22.05-BETA][root@pfSense.localdomain]/root:

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

            If you watch the console are there any errors output there? That is odd that it is acting like it's proceeding but then not updating.

            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
            • S
              swampkracker
              last edited by

              No errors appeared in the console while running the update from the WebUI.

              Looking at /var/db/pkg, it is a symbolic link to /root/var/db/pkg.

              [22.05-BETA][root@pfSense.localdomain]/root/var/db/pkg: ls -l
              total 7008
              -rw-r--r-- 1 root wheel 5578752 May 24 08:37 local.sqlite
              -rw-r--r-- 1 root wheel 158 May 24 01:14 pfSense-core.meta
              -rw-r--r-- 1 root wheel 158 May 23 23:07 pfSense.meta
              -rw-r--r-- 1 root wheel 221184 May 24 01:14 repo-pfSense-core.sqlite
              -rw-r--r-- 1 root wheel 1253376 May 23 23:07 repo-pfSense.sqlite
              [22.05-BETA][root@pfSense.localdomain]/root/var/db/pkg:

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

                Do you have RAM disks enabled?

                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
                • S
                  swampkracker
                  last edited by

                  Yes. System has 8GB of RAM with only 4% in use.

                  1 Reply Last reply Reply Quote 0
                  • S
                    swampkracker
                    last edited by

                    Update: saw a new update, 22.05.b.20220524.1701, and tried to update from the console. Except for the strange ZFS errors, everything was fine until this happened:

                    pkg-static: Not enough space in /var/cache/pkg, needed 111 MiB available 106 MiB

                    I increased the ram disk for /var from 256MB to 384MB and rebooted.

                    No warning about /var not having enough space, but the update did not happen.

                    Increased the ram disk for /var to 512MB and rebooted. Again, the update failed.

                    Disabled the ram disk and rebooted.

                    Success! Until further notice, I am not using a ram disk for /tmp and /var.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post