PHP errors after upgrade to 23.09: "libicuio.so.72" not found

DominikHoffmann

I don’t have physical access nor ssh access to the real command line, the latter presumably, because sshd is in limbo, somehow.

I will try pkg-static upgrade from Diagnostics → Command Prompt → Execute Shell Command.

stephenw10

You will need to use pkg-static upgrade -y at the gui command prompt because it's non-interactive.

Do you know if it rebooted after the initial failed upgrade?

DominikHoffmann

@stephenw10

The output of pkg-static upgrade contains the line The process will require 386 MiB more space. Does that point to the source of the problem?

DominikHoffmann

@stephenw10

I am not entirely sure that it rebooted. I have notifications via email enabled on the system, and received the notification that the system was going to go down for the update. However, I never did receive the notification that the reboot was complete.

I just tried rebooting it from Diagnostics → Reboot. After that, when I got the WebConfigurator login prompt again, I looked at the uptime: 21:24 h. It did not reboot.

I think, I need to get physical access and reboot the unit from the console.

stephenw10

@DominikHoffmann said in PHP errors after upgrade to 23.09: "libicuio.so.72" not found:

The output of pkg-static upgrade contains the line The process will require 386 MiB more space. Does that point to the source of the problem?

No, that's just telling you how much additional space it will require.

Check the uptime on the dashboard. That will tell you when it last rebooted.

It's possible it simply never rebooted after the first part of the upgrade. There's probably a reason for that though if it's the case.

Is it running ZFS? If so you can always roll back but that requires some local access.

DominikHoffmann

@stephenw10 Yes, it is running ZFS.

stephenw10

What about the uptime? Does it look like it rebooted?

DominikHoffmann

Doing pkg-static upgrade -y at Diagnostics → Command Prompt → Execute Shell Command updated the packages correctly. I then forced a reboot at Diagnostics → Reboot. Uptime is now in the minutes range. This seems to have worked. Making an ssh connection to the router works, too. It looks like all is good.

stephenw10

Ah, excellent!

DominikHoffmann

@stephenw10 Thanks so much, Stephen, for your excellent help!