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

    Update from 2.3 to 2.3.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    39 Posts 20 Posters 12.5k 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.
    • V Offline
      vectr0n
      last edited by

      Also seeing the same issue with 2.3_1 -> 2.3.1

      [2.3-RELEASE][root@fw0.<removed>.net]/root: pkg update
      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.
      [2.3-RELEASE][root@fw0.<removed>.net]/root: pkg upgrade
      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.
      New version of pkg detected; it needs to be installed first.
      The following 1 package(s) will be affected (of 0 checked):

      Installed packages to be UPGRADED:
              pkg: 1.6.2 -> 1.7.2_2 [pfSense]

      The process will require 91 KiB more space.
      2 MiB to be downloaded.

      Proceed with this action? [y/N]: y
      pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/pkg-1.7.2_2.txz: Not Found

      UPDATE:

      [2.3-RELEASE][root@fw0.<removed>.net]/root: pkg add https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/pkg-1.7.2_2.txz
      Fetching pkg-1.7.2_2.txz: 100%    2 MiB  2.6MB/s    00:01   
      Installing pkg-1.7.2_2…
      the most recent version of pkg-1.6.2 is already installed</removed></removed></removed>

      1 Reply Last reply Reply Quote 0
      • T Offline
        turker
        last edited by 

        >>> 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.
>>> Upgrading pkg...
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.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pkg: 1.6.2 -> 1.7.2_2 [pfSense]

