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

    Upgrade from 2.3.4-RELEASE-p1 to 2.4.2 appears to have failed.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 1.3k 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
      ctirado
      last edited by

      I waited a while before attempting to upgrade from 2.3.4 to 2.4.2 as I am one of those people with PPPOE with VLAN tagging on my WAN connection. After playing around with the Update settings, I finally got the system pointed to 2.4.2. So from the GUI, I attempted to upgrade. It said it had over 100 individual packages that need to be updated and it appeared to have downloaded and installed them all. After a reboot, however, the pFsense package appears to still be stuck on version 2.3.4.

      The Dashboard reports:

      2.3.4-RELEASE-p1 (amd64)
      built on Fri Jul 14 14:52:43 CDT 2017
      FreeBSD 11.1-RELEASE-p4

      The system is on the latest version.

      After this I attempted to update with option 13 from the ssh menu and I get the following:

      Updating repositories metadata…
      Updating pfSense-core repository catalogue...
      pkg-static: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
      pkg-static: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz: No address record
      repository pfSense-core has no meta file, using default settings
      pkg-static: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz: No address record
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg-static: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
      pkg-static: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz: No address record
      repository pfSense has no meta file, using default settings
      pkg-static: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz: No address record
      Unable to update repository pfSense
      Error updating repositories!

      The DNS configuration worked just fine for updating before this last attempt from the console. Nothing has changed. I am almost ready to let it be as the system is still connecting me to the Internet, however, the dashboard is showing a ridiculous number of errors and collisions.

      WAN LAN MODEM
      Packets In     243737 120517 0
      Packets Out     120867 241360 0
      Bytes In       330.56 MiB 7.10 MiB 0 B
      Bytes Out     5.92 MiB 330.97 MiB 0 B
      Errors In     120872 242231 121053
      Errors Out       0 0 0
      Collisions       346627577 9947119 352047337

      Not sure if its reporting accurately though as I would figured this number of errors/collisions would make the system unusable and it appears to be anything. Any hints on how to get pFsense straightened out?

      Carlos

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by

        My "2.4.2" install shows :

        2.4.2-RELEASE (amd64)
        built on Mon Nov 20 08:12:56 CST 2017
        FreeBSD 11.1-RELEASE-p4

        So the - your - kernel is upgraded.

        Restart ?
        Or save config and clean install to be sure to reach the goal fast without issues.
        Check-out also the many forum threads about related subjects.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • C
          ctirado
          last edited by

          The system has been restarted several times. I was hoping not to have to do a clean install as the device is in a somewhat inconvenient location. I have seen the threads but many of them reference development versions of 2.4 and it wasn’t clear how much was applicable to my situation. Thanks for responding.

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