What type of hardware are you using: VPS bought online
What YunoHost version are you running: 12.0.14
What app is this about: Actual Budget
Describe your issue
The last update fails on my VPS i don’t understand why.
Hello, is that the complete log? (It seems cut off and the header does not include any key about the rsult of the script).
Yes it is the complete log.
I don’t know why it failed, after one hour without any new info on the installation screen i reloaded the webadmin and found this in the logs.
I had to manually remove the app and install the last available backup.
I have 4GO of ram with usually more than 2Go free. And 10Go of empty storage on this VPS.
Can you check if there’s another log for this failed upgrade by running ls /var/log/yunohost/operations/ | grep actual?
| 0.58K | 2025-04-19 16:52 | 20250419-165244-app_upgrade-actual.yml |
|---|---|---|
| 0.12K | 2025-04-19 16:52 | 20250419-165246-permission_url-actual.log |
| 0.33K | 2025-04-19 16:52 | 20250419-165246-permission_url-actual.yml |
| 0.12K | 2025-04-19 16:52 | 20250419-165246-user_permission_update-actual.log |
| 0.33K | 2025-04-19 16:52 | 20250419-165246-user_permission_update-actual.yml |
| 82.85K | 2025-04-19 16:56 | 20250419-165244-app_upgrade-actual.log |
| 0.01K | 2025-04-19 17:18 | .20250419-165244-app_upgrade-actual.parent.yml |
| 0.04K | 2025-04-19 17:18 | .20250419-165246-permission_url-actual.parent.yml |
| 0.04K | 2025-04-19 17:18 | .20250419-165246-user_permission_update-actual.parent.yml |
| 10.76K | 2025-04-19 17:38 | 20250419-173809-app_remove-actual.log |
| 0.77K | 2025-04-19 17:38 | 20250419-173809-app_remove-actual.yml |
| 0.07K | 2025-04-19 17:38 | 20250419-173815-permission_delete-actual.log |
| 0.30K | 2025-04-19 17:38 | 20250419-173815-permission_delete-actual.yml |
| 36.97K | 2025-04-19 17:39 | 20250419-173934-backup_restore_app-actual.log |
| 0.97K | 2025-04-19 17:39 | 20250419-173934-backup_restore_app-actual.yml |
| 0.37K | 2025-04-19 17:39 | 20250419-173934-permission_create-actual.log |
| 0.43K | 2025-04-19 17:39 | 20250419-173934-permission_create-actual.yml |
| 0.07K | 2025-04-19 17:39 | 20250419-173934-permission_url-actual.log |
| 0.33K | 2025-04-19 17:39 | 20250419-173934-permission_url-actual.yml |
| 0.13K | 2025-04-19 17:39 | 20250419-173935-permission_url-actual.log |
| 0.34K | 2025-04-19 17:39 | 20250419-173935-permission_url-actual.yml |
| 0.13K | 2025-04-19 17:39 | 20250419-173935-user_permission_update-actual.log |
| 0.34K | 2025-04-19 17:39 | 20250419-173935-user_permission_update-actual.yml |
J’ai ouvert le fichier 20250419-165244-app_upgrade-actual.log
Les logs remontés par ynh sont identiques voilà les dernières lignes, il n’y a rien après
2025-04-19 16:56:12,310: DEBUG - + export IS_GENERIC_BROWSER=1
2025-04-19 16:56:12,311: DEBUG - + ls ./bin/../public/kcab/kcab.worker.4bc35628d00550b0416b.js
2025-04-19 16:56:12,311: DEBUG - + sed s/.*kcab\.worker\.\(.*\)\.js/\1/
2025-04-19 16:56:12,317: DEBUG - + export REACT_APP_BACKEND_WORKER_HASH=4bc35628d00550b0416b
2025-04-19 16:56:12,317: DEBUG - + yarn build
2025-04-19 16:56:14,481: DEBUG - vite v5.4.8 building for production...
2025-04-19 16:56:14,558: DEBUG - transforming...
2025-04-19 16:56:49,421: DEBUG - ✓ 4661 modules transformed.
2025-04-19 16:56:53,308: DEBUG - rendering chunks...
I have 4GO of ram with usually more than 2Go free.
The build needs 850Mo : any warning about RAM when upgrading ?
zgrep -Ei "Out of memory|Killed process|oom" /var/log/{syslog*,kern.log*}
And upgrade script says NODE_OPTIONS=--max-old-space-size=3000
Maybe retry the upgrade and monitor memory usage with htop to get some more information ?
I tried this command and i do have a lot of entries but none is exactly at 16:56 when the update failed and i probably made other manipulations afterwards :
/var/log/kern.log.1:2025-04-19T16:33:58.698143+00:00 mon-serveur kernel: [ 9.276248] xen_netfront: backend supports XDP headroom
/var/log/kern.log.1:2025-04-19T17:11:31.021220+00:00 mon-serveur kernel: [ 2289.791369] php-fpm8.3 invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
/var/log/kern.log.1:2025-04-19T17:11:32.229310+00:00 mon-serveur kernel: [ 2289.846029] oom_kill_process.cold+0xb/0x10
/var/log/kern.log.1:2025-04-19T17:11:32.229442+00:00 mon-serveur kernel: [ 2290.293364] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
/var/log/kern.log.1:2025-04-19T17:11:32.229679+00:00 mon-serveur kernel: [ 2291.136560] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/yunohost-api.service,task=node,pid=5270,uid=990
/var/log/kern.log.1:2025-04-19T17:11:32.229680+00:00 mon-serveur kernel: [ 2291.153172] Out of memory: Killed process 5270 (node) total-vm:24368632kB, anon-rss:1772964kB, file-rss:320kB, shmem-rss:0kB, UID:990 pgtables:46660kB oom_score_adj:0
I tried multiple times over the last few days but even the manual backup failed (probably because the new backup created was flawed).
I tried uninstalling and installing again the app fresh from the yunohost catalog and it failled exactly the same way.
This morning i was finaly able to install it successfully after :
- Uninstalling the failed app and checking the
Delete the data directory associated with the application - Upgrading temporarily to a higher tier VPS : 4 CPUs / 8 GB RAM / 30,00 € each month
I don’t know what was the problem between those changes but I always have more than 1,5go of free ram even with my normal 4GB configuration so i don’t think it was Ram. Here is a screenshot of monitoring during this fresh install and it used more than 80% of this higher grade CPU during this fresh install.
I hope i won’t have such problems for the next update and i will keep doing regularly some Zip export of the database.
Thanks for your time and advices.
Update with the 25.5.0 release :
- I have the exact same issue as with the previous update. It fails at the end of the installation without any error message. I reinstalled the backup and i will skip this update for now.
Hi,
I think I have the same issue. I wrote a ticket on github : Unable to install actual package · Issue #73 · YunoHost-Apps/actual_ynh · GitHub.
Thank you for this thread, since I had no idea where to look for the problem.
IMHO the build step should not be done on YunoHost instances. The package should contains already build assets.
I’ll try to propose something like that in a (I hope) near future.
1 Like
I guess installation process could be changed again since in 25.5.0 we can now install without building.
Will take a look at CLI tool | Actual Budget Documentation in the next few days.
2 Likes