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

    Update from 2.3-rc to 2.3.1-development - issue following snapshots by GUI

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    12 Posts 6 Posters 3.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.
    • H
      heper
      last edited by

      Hi,

      i've updated from 04/06  –> 04/14. I wish to keep tracking the snapshots. (goal is not to go to -release)

      since then i'm unable to see package-list / installed packages in the GUI:

      Unable to retrieve package information

      system / update (https://ip/pkg_mgr_install.php?id=firmware) shows this:

      
Current Base System
Latest Base System
Unable to retrieve system versions.

      -updating from console option 13 works without a problem
      -re-saved branch from GUI to "keep following 2.3 development snapshots'
      -gitsync'd to releng_2_3
      -pkg update -f  completes succesfully
      -pkg upgrade -f completes succesfully
      -pkg info -x pfSense:

      
[2.3.1-DEVELOPMENT][root@pfsense.vbees.lan]/root: pkg info -x pfSense
pfSense-2.3.1.a.20160414.1104
pfSense-Status_Monitoring-1.0_1
pfSense-base-2.3.1.a.20160414.0539
pfSense-default-config-2.3.1.a.20160414.0539
pfSense-kernel-pfSense-2.3.1.a.20160414.0539
pfSense-pkg-Cron-0.3.6_2
pfSense-pkg-Quagga_OSPF-0.6.12.1_4
pfSense-pkg-Service_Watchdog-1.8.3
pfSense-pkg-System_Patches-1.1.4_1
pfSense-pkg-arping-1.2.2_1
pfSense-pkg-sudo-0.2.9_2
pfSense-rc-2.3.1.a.20160414.0539
pfSense-repo-2.3.1.a.20160414.0539
php56-pfSense-module-0.12
[2.3.1-DEVELOPMENT][root@pfsense.vbees.lan]/root: 


      
[2.3.1-DEVELOPMENT][root@pfsense.vbees.lan]/root: ls -l /usr/local/etc/pkg/repos/pfSense.conf
lrwxr-xr-x  1 root  wheel  58 Apr 14 23:01 /usr/local/etc/pkg/repos/pfSense.conf -> /usr/local/share/pfSense/pkg/repos/pfSense-repo-devel.conf
[2.3.1-DEVELOPMENT][root@pfsense.vbees.lan]/root:

      what am i missing here?

      1 Reply Last reply Reply Quote 0
      • P
        papadeeh
        last edited by

        I ran into exactly the same problem yesterday and have not found a solution.

        Hope someone knows what to do.

        1 Reply Last reply Reply Quote 0
        • M
          MorpheusRO
          last edited by

          Same problem for me, after one of yesterdays update.

          I tried setting up the update to Follow 2.3 snapshots and move automatically to -RELEASE and after pkg update -f and pkg upgrade -f I could check for updates in the Web Interface, but obviously I was on 2.3 STABLE.
          Change back to Keep following 2.3 development snapshots and after all the updates, I get again the Unable to check for updates / Unable to retrieve system versions error…
          Updating from console Option 13 is working.

          Waiting for a fix…

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

            For those following 2.3.1, the issue there was a regression in pkg 1.7 that broke its output formatting we use. That was just fixed a bit ago, if you run 'pkg update' via SSH, it should prompt to upgrade to pkg 1.7.2_1, which will fix that.

            If you're reading this thread and not intending to follow 2.3.1 snapshots and want release versions, this isn't relevant. Go here.

            1 Reply Last reply Reply Quote 0
            • H
              heper
              last edited by 

              
[2.3.1-DEVELOPMENT][root@pfsense.vbees.lan]/root: pkg update
Updating pfSense-core repository catalogue...
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01    
Fetching packagesite.txz: 100%    2 KiB   2.2kB/s    00:01    
Processing entries: 100%
pfSense-core repository update completed. 13 packages processed.
Updating pfSense repository catalogue...
Fetching meta.txz: 100%    940 B   0.9kB/s    00:01    
Fetching packagesite.txz: 100%   95 KiB  97.1kB/s    00:01    
Processing entries: 100%
pfSense repository update completed. 349 packages processed.

[2.3.1-DEVELOPMENT][root@pfsense.vbees.lan]/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.
Updating database digests format: 100%
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.7.2 -> 1.7.2_1 [pfSense]

2 MiB to be downloaded.

              this works. thanks chris

              1 Reply Last reply Reply Quote 0
              • P
                papadeeh
                last edited by

                Thanks, problem solved…..

                1 Reply Last reply Reply Quote 0
                • N
                  NOYB
                  last edited by

                  @cmb:

                  … if you run 'pkg update' via SSH, ...

                  What is the significance of doing this via SSH?  Will it work via physical console?

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

                    @NOYB:

                    @cmb:

                    … if you run 'pkg update' via SSH, ...

                    What is the significance of doing this via SSH?  Will it work via physical console?

                    It'll work fine from the physical console too. I just noted SSH so people wouldn't try to run it under Diag>Command (where it could potentially hang up the GUI, and you wouldn't get real-time output from it).

                    1 Reply Last reply Reply Quote 0
                    • N
                      NOYB
                      last edited by

                      Kind of what I figured.  Just wanted to be sure there wasn't some weird quirk about it needing a virtual console (ssh).

                      1 Reply Last reply Reply Quote 0
                      • N
                        NOYB
                        last edited by

                        Will the ordinary console option 13 update process pick this change up?

                        1 Reply Last reply Reply Quote 0
                        • N
                          NOYB
                          last edited by

                          This is strange… I didn't run the pkg update command yet.  But today the WebGUI update is showing the versions.  Go figure.  I did do console option 13 but only to see if there was an update.  Didn't apply it.  Said (N)o.

                          1 Reply Last reply Reply Quote 0
                          • W
                            wheemer
                            last edited by

                            I used winscp to connect via SCP and used the command windows to execute "pkg update" but it does nothing.

                            Says everything is up to date, yet I can't check packages or check if there is a system update.

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