System is on a later version than the official release / Latest 0.18_1



  • Getting the system is on a later version than offical message on 2.3.3 boxes today.
    Update shows latest base is 0.18_1
    Something broken?



  • I am also getting the same message today …


  • Banned

    ??? ??? ??? ??? ??? ???



  • I’m seeing the same on my box at home.  Just noticed it today.  Upgraded to 2.3.3 4 days ago.



  • Same here
    so wait until someone fix it.




  • I had the time and spare box to let it “do its thing” and confirmed the update in System->Update …… it went through its motions and apparently did update something …
    Anyway, all is well and System->Update now reflects that everything is updated.


  • Administrator

    Since it didn’t happen on any of my test boxes, could you go to console and run following command, then send me the output?

    pfSense-upgrade -c -d

    This is harmless and will only say if there is a new version available.



  • ~~Only on one of my several boxes so far…         ~~

    Going back through them they are all showing it now.

    /root: pfSense-upgrade -c -d

    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.
    0.18_1 version of pfSense-upgrade is available



  • I have the same output as chpalmer:

    [2.3.3-RELEASE][admin@pfsense]/root: pfSense-upgrade -c -d

    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.
    0.18_1 version of pfSense-upgrade is available



  • Seeing on both Netgate boxes and my own boxes with “CE”…  2.3.3R only. No issues with my 2.4B boxes.



  • Found this notice when I signed into my pfsense firewall.  I’m currently on the latest release, however it’s saying the “official release” is 0.18_1.  See attachments.

    ![Screen Shot 2017-03-02 at 5.46.55 PM.png](/public/imported_attachments/1/Screen Shot 2017-03-02 at 5.46.55 PM.png)
    ![Screen Shot 2017-03-02 at 5.46.55 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-03-02 at 5.46.55 PM.png_thumb)
    ![Screen Shot 2017-03-02 at 5.47.10 PM.png](/public/imported_attachments/1/Screen Shot 2017-03-02 at 5.47.10 PM.png)
    ![Screen Shot 2017-03-02 at 5.47.10 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-03-02 at 5.47.10 PM.png_thumb)


  • Administrator

    Can you please run this and send me output?

    sh -x /usr/local/sbin/pfSense-upgrade -c -d





  • sh -x /usr/local/sbin/pfSense-upgrade -c -d

    • export LANG=C
    • basename /usr/local/sbin/pfSense-upgrade
    • pid_file=/var/run/pfSense-upgrade.pid
    • logfile=/cf/conf/upgrade_log.txt
    • stdout=/dev/null
    • /usr/local/sbin/read_xml_tag.sh string system/proxyurl
    • HTTP_PROXY=’’
    • [ ‘’ != ‘’ ]
    • export ASSUME_ALWAYS_YES=true
    • export FETCH_TIMEOUT=5
    • export FETCH_RETRY=2
    • /usr/local/bin/php -n /usr/local/sbin/read_global_var product_name pfSense
    • export product=pfSense
    • /usr/local/bin/php -n /usr/local/sbin/read_global_var pkg_prefix pfSense-pkg-
    • export pkg_prefix=pfSense-pkg-
    • cat /etc/platform
    • export platform=pfSense
    • /usr/local/sbin/read_xml_tag.sh boolean system/use_mfs_tmpvar
    • USE_MFS_TMPVAR=false
    • [ pfSense = nanobsd ]
    • [ false = true ]
    • cat /etc/version
    • product_version=2.3.3-RELEASE
    • /usr/local/sbin/read_xml_tag.sh boolean system/do_not_send_host_uuid
    • do_not_send_host_uuid=false
    • [ false != true ]
    • sysctl kern.hostuuid
    • hostuuid=‘kern.hostuuid: d6502627-f84c-11e6-9c64-00095b8f1b71’
    • export ‘HTTP_USER_AGENT=pfSense/2.3.3-RELEASE:kern.hostuuid: d6502627-84c-11e6-9c64-00095b8f1b71’
    • validate_repo_conf
    • pkg_repo_conf=/usr/local/etc/pkg/repos/pfSense.conf
    • default_pkg_repo_conf_path=/usr/local/share/pfSense/pkg/repos/pfSense-repo.con                                                                                                                                                            f
    • /usr/local/sbin/read_xml_tag.sh string system/pkg_repo_conf_path
    • pkg_repo_conf_path=/usr/local/share/pfSense/pkg/repos/pfSense-repo.conf
    • [ -z /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf -o ! -f /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf ]
    • [ -f /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf ]
    • [ -e /usr/local/etc/pkg/repos/pfSense.conf -a ! -L /usr/local/etc/pkgrepos/pfSense.conf ]
    • readlink /usr/local/etc/pkg/repos/pfSense.conf
    • [ /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf != /usr/localshare/pfSense/pkg/repos/pfSense-repo.conf ]
    • export delete_annotation=
    • export unlock_additional_pkgs=
    • export pkg_chroot=
    • export chroot_dir=
    • export nc_pid=
    • export reboot_after=10
    • export reboot_params=
    • unset dry_run
    • unset dont_reboot
    • unset dont_update
    • unset booting
    • unset boot_stage
    • unset force
    • unset yes
    • unset progress_file
    • unset progress_socket
    • unset action
    • unset action_pkg
    • unset force_ipv4
    • unset force_ipv6
    • getopts 46b:cdfi:hp:l:nr:RuUy opt
    • action=check
    • getopts 46b:cdfi:hp:l:nr:RuUy opt
    • stdout=’’
    • getopts 46b:cdfi:hp:l:nr:RuUy opt
    • [ -n ‘’ ]
    • [ -n ‘’ ]
    • : check
    • pgrep -qF /var/run/pfSense-upgrade.pid
    • [ -z ‘’ -o ‘’ != 2 ]
    • /usr/local/bin/php /etc/rc.conf_mount_rw
    • [ -n ‘’ ]
    • echo 4146
      /usr/local/sbin/pfSense-upgrade: cannot create /var/run/pfSense-upgrade.pid: Permission denied
    • trap _exit 1 2 15 EXIT
    • [ check != upgrade -a -f /cf/conf/upgrade_log.txt ]
    • rm -f /cf/conf/upgrade_log.txt
      rm: /cf/conf/upgrade_log.txt: Permission denied
    • progress_file=/cf/conf/upgrade_log.json
    • [ -e /cf/conf/upgrade_log.json ]
    • abi_setup
    • uname -r
    • local _freebsd_version=10.3-RELEASE-p16
    • local _pkg_repo_conf=/usr/local/etc/pkg/repos/pfSense.conf
    • uname -p
    • local _arch=i386
    • CUR_ABI=FreeBSD:10:i386
    • [ i386 == armv6 ]
    • [ i386 == i386 ]
    • CUR_ALTABI=freebsd:10:x86:32
    • [ ! -e /usr/local/etc/pkg/repos/pfSense.conf ]
    • readlink /usr/local/etc/pkg/repos/pfSense.conf
    • local _repo_abi_file=/usr/local/share/pfSense/pkg/repos/pfSense-repo.conf
    • [ -f /usr/local/share/pfSense/pkg/repos/pfSense-repo.abi ]
    • cat /usr/local/share/pfSense/pkg/repos/pfSense-repo.abi
    • ABI=FreeBSD:10:i386
    • [ -f /usr/local/share/pfSense/pkg/repos/pfSense-repo.altabi ]
    • cat /usr/local/share/pfSense/pkg/repos/pfSense-repo.altabi
    • ALTABI=freebsd:10:x86:32
    • echo ABI=FreeBSD:10:i386
      /usr/local/sbin/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Permission denied
    • echo ALTABI=freebsd:10:x86:32
      /usr/local/sbin/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Permission denied
    • [ FreeBSD:10:i386 = FreeBSD:10:i386 -o FreeBSD:10:i386 = freebsd:10:x86:32 ]
    • NEW_MAJOR=’’
    • export CUR_ABI CUR_ALTABI ABI ALTABI NEW_MAJOR
    • [ -n ‘’ -a check = install ]
    • check_upgrade
    • get_meta_pkg_name
    • is_pkg_installed pfSense-vmware
    • local _pkg_name=pfSense-vmware
    • shift
    • local _pkg_chroot=
    • pkg info -e pfSense-vmware
    • return 1
    • is_pkg_installed pfSense
    • local _pkg_name=pfSense
    • shift
    • local _pkg_chroot=
    • pkg info -e pfSense
    • return 0
    • echo pfSense
    • local _meta_pkg=pfSense
    • pkg_update ‘’ mute
    • local _force=
    • local _mute=
    • [ ‘’ = force ]
    • [ -z ‘’ -a -n ‘’ ]
    • [ mute = mute ]
    • _mute=mute
    • abi_setup
    • uname -r
    • local _freebsd_version=10.3-RELEASE-p16
    • local _pkg_repo_conf=/usr/local/etc/pkg/repos/pfSense.conf
    • uname -p
    • local _arch=i386
    • CUR_ABI=FreeBSD:10:i386
    • [ i386 == armv6 ]
    • [ i386 == i386 ]
    • CUR_ALTABI=freebsd:10:x86:32
    • [ ! -e /usr/local/etc/pkg/repos/pfSense.conf ]
    • readlink /usr/local/etc/pkg/repos/pfSense.conf
    • local _repo_abi_file=/usr/local/share/pfSense/pkg/repos/pfSense-repo.conf
    • [ -f /usr/local/share/pfSense/pkg/repos/pfSense-repo.abi ]
    • cat /usr/local/share/pfSense/pkg/repos/pfSense-repo.abi
    • ABI=FreeBSD:10:i386
    • [ -f /usr/local/share/pfSense/pkg/repos/pfSense-repo.altabi ]
    • cat /usr/local/share/pfSense/pkg/repos/pfSense-repo.altabi
    • ALTABI=freebsd:10:x86:32
    • echo ABI=FreeBSD:10:i386
      /usr/local/sbin/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Permission denied
    • echo ALTABI=freebsd:10:x86:32
      /usr/local/sbin/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Permission denied
    • [ FreeBSD:10:i386 = FreeBSD:10:i386 -o FreeBSD:10:i386 = freebsd:10:x86:32 ]
    • NEW_MAJOR=’’
    • export CUR_ABI CUR_ALTABI ABI ALTABI NEW_MAJOR
    • _exec ‘pkg  update’ ‘Updating repositories metadata’ mute
    • local ‘_cmd=pkg  update’
    • local ‘_msg=Updating repositories metadata’
    • local _mute=mute
    • local _ignore_result=
    • local _stdout=
    • [ -z ‘pkg  update’ -o -z ‘Updating repositories metadata’ ]
    • [ mute != mute ]
    • _echo -n '>>> Updating repositories metadata… ’
    • local _n=
    • [ -n = -n ]
    • shift
    • _n=-n
    • [ -z /cf/conf/upgrade_log.txt ]
    • echo -n '>>> Updating repositories metadata… ’
    • tee -a /cf/conf/upgrade_log.txt
      tee: /cf/conf/upgrade_log.txt: Permission denied

    Updating repositories metadata… + [ -z ‘’ ]

    • _echo ‘’

    • local _n=

    • [ ‘’ = -n ]

    • [ -z /cf/conf/upgrade_log.txt ]

    • echo ‘’

    • tee -a /cf/conf/upgrade_log.txt
      tee: /cf/conf/upgrade_log.txt: Permission denied

    • exec

    • pkg update

    • tee -a /cf/conf/upgrade_log.txt
      tee: /cf/conf/upgrade_log.txt: Permission denied
      pkg: Insufficient privileges to update the repository catalogue.

    • printf 77

    • local _result=77

    • exec

    • [ 77 -eq 0 -o -n ‘’ ]

    • [ -n ‘’ ]

    • _exit 1

    • trap - 1 2 15 EXIT

    • pkg_lock

    • local _pkgs=

    • [ -z ‘’ ]

    • return

    • [ -f /var/run/pfSense-upgrade.pid ]

    • [ -n ‘’ ]

    • [ -z ‘’ -o ‘’ != 2 ]

    • /usr/local/bin/php /etc/rc.conf_mount_ro

    • [ -n ‘’ ]

    • [ -n ‘’ ]

    • [ -n ‘’ ]

    • local _rc=1

    • [ -n ‘’ ]

    • exit 1


  • Administrator

    I’ve pushed a fix, it’s on pfSense-upgrade 0.19.

    pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.

    Fix is on version 0.19. As soon as it’s available it’s safe to manually run ‘pkg upgrade pfSense-upgrade’ on console to go to latest verssion.

    This issue is being tracked at https://redmine.pfsense.org/issues/7343

    Sorry for the inconvenience



  • Now I get :




  • My boxes are now showing up to date 2.3.3 without any updating by me.

    Going to console and running…

    pkg upgrade pfSense-upgrade

    Im prompted with an upgrade from 0.17 to 0.19…



  • the command

    pkg upgrade pfSense-upgrade

    fixed for me



  • It’s fine now now without any intervention  ;D




  • After “pkg upgrade pfSense-upgrade” as proposed above :

    [2.3.3-RELEASE][admin@pfsense.brit-hotel-fumel.net]/root: pkg upgrade pfSense-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.
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
            pfSense-upgrade: 0.17 -> 0.19 [pfSense]
    
    Number of packages to be upgraded: 1
    
    11 KiB to be downloaded.
    
    Proceed with this action? [y/N]: Y
    Fetching pfSense-upgrade-0.19.txz: 100%   11 KiB  11.5kB/s    00:01
    Checking integrity... done (0 conflicting)
    [1/1] Upgrading pfSense-upgrade from 0.17 to 0.19...
    [1/1] Extracting pfSense-upgrade-0.19: 100%
    

    all reverted to normal.



  • I open the Dashboard then went to  System Update

    @/cf/conf/upgrade_log.txt:

    Updating repositories metadata… done.
    0.19 version of pfSense-upgrade is available

    -rw-r–r--  1 root  wheel      89 Mar  3 03:17 upgrade_log.txt
    LOL Then a few minutes later going back to System Update I get :  😮 😮 😮



  • Banned



  • I upgraded without issues to 2.3.3 last week, suddenly, yesterday, I started to see “The system is on a later version than
    the official release.” in the GUI.

    I did not change or do anything since the upgrade so this is certainly coming from somewhere else.

    Thanks.



  • Same for me.  This is what I see on the update page.  0.19??



  • Not sure if we now have an official solution to this, but, do we know why this happened?
    (Just when I thought upgrade issues had been ironed-out…).

    Thanks.

    @RonpfS:

    https://forum.pfsense.org/index.php?topic=126523


  • Rebel Alliance Developer Netgate

    N.B.: I merged several identical threads together, so if it appears that people didn’t see/read earlier responses, it’s likely because they were not originally part of this thread, so be kind in replies.

    If you are seeing this and still experience the issue, please re-read this post starting from the first page.



  • @jimp:

    N.B.: I merged several identical threads together, so if it appears that people didn’t see/read earlier responses, it’s likely because they were not originally part of this thread, so be kind in replies.

    If you are seeing this and still experience the issue, please re-read this post starting from the first page.

    all fixed now, thanks for merging the threads.



  • seeing 0.20 now




  • I just applied patch 0.20 to my systems.

    System rebooted afterwards and looking healthy again.
    To be clear, the update is valid right? Not a cosmetic bug.
    I thought the update was part of the new patch-system.
    Thanks for the great work!


  • Rebel Alliance Developer Netgate

    There was an update for pfSense-upgrade, not the whole system. That update is good/legitimate.



  • Yeah… since i pressed the update key in the notion of “nothing bad will happen”, i was NOT expecting a full reboot……

    But well… A couple of unhappy faces can be survived on a late friday i guess  ::)

    C



  • @Renato:

    I’ve pushed a fix, it’s on pfSense-upgrade 0.19.

    pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.

    Fix is on version 0.19. As soon as it’s available it’s safe to manually run ‘pkg upgrade pfSense-upgrade’ on console to go to latest verssion.

    This issue is being tracked at https://redmine.pfsense.org/issues/7343

    Sorry for the inconvenience

    So the only way to fix this “issue” is to run pkg upgrade pfSense-upgrade from the console?
    And it won’t reboot the box ?



  • Dunno about the console command, but running the upgrade on the web-gui updated AND rebooted… But showing “you are on the latest version” now, so its “good” 🙂

    C



  • Mine also showed the “upgrade” to 0.20 and after pressing Confirm to let it do it, all is well reporting 2.3.3

    The issue is that there are multiple “parts/packages” that make up “pfSense”. Normally “parts” would be released along with actual new code that has a “proper” release version. So it would find the “main” version to display and say that “2.3.4” (for example) is available. But in this case there have been some changes/fixes to the bit called pfsense-upgrade going from about 0.16 to 0.20. The GUI code sees that 0.20<2.3.3 and thus says that the system 2.3.3 is newer than what it thinks is the release version (0.20).

    I guess the code that parses the results of checking for upgrades needs to be smarter, and understand what pieces might come separately from the complete release. Then it needs to work out how to explain to the user that the “main” version is still 2.3.3 but that some component(s) upgrade is available.



  • The proper solution to this would be to present two types of updates to the user, one that is the “firmware” level update and one that only updates the individual packages within a version of the firmware.



  • @RonpfS:

    @Renato:

    I’ve pushed a fix, it’s on pfSense-upgrade 0.19.

    pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.

    Fix is on version 0.19. As soon as it’s available it’s safe to manually run ‘pkg upgrade pfSense-upgrade’ on console to go to latest verssion.

    This issue is being tracked at https://redmine.pfsense.org/issues/7343

    Sorry for the inconvenience

    So the only way to fix this “issue” is to run pkg upgrade pfSense-upgrade from the console?
    And it won’t reboot the box ?

    Using the GUI upgrade button will fix this, but will reboot.

    Using the console ‘pkg upgrade pfSense-upgrade’ will fix this and does not require a reboot.



  • [2.3.3-RELEASE][root@somewhere.local]/root: pkg upgrade pfSense-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.
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
            pfSense-upgrade: 0.17 -> 0.20 [pfSense]
    
    Number of packages to be upgraded: 1
    
    11 KiB to be downloaded.
    
    Proceed with this action? [y/N]: y
    Fetching pfSense-upgrade-0.20.txz: 100%   11 KiB  11.5kB/s    00:01
    Checking integrity... done (0 conflicting)
    [1/1] Upgrading pfSense-upgrade from 0.17 to 0.20...
    [1/1] Extracting pfSense-upgrade-0.20: 100%
    [2.3.3-RELEASE][root@somewhere.local]/root:
    
    




  • I’m seeing the same thing as well but am showing the latest base system as 0.20. Looked at the issue tracking and saw I’m not the only one who sees 0.20.



  • @nipstech:

    I’m seeing the same thing as well but am showing the latest base system as 0.20. Looked at the issue tracking and saw I’m not the only one who sees 0.20.

    That is true. Just do the suggested “upgrade”. It will install that component that is v0.20. Then it will understand that the system as a whole is up-to-date running 2.3.3.

    The logic there just needs to know that components might be needing an update, not the “system as a whole”, and have a way to “explain” that to the user.



  • The system is on a later version than
    the official release.

    Current Base System
    2.3.3
    Latest Base System
    0.20
    Confirm Update

    Going to try the update

    Strange, it just fixed itself before I could run the update
    The system is on the latest version.


 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy