Upgrade to 2.5.0 failing to startup
-
The libraries exist, but cant seem to be loaded for some reason
-
4.5.0 ?
Reading pictures in post stamp size is not possible...-Rico
-
@Rico Fixed them. sorry apparently imgur sets them microscopic if not parameterized
-
I'd just reinstall 2.5.0 with the recover config.xml Option.
Or reinstall 2.5.0 an recover your config.xml via WebGUI.-Rico
-
webgui not available as it doesnt even want to give out ip addresses, nor obtain any from the ISP
-
Looks like it didn't upgrade completely, or some part of it failed. Look in
/conf/upgrade_log.latest.txtand/conf/upgrade_log.txtto see if they have any clues.To recover:
dhclient xx0wherexx0is your WAN interfaceThen
pfSense-upgrade -dyand let it complete the process.Might be similar to what someone else hit here: https://redmine.pfsense.org/issues/9431
-
@jimp said in Upgrade to 2.5.0 failing to startup:
Looks like it didn't upgrade completely, or some part of it failed. Look in
/conf/upgrade_log.latest.txtand/conf/upgrade_log.txtto see if they have any clues.To recover:
dhclient xx0wherexx0is your WAN interfaceThen
pfSense-upgrade -dyand let it complete the process.Might be similar to what someone else hit here: https://redmine.pfsense.org/issues/9431
pkg delete pfSense-pkg-\*Then continueing upgrade
via:pfSense-upgrade -dy
seems to get me further and into a working state...I didnt have aws installed though. Only openvpn and pfBlocker-NG -
If you read the thread linked from the issue above, the aws package didn't appear to be required by anything, which is part of the issue. It decided mid-upgrade that it was necessary for some as-yet-undiscovered reason and failed.
Without the console output or upgrade log from the first post-upgrade reboot it's difficult to say what might have happened in your case.
