Trying to go from Eramba 3.26.6 to 3.27.0
Started the upgrade and stuck at:
Tried manually running www-data’s cronjobs and yet no progress. Not a problem, I will just roll back but I’m curious what I should have done to get it going.
On a slightly related note:
we took heed of the 3.27.0 release notes and upgraded our environment to PHP 8.4 before trying the upgrade… at which point Eramba threw a System Health Check warning and refused to let us upgrade, because 3.26.6 does not support PHP 8.4 
We forced the upgrade by using debug mode, but it was a rather silly situation.
I ran into that issue, when the Eramba Upgrade required PHP8.2, so I didn’t fall for it this time 
1 Like
I’ve experienced this a couple of times and found that if I leave it, it will eventually complete though it can sometimes take nearly two hours before the update process kicks in and starts (Obviously, Maintenance Mode will disable itself). We’re running on-premise (VM). I did noticed the update job often appears to be waiting for another queued job to complete.
I’ve raised support tickets about this, but no solution has been provided. The only consistent factor I’ve observed is that we always shut the system down and take a VM snapshot beforehand. Interestingly, when I run an upgrade without creating a snapshot, the process begins immediately, so something is causing it after it starts up.
1 Like