Upgrade 2.3.5 to 2.4.3 ... crash report

[johnpoz]

Not sure that looks like a router.. This is what your talking about right jimp.. The image upload - look more like cloud with arrow ;)

[jimp]

@johnpoz said in Upgrade 2.3.5 to 2.4.3 ... crash report:

Not sure that looks like a router.. This is what your talking about right jimp.. The image upload - look more like cloud with arrow ;)

There should be one more to the right of that

[ColinJack]

@johnpoz
I stop at the cloud too. Pasted as code.

[johnpoz]

Im not seeing that one either.

[jimp]

Refresh the page and see if it's there now.

[johnpoz]

Yup there now!

[ColinJack]

Yay!
0_1528475927053_upgrade_log.latest.txt

[johnpoz]

Well your pain @ColinJack got us the ability to upload files -- so thanks ;) Guessing that was overlooked in the upgrade.

[jimp]

@colinjack said in Upgrade 2.3.5 to 2.4.3 ... crash report:

Yay!
0_1528475927053_upgrade_log.latest.txt

Strange, that looks to me like everything succeeded

[jimp]

@johnpoz said in Upgrade 2.3.5 to 2.4.3 ... crash report:

Well your pain @ColinJack got us the ability to upload files -- so thanks ;) Guessing that was overlooked in the upgrade.

Yes uploads were enabled under Settings > Uploads, but they were not enabled in the global privileges list under Manage > Privileges.

[ColinJack]

@jimp At least something came out of me being a pain! ;)

[johnpoz]

Yeah stuff like that for sure to happen in such a massive change.. No biggy all the kinks will get worked out I am sure.. Its clearly FASTER than the old forum...

[ColinJack]

@jimp That is what it looked like to my untrained eye.
Boots okay but just this constant message ...
PHP Errors:
[07-Jun-2018 18:48:48 Europe/London] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/rrd.so' - Shared object "librrd.so.8" not found, required by "rrd.so" in Unknown on line 0

[jimp]

It's probably something we could hammer on and solve with enough time but at this point it's easier to reinstall 2.4.3 in place and have it recover the configuration.

If this is real hardware and not a VM, I might also suspect an SSD failure where it's flipped the disk into a read only mode to preserve the data.

[ColinJack]

Its a VM ... so looks like I will have to ask the datacentre boys if they can do something.
No doubt there will be a few others that will hit this.
Worth trying your blunderbuss approach do you think?
'You might be able to force an update of everything with something like pkg unlock pfSense-kernel-pfSense; pkg upgrade -f.'

[johnpoz]

Can they not just roll it back from the snap they should of taken before you went to upgrade it.. And then try again.

[jimp]

You can give that a try if you want as a last ditch effort. I'd still have the DC crew ready in case that blows up. It shouldn't, but it's still possible.

[ColinJack]

@johnpoz That would roll it back to 2.3.5 ... I would rather be on 2.4.3.
It is a fallback though.

[ColinJack]

I have asked the DC crew to build a new one.
As the broken one is still functioning it can be left running until they are ready to change, so should be minimal downtime.

Really appreciate all the time and effort you have put into trying to help me fix this.
Hopefully you will track down what happened in case some other poor soul manages to break their firewall!

Many thanks @jimp.

[johnpoz]

No just to try the upgrade again is all.