Hi @Bumble
2025-09-28 19:45:34,850: DEBUG - installing : node-v22.20.0
2025-09-28 19:45:35,166: DEBUG - mkdir : /opt/node_n/n/versions/node/22.20.0
2025-09-28 19:45:35,182: DEBUG - fetch : https://nodejs.org/dist/v22.20.0/node-v22.20.0-linux-x64.tar.xz
2025-09-28 19:45:38,895: DEBUG - copying : node/22.20.0
2025-09-28 19:45:39,537: DEBUG - installed : v22.20.0
(...)
2025-09-28 19:59:12,520: WARNING - Sep 28 19:54:12 (node)[97636]: mastodon-streaming.service: Failed to locate executable /opt/node_n/n/versions/node/22.19.0/bin/node: No such file or directory
2025-09-28 19:59:12,521: WARNING - Sep 28 19:54:12 (node)[97636]: mastodon-streaming.service: Failed at step EXEC spawning /opt/node_n/n/versions/node/22.19.0/bin/node: No such file or directory
What does ls /opt/node_n/n/versions/node/ return ?
The backup wants to restart Mastodon using a systemd service file that points to Node.js version 22.19, while the same backup has installed version 22.20. A similar issue is mentioned here:
The proposed solution by @fflorent is, first to keep a backup, and then to manually install the version required by systemd and then restart the backup but there was no feedback from the user who faced this problem.
In your case :
N_PREFIX=/opt/node_n/ /usr/share/yunohost/helpers.v2.1.d/vendor/n/n install 22.19