Normal / Expected after upgrade to 2.4 via WebGUI?
-
how long after reboot are you seeing this? check in status services to see that everything finished starting up correctly, then reload the dashboard.
-
That install / upgrade was on a USB drive, and was a test of the process / result.
Thanks so much for the input / information.
I've made a backup of my config.xml and upgrading my live / primary system as I type.
As for the timing, it was immediately following the reboot.
UPDATE: Same result from my primary installation.
If need be, I will reinstall tomorrow back to 2.3.3_p1 or do the 2.4 install from scratch / USB drive and not through the WebGUI.
Again, thanks!
Ragen -
If you're running slow hardware and you reconnect to the gui when it first becomes available after the upgrade but before it's finished booting it may still be upgrading packages in the background and it can show mixed versions.
If that is the case it should be correct once the console reaches the menu and boot is complete.Steve
-
Yeah try it again and give it a minute to boot up. Also make sure all services started successfully.
-
All services loaded. I waited about 5 minutes after boot up was complete and no change.
I am going to do the next install from a fresh memstick image.
Results to follow.
-
All is well…
![Screen Shot 2017-04-10 at 3.23.13 PM.png](/public/imported_attachments/1/Screen Shot 2017-04-10 at 3.23.13 PM.png)
![Screen Shot 2017-04-10 at 3.23.13 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-04-10 at 3.23.13 PM.png_thumb) -
Updating got the same result as the OP….
All the services were started up normally and this was an upgrade through the update manager.
![pfSense.localdomain Status Dashboard.png_thumb](/public/imported_attachments/1/pfSense.localdomain Status Dashboard.png_thumb)
![pfSense.localdomain Status Dashboard.png](/public/imported_attachments/1/pfSense.localdomain Status Dashboard.png) -
Can you try running from a ssh/console session the following commands and tell if/what error they give?:
ping -c 3 pkg.pfsense.org pkg update -f pkg unlock pfSense-kernel-pfSense pkg upgrade -f
If the above pkg commands fail with a error about some dependency required for pkg then try the same commands with pkg-static instead.
-
Sorry I can't do that now as I was not sure how that upgrade actually went, with what it was reporting. So I have just reinstalled 2.3.3 from a stick and restored the config.
-
See image.
had this happen to me as well, upgrade from 2.3.3_p1 to 2.4 via GUI is problematic for few i guess
but had more trouble…
On restore one of my packages broke libssl too. ended up re-installing & restoring from modifying config to exclude a few & it works now.