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

    "Assertion failed" from pkg durign 2.3.2 upgrade

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 2 Posters 1.9k 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.
    • J
      jkent3rd
      last edited by

      I hit a similar problem when upgrading through the webapp.  All the packages appeared to install correctly, but on reboot my version appears to still be 2.3.1, the version check on the dashboard fails.  I followed the instructions to do: "pfSense-upgrade -d" from the shell and get the following:

      Updating repositories metadata…
      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.
      Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 399.
      Child process pid=18427 terminated abnormally: Abort trap
      Unlocking package pfSense-kernel-pfSense...
      Unlocking pfSense-kernel-pfSense-2.3.2
      Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 399.
      Child process pid=22692 terminated abnormally: Abort trap

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

      Locking package pfSense-kernel-pfSense...
      Locking pfSense-kernel-pfSense-2.3.2
      [2.3.1-RELEASE][root@LeMonde.local]/root:

      Any ideas?

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

        I split this off the other post because it was not related.

        Try running "pkg update -f", see if it produces any errors. Then try "pkg update" (without the "-f"). If neither of those show an error, see what "pkg upgrade" does.

        Also check what version of pkg you have, you can see that with "pkg info -x pkg"

        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
        • J
          jkent3rd
          last edited by

          Thank you!

          'pkg update -f' and 'pkg update' report no errors.

          'pkg upgrade" yields a similar error:

          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 (65 candidates): 100%
          Processing candidates (65 candidates):  67%

          pfSense-kernel-pfSense-2.3.2 is locked and may not be modified
          Processing candidates (65 candidates): 100%
          Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 399.
          Child process pid=52298 terminated abnormally: Abort trap

          'pkg info -x pkg' yields:

          pfSense-pkg-Avahi-1.11_2
          pfSense-pkg-System_Patches-1.1.4_1
          pkg-1.8.7_1

          1 Reply Last reply Reply Quote 0
          • J
            jkent3rd
            last edited by

            I think I've worked around the problem.

            I ran "pkg info" from the shell and noted all pfSense packages that remained "2.3.1_1".

            I ran "pkg install" for the "2.3.2" version of each of these versions, including "base", "config", and finally "pfSense".

            It uninstalled a dns related package and installed "dnsmasq" but now it reboots, identifies as 2.3.2, and seems to be functioning correctly now.

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