The upgrade went through, health status seems OK, I am just wondering about this message. Clicking on “Update” simply brings me to the updates screen saying: no upgrades available.
Is this right? Was my Upgrade successful?
Doesn’t seem to have been successful. I will now revert to a previous system snapshot and try again. Would appreciate any feedback.
Found a similar issue btw. Bug - UI issue after updating to v3.28.0 - #5 by Embezzle
Indeed, the label issue and the ‘update available’ message are the same as reported here:
As mentioned there, the issue with labels might be caused by cache or an outdated language file. (If you are using a custom PO file, you’ll need to add the new translations for the new labels)
The ‘update available’ message is a bug (Int. ref.: Jira ).
Regarding the user view not loading, could you try creating a new view manually?
thanks for the feedback.
Some more info:
Eramba Enterprise v. 3.27.3
Running on virtual machine, not the Docker installation. Health check reported everything green before the upgrade.
Currently on my second try, staring at this message:
The upgrade will begin when the scheduler (System / Settings / Crontab) picks up this task. You can refresh this page to see updates.
Tried manually running one of the cron jobs. Previously, it reported some PHP intl. issues but I fixed those. Now it reports:
sudo -u www-data bash -c 'cd /var/www/html/eramba_v2/app/upgrade && bin/cake queue run -vv'
Entity save failure. Found the following errors (server.validateCount: "Too many workers running (2/2). Check your `Queue.maxworkers` config.").
Cannot start worker: Too many workers already/still running on this server (2/2)
but there weren’t actually any running workers, at least none I could find.
I now raised maxworkers to 5 in this file: /var/www/html/eramba_v2/app/upgrade/config/app.php and triggered it:
root@eramba:/home/eramba# sudo -u www-data bash -c 'cd /var/www/html/eramba_v2/app/upgrade && bin/cake queue run -vv'
[2026-01-16 11:41:47] Looking for Job ...
Running Job of type "Queue.Execute"
Executing: `/usr/bin/php /var/www/html/eramba_v2/app/upgrade/bin/cake.php update --fetch-latest --queued`
Upgrade started now, will check and report about the user views once its done.
I refreshed the page with the update logs to see progress and was logged out.
When I log back into Eramba I see a pop-up, too quick to screenshot, but I managed to copy the text:
Class "NewApp\Services\Authorization\AuthorizationService" not found
Health Check shows all green.
Still, seem to be stuck on the previous version:
App Version
3.27.3
DB Schema Version
20251117101151
And the upgrade seems to be still running. Current logs:
Run update process
2026-01-16 11:41:53 info: Support server said we are going to update from version 3.27.3 to version: 3.28.0.
2026-01-16 11:41:53 info: Downloading update package from `https://support-v3.eramba.org/api/download/c6296aeaf6ca3e389421f5e0488c85cfe14db62f` to `/var/www/html/eramba_v2/app/upgrade/tmp/updates/update.zip`.
2026-01-16 11:42:00 info: Starting update process using package: phar:///var/www/html/eramba_v2/app/upgrade/tmp/updates/update.zip
2026-01-16 11:42:00 info: Cleanup.
2026-01-16 11:42:00 info: Datasource for this update process is set to: default
2026-01-16 11:42:00 info: Emergency rollback for database version is set to: 20251117101151
2026-01-16 11:42:00 info: Starting to validate filesystem permissions.
2026-01-16 11:42:18 debug: Profiling "validatePermissions", took 17.31449 second(s) to complete, having result: Ok.
2026-01-16 11:42:18 info: Starting to mirror all files from the update package.
2026-01-16 11:42:22 info: Copying files from the package
Finally, success: Update finished successfully, you can now disable Maintenance Mode and login into application again.
Btw. I cannot click this button, or rather nothing is happening when clicking it:
I went to the login, logged in, looks like I am on 3.28.0 now but can’t find where to disable the maintenance mode.
Seeing some stuff, not sure what is going on, looks different then before, need to figure this out myself.
Going to set this to the right connector, and see how it goes.
These 4 tabs are all empty:
I created a view, could see all users, deleted the view and was thrown here:
To be honest, this upgrade feels pretty broken. I will now revert to 3.27.3 and wait for the next minor update. Feel free to reach out if you want more information or if you have suggestions what to try next.
I will keep a snapshot of the system at this point in time so if you want me to test something, I can restore it temporarily to see if we can fix it, meanwhile I’ll stay with 3.27.3
Just done some testing myself and seeing exactly the same issues as above!!!
1 Like
@Ovidiu, interestingly where did you change ‘maxworkers to 5’ as I think this may fix an issue I have had for ages where the update won’t trigger for ages after a reboot?
/var/www/html/eramba_v2/app/upgrade/config/app.php
Perfect, thank you. I will give that a shot.
Thanks for the detailed analysis. All these label, view, and layout issues seem cache-related. We’re looking into it and will include a fix in the next hotfix.
1 Like