2.4.5 -> 2.5.2: PHP-related update issue

pwest

Hi:
Today, I attempted to update my MBT-4220 via the web interface from 2.4.5 to 2.5.2. The update progress on the web dialog appeared to go smoothly until it rebooted. Although I may not have waited long enough (10 mins?), the firewall never re-connected to the web interface. Eventually, I powered the box down and then back up. All firewall functionality that I've checked has returned except the web interface. I hooked up a keyboard and screen to the box and can access the shell, system logs, etc.

In the middle of the list of numbered options ( 0) logout ...16) Restart PHP-FPM) I see this:

Warning PHP Startup: Unable to load dynamic library 'rrd.so" (tried ... [stuff omitted] )

Looking through /cf/conf/upgrade_log.latest there seem to be a few stages where php packages get updatet from e.g. 7.2.10 to 7.2.29, but after:

Extracting php72-pear-Net_Socket-1.0.14: .... done

I see:

Warning: PHP Startup Unable to load dynamic library 'readline.so'

followed by some more warnings and then

install ok: channel://pear.php.net/Net_Socket-1.0.14

Similar errors show up a couple of times later. So, it looks like I may have a fairly complete 2.5.2 install with little or no PHP. How might I proceed to attempt to fix this?

Thanks for any ideas,
Phil

SteveITS

@pwest said in 2.4.5 -> 2.5.2: PHP-related update issue:

I may not have waited long enough (10 mins?)

Not familiar with that model but on a 2100 or 3100 I know I try to allow 15 minutes before even starting to worry. Then I just wait longer. They don't have super fast storage. The upgrade counter page timer still starts at 90 seconds but that's almost laughable on lower end hardware.

Regardless, if you are on 2.5.2 the easiest thing would probably be to reinstall, and restore your backup config file.

pwest

Thanks for that input @steveits--that may be my best option.

I didn't post my install log earlier because I had some ssh/firewall configuration issues which I've now resolved. My /cf/conf/upgrade_log.latest.txt file is now attached.
upgrade_log.latest.txt
-Phil

pwest

@steveits said in 2.4.5 -> 2.5.2: PHP-related update issue:

Regardless, if you are on 2.5.2 the easiest thing would probably be to reinstall, and restore your backup config file.

I'm going to try have to get this fixed this weekend. Is it really as simple as doing a clean install and then overwriting the config file with what I have now?

I'm thinking about various things like NUT (I never want to have to reconfigure NUT), dynDNS, DNSblock (with lots of exceptions), openVPN, certificate management, and all the stuff that I had working but had largely forgotten about. Are all those things fully configured in the one config file? Or are there other databases, config files, and certificates lurking around?

Thanks for any additional guidance,
Phil

SteveITS

@pwest all in the config file. :)