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

    2.3.1 > 2.3.2_1: Unable to update repository…

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    11 Posts 6 Posters 2.4k 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.
    • B Offline
      Bluebrain
      last edited by

      Hello!

      I tried to upgrade from 2.3.1 to 2.3.2_1, but I get the following errors:

      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.
      **** WARNING ****
      Duplicate slice required!!

      Before starting the upgrade process, the currently mounted nanobsd partition
      needs to be cloned to the secondary partition, where the update will happen

      After installation a reboot will be required to switch partition.

      Cleaning secondary partition... done.
      Duplicating current slice... done.
      Restoring slice label... done.
      Testing duplicated partition integrity... done.
      Mounting second partition to run upgrade... done.
      Unlocking package pfSense-kernel-pfSense... done.
      Downloading upgrade packages...
      Updating pfSense-core repository catalogue...
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue…
      Unable to update repository pfSense
      All repositories are up-to-date.
      pkg: Repository pfSense-core cannot be opened. 'pkg update' required
      pkg: Repository pfSense cannot be opened. 'pkg update' required
      Checking for upgrades (0 candidates): . done
      Processing candidates (0 candidates): . done
      Checking integrity… done (0 conflicting)
      Your packages are up to date.

      Any ideas, how to fix that?

      1 Reply Last reply Reply Quote 0
      • ajmA Offline
        ajm
        last edited by

        @Bluebrain:

        pkg: Repository pfSense-core cannot be opened. 'pkg update' required
        pkg: Repository pfSense cannot be opened. 'pkg update' required

        Any ideas, how to fix that?

        Hint:

        @Bluebrain:

        'pkg update' required

        Obvious enough ?

        ;)

        1 Reply Last reply Reply Quote 0
        • D Offline
          doktornotor Banned
          last edited by 

          
