Problem upgrading 2.3.2-RELEASE-p1 to 2.3.3
-
Greetings community. I'm having a strange issue trying to upgrade. I went through the process initially using the web GUI, but failed. Unfortunately I didn't capture the failure message. I then rebooted and tried via the console and got the below. Nothing happens, the system does not reboot and the version stays as is. I have installed Suricata, ntopng, and openvpn client export packages. I've tried multiple reboots and attempts, no-go. Any help is appreciated , or if its easier to just re-install and restore I'll do that.
uname -a
FreeBSD pfsense.hexmesh.net 10.3-RELEASE-p9 FreeBSD 10.3-RELEASE-p9 #1 5fc1b19(RELENG_2_3_2): Tue Sep 27 12:26:06 CDT 2016 root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense amd64[2.3.2-RELEASE][root@pfsense.hexmesh.net]/cf/conf: exit
exit
*** Welcome to pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfsense ***WAN (wan) -> em0 -> v4/DHCP4: 172.73.177.151/20
v6/DHCP6: 2606:a000:dfc0:9e:ac:ad13:444f:b4bc/128
LAN (lan) -> em1 -> v4: 10.0.25.1/16
OPT1 (opt1) -> re0 ->- Logout (SSH only) 9) pfTop
- Assign Interfaces 10) Filter Logs
- Set interface(s) IP address 11) Restart webConfigurator
- Reset webConfigurator password 12) PHP shell + pfSense tools
- Reset to factory defaults 13) Update from console
- Reboot system 14) Disable Secure Shell (sshd)
- Halt system 15) Restore recent configuration
- Ping host 16) Restart PHP-FPM
- Shell
Enter an option: 13
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.
Unlocking package pfSense-kernel-pfSense... done.
Your packages are up to date
Locking package pfSense-kernel-pfSense... done.
*** Welcome to pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfsense ***WAN (wan) -> em0 -> v4/DHCP4: 172.73.177.151/20
v6/DHCP6: 2606:a000:dfc0:9e:ac:ad13:444f:b4bc/128
LAN (lan) -> em1 -> v4: 10.0.25.1/16
OPT1 (opt1) -> re0 ->- Logout (SSH only) 9) pfTop
- Assign Interfaces 10) Filter Logs
- Set interface(s) IP address 11) Restart webConfigurator
- Reset webConfigurator password 12) PHP shell + pfSense tools
- Reset to factory defaults 13) Update from console
- Reboot system 14) Disable Secure Shell (sshd)
- Halt system 15) Restore recent configuration
- Ping host 16) Restart PHP-FPM
- Shell
Enter an option:
Output of the log: # cat upgrade_log.txt >>> 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. >>> Unlocking package pfSense-kernel-pfSense... done. Your packages are up to date >>> Locking package pfSense-kernel-pfSense... done.
-
Welp, I just installed 2.3.3 fresh overwriting the old system and restored the backup .xml. Worked like a charm! Bravo for the backup/restore routine.
-
Welp, I just installed 2.3.3 fresh overwriting the old system and restored the backup .xml. Worked like a charm! Bravo for the backup/restore routine.
I have been able to upgrade my Fireboxes without any issues. And any new ones I have built with 2.3.2 I have been able to upgrade to 2.3.3 without any issues.