Retired > 2.3-RC Snapshot Feedback and Issues - ARCHIVED

HEADS UP: error expected during your next upgrade, but it will work fine

(1/2) > >>

cmb:
When you next upgrade, the system will spit out an error and may claim the upgrade failed, but will continue and reboot. The repo-devel package had to be removed as part of getting to a final release, and unfortunately not a way to make that not error out on already-installed systems. It'll still upgrade just fine, the failure's just log noise. And it won't happen again.


EDIT: [jimp]:

For issues updating from RC (or older) to -RELEASE:

If you see "unable to check for updates", make sure you have pfSense-base installed (check the output of "pkg info -x pfSense"). If missing, run "pkg install pfSense-base"

If you see an error when checking for or installing updates that states no trusted keys could be found, run the following command from the shell or Diagnostics > Command:


--- Code: ---fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_0/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406
--- End code ---

Eniqmatic:
Thanks for the heads up and continued effort into improving pfSense!

heper:
didn't automatically wake up for me. (might be unrelated)
had to manually power it down/restart. It's headless, so no clue if any error was showing.

logs once it booted

--- Code: ---Apr 6 13:21:51 kernel root@ce23-i386-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense i386
Apr 6 13:21:51 kernel FreeBSD 10.3-RELEASE #12 eac8329(RELENG_2_3): Tue Apr 5 21:11:57 CDT 2016
Apr 6 13:21:51 kernel FreeBSD is a registered trademark of The FreeBSD Foundation.
Apr 6 13:21:51 kernel The Regents of the University of California. All rights reserved.
Apr 6 13:21:51 kernel Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Apr 6 13:21:51 kernel Copyright (c) 1992-2016 The FreeBSD Project.
Apr 6 13:21:51 syslogd kernel boot file is /boot/kernel/kernel

<<<<<<----- power-cycled it around 13:21 ----->>>>>>>

Apr 6 13:13:33 syslogd exiting on signal 15
Apr 6 13:13:32 shutdown reboot by root:
Apr 6 13:13:22 xinetd 18385 Reconfigured: new=0 old=1 dropped=0 (services)
Apr 6 13:13:22 xinetd 18385 readjusting service 6969-udp
Apr 6 13:13:22 xinetd 18385 Swapping defaults
Apr 6 13:13:22 xinetd 18385 Starting reconfiguration
Apr 6 13:13:22 php-fpm 69464 /rc.start_packages: Restarting/Starting all packages.
Apr 6 13:13:21 check_reload_status Starting packages
Apr 6 13:13:21 check_reload_status Reloading filter
Apr 6 13:13:19 pkg pfSense-kernel-pfSense upgraded: 2.3.r.20160401.0002 -> 2.3.r.20160405.2024
Apr 6 13:13:13 pkg pfSense-rc upgraded: 2.3.r.20160401.0002 -> 2.3.r.20160405.2024
Apr 6 13:12:33 check_reload_status Syncing firewall

--- End code ---

whocares:
>>> 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.
ERROR: It was not possible to determine pfSense-repo-devel remote version
Failed

does not reboot after that

jimp:
I updated about a dozen VMs and most of them showed that and rebooted on their own. Only one required manual intervention, the others only needed to sit and wait for the update to finish and then they rebooted themselves.

Not sure what happened on the problem one, but probably was due to my own meddling, I likely did not allow it enough time to finish before fiddling with it.

Navigation

[0] Message Index

[#] Next page

Go to full version