pkg update -f; pkg upgrade pkg
          1 Reply Last reply Reply Quote 0
          • B Offline
            Bluebrain
            last edited by

            Still doesn't work.  :'(

            Updating pfSense-core repository catalogue...
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01
Fetching packagesite.txz: 100%    2 KiB   1.9kB/s    00:01
Processing entries: 100%
pfSense-core repository update completed. 9 packages processed.
Updating pfSense repository catalogue...
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01
Fetching packagesite.txz: 100%  110 KiB 112.8kB/s    00:01
Processing entries: 100%
pfSense repository update completed. 406 packages processed.
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 integrity... done (0 conflicting)
Your packages are up to date.

            >>> 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.
**** WARNING ****
Duplicate slice required!!

Before starting the upgrade process, the currently mounted nanobsd partition
needs to be cloned to the secondary partition, where the update will happen

After installation a reboot will be required to switch partition.

>>> Cleaning secondary partition... done.
>>> Duplicating current slice... done.
>>> Restoring slice label... done.
>>> Testing duplicated partition integrity... done.
>>> Mounting second partition to run upgrade... done.
>>> Unlocking package pfSense-kernel-pfSense... done.
>>> Downloading upgrade packages... 
Updating pfSense-core repository catalogue...
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Unable to update repository pfSense
All repositories are up-to-date.
pkg: Repository pfSense-core cannot be opened. 'pkg update' required
pkg: Repository pfSense cannot be opened. 'pkg update' required
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.

            just when I do a "pkg upgrade", it offers me upgrades:

            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 (69 candidates):  65%

pfSense-kernel-pfSense-2.3.1 is locked and may not be modified
Checking for upgrades (69 candidates): 100%
Processing candidates (69 candidates): 100%
The following 69 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        dnsmasq: 2.76,1 [pfSense]

Installed packages to be UPGRADED:
        xinetd: 2.3.15_1 -> 2.3.15_2 [pfSense]
        unbound: 1.5.8 -> 1.5.9 [pfSense]
        strongswan: 5.4.0 -> 5.5.0 [pfSense]
        sqlite3: 3.11.1 -> 3.13.0 [pfSense]
        smartmontools: 6.4_2 -> 6.5_1 [pfSense]
        rrdtool: 1.5.5_1 -> 1.6.0_1 [pfSense]
        relayd: 5.5.20140810_1 -> 5.5.20140810_2 [pfSense]
        python27: 2.7.11_2 -> 2.7.12 [pfSense]
        php56-zlib: 5.6.21 -> 5.6.26 [pfSense]
        php56-xmlwriter: 5.6.21 -> 5.6.26 [pfSense]
        php56-xmlreader: 5.6.21 -> 5.6.26 [pfSense]
        php56-xml: 5.6.21 -> 5.6.26 [pfSense]
        php56-tokenizer: 5.6.21 -> 5.6.26 [pfSense]
        php56-sysvshm: 5.6.21 -> 5.6.26 [pfSense]
        php56-sysvsem: 5.6.21 -> 5.6.26 [pfSense]
        php56-sysvmsg: 5.6.21 -> 5.6.26 [pfSense]
        php56-sqlite3: 5.6.21 -> 5.6.26 [pfSense]
        php56-sockets: 5.6.21 -> 5.6.26 [pfSense]
        php56-simplexml: 5.6.21 -> 5.6.26 [pfSense]
        php56-shmop: 5.6.21 -> 5.6.26 [pfSense]
        php56-session: 5.6.21 -> 5.6.26 [pfSense]
        php56-readline: 5.6.21 -> 5.6.26 [pfSense]
        php56-posix: 5.6.21 -> 5.6.26 [pfSense]
        php56-pdo_sqlite: 5.6.21 -> 5.6.26 [pfSense]
        php56-pdo: 5.6.21 -> 5.6.26 [pfSense]
        php56-pcntl: 5.6.21 -> 5.6.26 [pfSense]
        php56-openssl: 5.6.21 -> 5.6.26 [pfSense]
        php56-opcache: 5.6.21 -> 5.6.26_1 [pfSense]
        php56-mcrypt: 5.6.21 -> 5.6.26 [pfSense]
        php56-mbstring: 5.6.21 -> 5.6.26 [pfSense]
        php56-ldap: 5.6.21 -> 5.6.26 [pfSense]
        php56-json: 5.6.21 -> 5.6.26 [pfSense]
        php56-hash: 5.6.21 -> 5.6.26 [pfSense]
        php56-gettext: 5.6.21 -> 5.6.26 [pfSense]
        php56-filter: 5.6.21 -> 5.6.26 [pfSense]
        php56-dom: 5.6.21 -> 5.6.26 [pfSense]
        php56-curl: 5.6.21 -> 5.6.26 [pfSense]
        php56-ctype: 5.6.21 -> 5.6.26 [pfSense]
        php56-bz2: 5.6.21 -> 5.6.26 [pfSense]
        php56-bcmath: 5.6.21 -> 5.6.26 [pfSense]
        php56: 5.6.21 -> 5.6.26 [pfSense]
        php-xdebug: 2.2.5 -> 2.4.0 [pfSense]
        pfSense-rc: 2.3.1 -> 2.3.2_1 [pfSense-core]
        pfSense-default-config-serial: 2.3.1 -> 2.3.2_1 [pfSense-core]
        pfSense-base-nanobsd: 2.3.1 -> 2.3.2_1 [pfSense-core]
        pfSense-Status_Monitoring: 1.3_1 -> 1.4.4_2 [pfSense]
        pfSense: 2.3.1 -> 2.3.2_1 [pfSense]
        perl5: 5.20.3_12 -> 5.20.3_15 [pfSense]
        pecl-rrd: 1.1.3_2 -> 1.1.3_3 [pfSense]
        pecl-radius: 1.2.7 -> 1.3.0 [pfSense]
        pcre: 8.38_1 -> 8.39 [pfSense]
        ntp: 4.2.8p7 -> 4.2.8p8 [pfSense]
        nginx: 1.8.1,2 -> 1.10.1,2 [pfSense]
        libxml2: 2.9.3 -> 2.9.4 [pfSense]
        libssh2: 1.6.0_1,2 -> 1.7.0,2 [pfSense]
        libidn: 1.31 -> 1.33_1 [pfSense]
        libedit: 3.1.20150325_2 -> 3.1.20150325_2,1 [pfSense]
        isc-dhcp43-server: 4.3.3P1_1 -> 4.3.4 [pfSense]
        isc-dhcp43-relay: 4.3.3P1_1 -> 4.3.4_1 [pfSense]
        isc-dhcp43-client: 4.3.3P1_1 -> 4.3.4 [pfSense]
        ipmitool: 1.8.15_1 -> 1.8.17_1 [pfSense]
        gettext-runtime: 0.19.7 -> 0.19.8.1 [pfSense]
        filterlog: 0.1_2 -> 0.1_4 [pfSense]
        expat: 2.1.0_3 -> 2.1.1_2 [pfSense]
        curl: 7.48.0_1 -> 7.50.3 [pfSense]
        ca_root_nss: 3.22.2 -> 3.25 [pfSense]
        bind-tools: 9.10.3P4 -> 9.10.4P2 [pfSense]

Installed packages to be REINSTALLED:
        scponly-4.8.20110526_2 [pfSense] (options changed)

Number of packages to be installed: 1
Number of packages to be upgraded: 67
Number of packages to be reinstalled: 1

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

Proceed with this action? [y/N]:
            1 Reply Last reply Reply Quote 0
            • X Offline
              xmalcomx
              last edited by

              Up to here I have arrived, but how do I tell it to you?

              1 Reply Last reply Reply Quote 0
              • R Offline
                RenegadeTech
                last edited by

                I'm having this same exact problem since upgrading to 2.3.2-RELEASE on the Nano distribution. I couldn't install _p1 and now can't install 2.3.3.

                pkg update -f works fine (437 packages processed) but pkg upgrade pkg just results in Your packages are up to date. without having installed anything. I'm on pkg version 1.9.4. Is that the latest? (How can I check?)

                What can I try next?

                1 Reply Last reply Reply Quote 0
                • D Offline
                  doktornotor Banned
                  last edited by

                  Doing a fresh install and restoring the config will be probably couple of days faster than debugging braindead pkg package "manager".

                  1 Reply Last reply Reply Quote 0
                  • R Offline
                    RenegadeTech
                    last edited by

                    That's what I was going to try next time I'm on site. It's a good opportunity to switch to the regular distro since Nano is being dropped in 2.4 from the sounds of things.

                    Can I restore a 2.3.2 Nano config onto a fresh 2.3.3 Regular system?

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      doktornotor Banned
                      last edited by

                      Yes, that works just fine. (Assuming it's the same HW, otherwise I'd recommend to edit the assigned interfaces in the XML to match the new box.)

                      1 Reply Last reply Reply Quote 0
                      • P Offline
                        phil.davis
                        last edited by

                        You could try the process described here: https://forum.pfsense.org/index.php?topic=125873.msg695386#msg695386

                        (switching to development, starting a upgrade freom console, saying no, switching back to stable)

                        That might force a reinstall/refresh of the whole pkg database and "trick" it into knowing what it should do.

                        But make sure to have a backup of the config first, and be ready to take @doktornoktor advice above.

                        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          RenegadeTech
                          last edited by

                          One more question: I have two boxes in failover config. Will there be any problems if one is running Nano while the other is on Regular?

                          Thanks so much for the help!

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