The process will require 91 KiB more space.
2 MiB to be downloaded.
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/pkg-1.7.2_2.txz: Not Found
        1 Reply Last reply Reply Quote 0
        • P Offline
          padenom
          last edited by

          @SlackerDude:

          ….
          The following 1 package(s) will be affected (of 0 checked):

          Installed packages to be UPGRADED:
                  pkg: 1.6.2 -> 1.7.2_2 [pfSense]

          The process will require 91 KiB more space.
          2 MiB to be downloaded.
          pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/pkg-1.7.2_2.txz: Not Found

          I'm getting the same behaviour on my side. However, why does the system look in pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All and not in http://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/ directory?

          PS: I'm new to pkg.

          1 Reply Last reply Reply Quote 0
          • K Offline
            kpa
            last edited by

            The upgrade fails to switch to the correct repository for some reason. On the second try when my upgrade succeeded  I witnessed a message that said "Repository x has a wrong packagesite, need to re-create database" or something like that and it then proceeded to re-download all the repository catalogues using the correct addresses.

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

              Oh, that should work now. Thanks

              1 Reply Last reply Reply Quote 0
              • V Offline
                vectr0n
                last edited by

                I seem to have found a fix:

                Login to SSH # 8

                Run: pfSense-upgrade -u

                You should be able to run the upgrade like normal with option # 13 or via the GUI. Not sure on cause, but this fixes it.

                1 Reply Last reply Reply Quote 0
                • P Offline
                  padenom
                  last edited by

                  Tried another time and it worked OK.

                  This was from the GUI and not from command line.

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

                    @vectr0n:

                    I seem to have found a fix:

                    either that updated the repo URL, or you just happened to catch it after I fixed the source of the issue. No need to do that at this point.

                    1 Reply Last reply Reply Quote 0
                    • B Offline
                      blankphoto
                      last edited by

                      Had the same issue, I just kept trying. Eventually the servers will get through everyone. A staggered release may be in order for the next one, assuming more update  servers are added by then.

                      pfSense WE LOVE GUYS. Keep up the great work.

                      Brian Blankenship
                      Proofpoint Technical Support Engineer

                      1 Reply Last reply Reply Quote 0
                      • J Offline
                        joelserrano
                        last edited by

                        Hi,

                        I have run into this problem (updating from 2.3_1 to 2.3.1):

                        Updating repositories metadata…
                        Updating pfSense-core repository catalogue...
                        pfSense-core repository is up-to-date.
                        Updating pfSense repository catalogue...
                        pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/meta.txz: Forbidden
                        repository pfSense has no meta file, using default settings
                        pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/packagesite.txz: Forbidden
                        Unable to update repository pfSense
                        Failed

                        After a while, now I'm getting this:

                        Updating repositories metadata...
                        Updating pfSense-core repository catalogue...
                        pfSense-core repository is up-to-date.
                        Updating pfSense repository catalogue...
                        pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/meta.txz: Not Found
                        repository pfSense has no meta file, using default settings
                        pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/packagesite.txz: Not Found
                        Unable to update repository pfSense
                        Failed

                        Any suggestions?

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

                          @blankphoto:

                          Had the same issue, I just kept trying. Eventually the servers will get through everyone. A staggered release may be in order for the next one, assuming more update  servers are added by then.

                          No relation to the update server. I screwed up a symlink initially so those on a version that didn't already have the latest version of pkg couldn't fetch it. We were already planning automating that part of the process away for next time around.

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

                            @joelserrano:

                            Hi,

                            I have run into this problem (updating from 2.3_1 to 2.3.1):

                            Any suggestions?

                            looks like you haven't tried since it was fixed.

                            1 Reply Last reply Reply Quote 0
                            • J Offline
                              joelserrano
                              last edited by

                              Update: after retrying several times, now the update is running as expected:

                              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.
                              Upgrading pfSense-repo... done.
                              Updating repositories metadata...
                              Updating pfSense-core repository catalogue...
                              Repository pfSense-core has a wrong packagesite, need to re-create database
                              Fetching meta.txz: . done
                              Fetching packagesite.txz: . done
                              Processing entries: . done
                              […]

                              Thanks!

                              Awesome work with pfSense!! You guys rock!

                              1 Reply Last reply Reply Quote 0
                              • S Offline
                                SlackerDude
                                last edited by

                                running "pfSense-upgrade -u", followed by "pfSense-upgrade -d" appears to be working for me.  I'll be able to confirm once it completes & reboots.

                                UPDATE:  I can confirm a successful upgrade.

                                1 Reply Last reply Reply Quote 0
                                • C Offline
                                  churchi
                                  last edited by

                                  @vectr0n:

                                  I seem to have found a fix:

                                  Login to SSH # 8

                                  Run: pfSense-upgrade -u

                                  You should be able to run the upgrade like normal with option # 13 or via the GUI. Not sure on cause, but this fixes it.

                                  Thanks mate, the -u
                                  switch is what i needed to run first, then the upgrade worked without issues.

                                  Up until I ran this (even after the update by cmb) i was still not able to upgrade to 2.3.1. This was the fix for me.

                                  cheers.

                                  1 Reply Last reply Reply Quote 0
                                  • T Offline
                                    telerocker22
                                    last edited by

                                    I was having the same problem, but instead of rebooting the machine, I went to the "Update Settings" tab, changed it to "Development Snapshots", saved, then put it back to "Stable", and saved again.  After I did that, the update worked fine.  I also saw the "need to re-create database" message.

                                    1 Reply Last reply Reply Quote 0
                                    • JailerJ Offline
                                      Jailer
                                      last edited by

                                      @Jason:

                                      I was having the same problem, but instead of rebooting the machine, I went to the "Update Settings" tab, changed it to "Development Snapshots", saved, then put it back to "Stable", and saved again.  After I did that, the update worked fine.  I also saw the "need to re-create database" message.

                                      This worked for me as well. Thanks for the tip.

                                      1 Reply Last reply Reply Quote 0
                                      • N Offline
                                        nolaquen
                                        last edited by

                                        I'm getting a different error after the update. Any ideas?

                                        Crash report details:

                                        PHP Errors:
                                        [18-May-2016 19:56:23 America/New_York] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/suhosin.so' - /usr/local/lib/php/20131226/suhosin.so: Undefined symbol "ps_globals" in Unknown on line 0

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

                                          @nolaquen:

                                          I'm getting a different error after the update. Any ideas?

                                          Crash report details:

                                          PHP Errors:
                                          [18-May-2016 19:56:23 America/New_York] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/suhosin.so' - /usr/local/lib/php/20131226/suhosin.so: Undefined symbol "ps_globals" in Unknown on line 0

                                          just log spam, the crash reporter suppresses it in 2.3.1+.

                                          1 Reply Last reply Reply Quote 0
                                          • N Offline
                                            nolaquen
                                            last edited by

                                            @cmb:

                                            @nolaquen:

                                            I'm getting a different error after the update. Any ideas?

                                            Crash report details:

                                            PHP Errors:
                                            [18-May-2016 19:56:23 America/New_York] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/suhosin.so' - /usr/local/lib/php/20131226/suhosin.so: Undefined symbol "ps_globals" in Unknown on line 0

                                            just log spam, the crash reporter suppresses it in 2.3.1+.

                                            I appreciate the reply. Just to confirm though, I shouldn't be seeing this? It's popping up on my dashboard via the crash reporter (after updating from 2.3_1 to 2.3.1).

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