A few problems post upgrade
-
When I do that, will it backup the configuration for the PACKAGES as well?
Because, actually, I'd like to backup all configuration EXCEPT for the packages.
-
the config contains everything but you can backup/restore only sections if you'd want to ( one at a time)
-
Be careful with 'packages', some are real show stopper, break pfSense from upgrading (you already found that issue).
Backup your config settings (that is THE advantage of pfSense, everything is put in one place, easy to backup) with all the settins - and after a full, clean install, import your settings. Install and activate one package at the time, but check out if it is stable in 2.2.2 first. -
At this point the only packages I need are :
-
SQUID3
-
APCUPSd
-
OpenVPN export
So I'm going to do that… backup and restore.
But I see where to include or exclude those settings in the Backup/restore tab... unless it's the "package manager" one?
-
-
For posterity, the problem here is that your system finished the upgrade, but failed to reboot. Force a reboot, either on console, if you can get in, or by pulling the power/resetting the VM. That will fix the problem. If you're running in VMWare, don't forget to upgrade the VMTools.
Note that you're still running FreeBSD 8.3 on 2.2. That shouldn't be possible. If you look at your web interface, you'll also see an uptime counter that hasn't reset.
–Ted
First I was unable to auto-update :
https://forum.pfsense.org/index.php?topic=91575.0I got fed up and went for a manual firmware upgrade by downloading the update file from pfsense.org
So that's that.
Now I'm up to date.However, after the reboot, I've been getting these errors :
Crash report begins. Anonymous machine information: amd64 8.3-RELEASE-p16 FreeBSD 8.3-RELEASE-p16 #0: Mon Aug 25 08:27:11 EDT 2014 root@pf2_1_1_amd64.pfsense.org:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.8 -
For posterity, the problem here is that your system finished the upgrade, but failed to reboot. Force a reboot, either on console, if you can get in, or by pulling the power/resetting the VM. That will fix the problem. If you're running in VMWare, don't forget to upgrade the VMTools.
Note that you're still running FreeBSD 8.3 on 2.2. That shouldn't be possible. If you look at your web interface, you'll also see an uptime counter that hasn't reset.
–Ted
So what's the best fix then?
Wipe out and re-install fresh?
-
So what's the best fix then?
Wipe out and re-install fresh?
Not sure. I force power-cycled the system and when it booted, it came up cleanly. Rebooting through PFSense failed every time. I had to pull the power/hit the reset button. If you're still having problems after a true boot, then a wipe and re-install is probably your best choice.
-
Just power cycling is fine in that circumstance where it doesn't reboot on its own. That's part of an issue we'll get resolved for 2.2.3. https://redmine.pfsense.org/issues/4653
-
Hopefully on topic… as 2x upgrades had to be manually rebooted, and then both produced crashdumps within 48 hours. Both are VMWare images; outstandingly stable history, and OpenVM-Tools is current. I submitted and deleted the reports after cursory review. Didn't really understand what I was looking at. Who checks the submitted crashdump reports, and is there some follow up? We're Gold level members.
-
So what's the best fix then?
Wipe out and re-install fresh?
Not sure. I force power-cycled the system and when it booted, it came up cleanly. Rebooting through PFSense failed every time. I had to pull the power/hit the reset button. If you're still having problems after a true boot, then a wipe and re-install is probably your best choice.
I did force the power cycling.
On the dashboard I get:
2.2.2-RELEASE (amd64) built on Mon Apr 13 20:10:22 CDT 2015 FreeBSD 10.1-RELEASE-p9 Unable to check for updates.Everything seems fine… although I don't know why I'm unable to check for updates.
