My YunoHost server
Hardware: Hetzner virtual server
YunoHost version: 4.3.6.2
I have access to my server : Through SSH and through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
Description of my issue
I tried to update Wekan through the update system page. The update failed as some files are missing like the .bashrc. I have not tweaked the system.
Here is the yunopaste logs: https://paste.yunohost.org/raw/bonudefoxo
Here are some log messages from the system:
wekan wird jetzt aktualisiert...
Loading installation settings...
Checking version...
Backing up the app before upgrading (may take a while)...
Stopping a systemd service...
Ensuring downward compatibility...
Managing upgrade from previous version...
Making sure dedicated system user exists...
Upgrading source files...
Upgrading NGINX web server configuration...
Upgrading dependencies...
sed: can't read /root/.bashrc: No such file or directory
[Error] Upgrade failed.
Created symlink /run/systemd/system/avahi-daemon.service -> /dev/null.
Removed /run/systemd/system/avahi-daemon.service.
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-4.19.0-16-amd64
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.19.0-18-amd64
Found initrd image: /boot/initrd.img-4.19.0-18-amd64
Found linux image: /boot/vmlinuz-4.19.0-17-amd64
Found initrd image: /boot/initrd.img-4.19.0-17-amd64
Found linux image: /boot/vmlinuz-4.19.0-13-amd64
Found initrd image: /boot/initrd.img-4.19.0-13-amd64
done
rmdir: failed to remove '/var/run/avahi-daemon': Directory not empty
sed: can't read /opt/node_n/ynh_app_version: No such file or directory
grep: /opt/node_n/ynh_app_version: No such file or directory
/usr/share/yunohost/helpers.d/nodejs: line 198: /opt/node_n/bin/n: No such file or directory
sed: can't read /root/.bashrc: No such file or directory
148931 (this may take some time)
421564 The service wekan didn't fully executed the action start before the timeout.
421582 Please find here an extract of the end of the log of the service wekan:
422379 Jan 22 18:00:10 wekan[29064]: [INFO] Disconecting
422379 Jan 22 18:23:09 systemd[1]: Stopping Wekan, task board...
422379 Jan 22 18:23:09 systemd[1]: wekan.service: Main process exited, code=killed, status=15/TERM
422379 Jan 22 18:23:09 systemd[1]: wekan.service: Succeeded.
422380 Jan 22 18:23:09 systemd[1]: Stopped Wekan, task board.
422380 Jan 22 18:27:32 systemd[1]: Started Wekan, task board.
422382 Jan 22 18:27:39 wekan[5077]: Note: you are using a pure-JavaScript implementation of bcrypt.
422383 Jan 22 18:27:39 wekan[5077]: While this implementation will work correctly, it is known to be
422383 Jan 22 18:27:39 wekan[5077]: approximately three times slower than the native implementation.
422383 Jan 22 18:27:39 wekan[5077]: In order to use the native implementation instead, run
422384 Jan 22 18:27:39 wekan[5077]: meteor npm install --save bcrypt
422384 Jan 22 18:27:39 wekan[5077]: in the root directory of your application. You may also need to
422384 Jan 22 18:27:39 wekan[5077]: install build tools to compile bcrypt. For more information see:
422384 Jan 22 18:27:39 wekan[5077]: https://github.com/nodejs/node-gyp#installation
422385 Jan 22 18:27:41 wekan[5077]: Presence started serverId=iJdPCnge5CTRvDkDY
422385 Jan 22 18:27:47 wekan[5077]: [INFO] Enabling LDAP Background Sync
422385 Jan 22 18:27:47 wekan[5077]: {"line":"87","file":"percolate_synced-cron.js","message":"SyncedCron: Scheduled \"LDAP_Sync\" next run @Sat Jan 22 2022 19:00:00 GMT+0100 (Central European Standard Time)","time":{"$date":1642872467930},"level":"info"}
422386 Jan 22 18:27:48 wekan[5077]: {"line":"87","file":"percolate_synced-cron.js","message":"SyncedCron: Scheduled \"notification_cleanup\" next run @Sat Jan 22 2022 18:27:47 GMT+0100 (Central European Standard Time)","time":{"$date":1642872468192},"level":"info"}
422386 Jan 22 18:27:48 wekan[5077]: {"line":"87","file":"percolate_synced-cron.js","message":"SyncedCron: Scheduled \"LDAP_Sync\" next run @Sat Jan 22 2022 19:00:00 GMT+0100 (Central European Standard Time)","time":{"$date":1642872468195},"level":"info"}
422386 Jan 22 18:27:48 wekan[5077]: {"line":"87","file":"percolate_synced-cron.js","message":"SyncedCron: Scheduled \"notification_cleanup\" next run @Sat Jan 22 2022 18:27:48 GMT+0100 (Central European Standard Time)","time":{"$date":1642872468197},"level":"info"}
The app was restored to the way it was before the failed upgrade.
wekan konnte nicht aktualisiert werden: Es ist ein Fehler im App-Upgrade-Skript aufgetreten
Der Vorgang konnte nicht abgeschlossen werden 'Upgrade der Applikation 'wekan''. Bitte gib das vollständige Protokoll dieser Operation mit Klicken Sie hier an, um Hilfe zu erhalten
Packagers /!\ This app manually modified some system configuration files! This should not happen! If you need to do so, you should implement a proper conf_regen hook. Those configuration were affected:
- /etc/nsswitch.conf
What can I do to fix it?
Thanks for any help