2.6.x to 2.7.0beta upgrade saga

rcfa

Had exactly the same issue on two of two systems...
Steps:

backup
switch to new branch (which interestingly was displayed differently on the two systems)
start upgrade, system reboots, and Web-GUI never comes back.
login via ssh, notice it's not the usual menu system, but you get dumped directly onto the shell. Some things work, some don't, certainly not IPSec and the web UI
go to /cf/conf/ and check out the upgrade_log.latest.txt file there. Notice that a bunch of error messages are in there about modules from /usr/local/lib/php/20170718 and /usr/local/lib/20190902 can't be loaded, since they aren't found, but notice that /usr/local/lib/php/20220829 exists.
make an educated guess, and make symlinks pointing 20170718 and 20190902 at 20220829
cross fingers and reboot
ta-dah, web UI is back and system seems to run normal
to be sure no bad voodoo is going on, reinstall all packages from the backup/restore page
delete the symlinks
reboot

MAYBE just a reboot would have worked, I didn't test that, after the above procedure worked on the 1st system, I simply repeated it on the 2nd after the regular upgrade process had the same failure mode there. Wasn't in the mood to experiment and potentially lock myself out from a remote system...

I'm actually a bit surprised: with a two out of two hit rate, I'd suspect this affecting more than just my setup, especially since I use two different hardware platforms (old Dell server and a Minnowboard), but I didn't find a corresponding bug report, so here it goes...

Not sure if that would help, but it seems dated folders without a "latest" symlink that is referenced in configuration/script files, seems just asking for such types of failures.

stephenw10

Hmm, never hit that here.

Were you running packages? Any packages common between the two systems?

rcfa

@stephenw10 Yes, a bunch of packages, and they are both the same on both systems.

Upgrade from 2,7.0-beta to 2.7.0-rc went smoothly on one system.
On the other there was an issue due to cable modem dropping packets like mad (which I hadn't noticed), and so the upgrade stalled. But I got that fixed now, too, and in any case, that's not really a bug in pfSense.

As for installed packages: ALL available EXCEPT:
apcupsd
frr
haproxy-devel
LCDproc
Netgate_Firmware_Upgrade
node_exporter
nrpe
Open-VM-Tools
pfBlockerNG-devel
pimd
suricata
syslog-ng
zabbix-*

stephenw10

Hmm, I know FRR had a bug in the uninstall script that might have triggered this at one time. I had thought that was fixed though.
That would be my guess without seeing the logs.

rcfa

@stephenw10

I wrote ALL packages EXCEPT those listed, so frr can't be the culprit.

~~Where can I submit the log file?~~

upgrade_log.latest.txt

stephenw10

Oh! Ha. In that case almost certainly Squid.