System is on a later version than the official release / Latest 0.18_1
-
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.
 -
-
https://forum.pfsense.org/index.php?topic=126523
-
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
-
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 : :o :o :o
-
https://github.com/pfsense/FreeBSD-ports/commit/dcb288ff472f374b51ba60b36f65ca9eabc8165a
-
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.
https://forum.pfsense.org/index.php?topic=126523
-
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.
-
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!
