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

    Installed 2.3.1_1 showing error

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 1.2k 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.
    • M
      mafiosa
      last edited by

      installed 2.3.1 2 weeks back, then applied _1 update!!! Today _2 update poped up. Then after 30 mins system autonamtically rebooted. Now showing 2.3.1 with:
      The system is on a later version than
      the official release.
      2.3.png
      2.3.png_thumb

      1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad
        last edited by

        I've switched off automatic updates but I'm seeing :-

        Confirmation Required to update pfSense system.
        Current Base System 2.3.1_1
        Latest Base System 2.3.1
        Confirm Update Confirm

        When I try the update its failing :-

        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
        The following 1 package(s) will be affected (of 0 checked):

        Installed packages to be UPGRADED:
        pfSense-Status_Monitoring: 1.3_1 -> 1.4.1_1 [pfSense]

        12 KiB to be downloaded.
        pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/pfSense-Status_Monitoring-1.4.1_1.txz: Not Found

        Locking package pfSense-kernel-pfSense… done.
        Failed

        Andy

        1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

        1 Reply Last reply Reply Quote 0
        • NogBadTheBadN
          NogBadTheBad
          last edited by

          It's not down to the tmp folders created today is it ?

          https://pkg.pfsense.org/

          Index of /

          ../
          pfSense_v2_3_0_amd64-core/                        25-May-2016 21:51                  -
          pfSense_v2_3_0_amd64-pfSense_v2_3_0/              25-May-2016 21:53                  -
          pfSense_v2_3_0_i386-core/                          25-May-2016 21:54                  -
          pfSense_v2_3_0_i386-pfSense_v2_3_0/                25-May-2016 22:00                  -
          pfSense_v2_3_1_amd64-core/                        25-May-2016 21:51                  -
          pfSense_v2_3_1_amd64-core.tmp/                    25-May-2016 22:18                  -
          pfSense_v2_3_1_amd64-pfSense_v2_3_1/              25-May-2016 21:53                  -
          pfSense_v2_3_1_amd64-pfSense_v2_3_1.tmp/          10-Jun-2016 16:12                  -
          pfSense_v2_3_1_i386-core/                          25-May-2016 21:54                  -
          pfSense_v2_3_1_i386-core.tmp/                      25-May-2016 22:21                  -
          pfSense_v2_3_1_i386-pfSense_v2_3_1/                25-May-2016 22:00                  -
          pfSense_v2_3_1_i386-pfSense_v2_3_1.tmp/            10-Jun-2016 16:13                  -

          Andy

          1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

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

            There is no _2. https://forum.pfsense.org/index.php?topic=113435.msg630835#msg630835

            If you messed around with it while things were being changed around earlier, run 'pkg update -f', and upgrade back to 2.3.1_1 if you're on 2.3.1 now.

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