Umami won't start nor update

geoma · October 14, 2026, 2:00pm

I have searched the forum for similar issues

on

This category is for issues regarding specific apps, NOT general issues with YunoHost.

on

This form is written in English but feel free to write in French if you’re more comfortable!

on

What app is this about, and its version

Umami 3.3.1~ynh2

What YunoHost version are you running

yunohost_version: 12.1.41.2

What type of hardware are you using

Other(?)

Describe your issue

I recently had this trouble and it got fixed but I got it again:

Umami can’t be updated nor service started.

Share relevant logs or error messages

upgrade log:
https://paste.yunohost.org/raw/lotiropiwu

service log:

orhtej2 · October 14, 2026, 7:41pm

That’s the end of the log? Try (force) upgrading again perhaps?

geoma · October 22, 2026, 5:02pm

here’s what happened when I tried force upgrade:

root@eticadigital:~# yunohost app upgrade -F umami
==========
This release contains some security strengthening, namely ability to turn on 2FA. After the upgrade you may be prompted to log in again due to change of seed used for encrypting the session cookies.
==========
INFO Now upgrading umami…
INFO Creating a safety backup prior to the upgrade
INFO Collecting files to be backed up for umami…
INFO Declaring files to be backed up...
INFO Backing up the database...
WARNING could not change directory to "/home/yunohost.backup/tmp/umami-pre-upgrade2/apps/umami/backup": Permission denied
INFO Backup script completed for umami. (YunoHost will then actually copy those files to the archive).
INFO Creating a backup archive from the collected files…
INFO The archive will contain about 1.7GB of data.
SUCCESS Backup created: umami-pre-upgrade2
INFO Backup umami-pre-upgrade1 was deleted because it is replaced by a newer backup umami-pre-upgrade2
INFO '/etc/php/*/fpm/pool.d/monitorix_status.conf' wasn't deleted because it doesn't exist.
INFO Updating sources...
INFO Updating system_user...
INFO Updating install_dir...
INFO Updating permissions...
INFO Updating ports...
INFO Updating apt...
INFO Updating database...
INFO Updating nodejs...
INFO [++..................] > Stopping umami's systemd service...
INFO [##+++...............] > Ensuring downward compatibility...
INFO [#####+++............] > Provisioning pgcrypto...
WARNING NOTICE:  extension "pgcrypto" already exists, skipping
INFO [########+++.........] > Upgrading system configurations related to umami...
INFO [###########+++......] > Configuring and building the app...
INFO '/var/www/umami/release' wasn't deleted because it doesn't exist.
Read from remote host eticadigital.eu: Connection reset by peer
Connection to eticadigital.eu closed.
client_loop: send disconnect: Broken pipe

here is the full log

https://paste.yunohost.org/raw/niqajudoci

orhtej2 · October 22, 2026, 8:59pm

And it’s not up and running?

geoma · October 26, 2026, 1:29am

nope.

And here is the service log (it won’t start)

jarod5001 · October 26, 2026, 5:47pm

Can you share the output of ls /opt/node_n/n/versions/node ?

geoma · October 26, 2026, 5:55pm

14 16 16.20.2 18 18.20.8 20 22 22.22.0 22.22.2 22.23.4 24 24.19.0 24.20.0 24.21.0 24.22.1

jarod5001 · October 26, 2026, 6:17pm

In your logs /opt/node_n/n/versions/node/22.23.4/bin/node: No such file or directory
Can you check it?

geoma · October 26, 2026, 7:20pm

/opt/node_n/n/versions/node/22.23.4/bin# ls
corepack  node npm  npx  pnpm pnpx  yarn  yarnpkg



/opt/node_n/n/versions/node/22.23.4/bin# ls -la 
total 121984 
drwxr-xr-x 2 root root      4096 Oct 22 13:50 . 
drwxr-xr-x 6 root root      4096 Oct 21 12:21 .. 
lrwxrwxrwx 1 root root        45 Oct 22 13:50 corepack -> ../lib/node_modules/corepack/dist/corepack.js 
-rwxr-xr-x 1 root root 124902584 Oct 20 16:57 node 
lrwxrwxrwx 1 root root        38 Oct 20 16:57 npm -> ../lib/node_modules/npm/bin/npm-cli.js 
lrwxrwxrwx 1 root root        38 Oct 20 16:57 npx -> ../lib/node_modules/npm/bin/npx-cli.js 
lrwxrwxrwx 1 root root        41 Oct 22 13:50 pnpm -> ../lib/node_modules/corepack/dist/pnpm.js 
lrwxrwxrwx 1 root root        41 Oct 22 13:50 pnpx -> ../lib/node_modules/corepack/dist/pnpx.js 
lrwxrwxrwx 1 root root        41 Oct 22 13:50 yarn -> ../lib/node_modules/corepack/dist/yarn.js 
lrwxrwxrwx 1 root root        44 Oct 22 13:50 yarnpkg -> ../lib/node_modules/corepack/dist/yarnpkg.js

jarod5001 · October 26, 2026, 10:29pm

systemctl restart umami then systemctl status umami

geoma · October 27, 2026, 12:15am

```

×umami.service - Umami: Web Analytics
Loaded: loaded (/etc/systemd/system/umami.service;enabled; preset: enabled)
Active:failed(Result: exit-code) since Mon 2026-10-26 21:15:01 -03; 816ms ago
Duration: 38ms
Process: 709712 ExecStart=/opt/node_n/n/versions/node/22.23.4/bin/node server.js(code=exited, status=200/CHDIR)
Main PID: 709712 (code=exited, status=200/CHDIR)
CPU: 36ms

Oct 26 21:15:01 eticadigital.eu systemd[1]: Started umami.service - Umami: Web Analytics.
Oct 26 21:15:01 eticadigital.eu (node)[709712]: umami.service: Changing to the requested working directory failed: No such file or directory
Oct 26 21:15:01 eticadigital.eu (node)[709712]: umami.service: Failed at step CHDIR spawning /opt/node_n/n/versions/node/22.23.4/bin/node: No such file or directory
Oct 26 21:15:01 eticadigital.eu systemd[1]: umami.service: Main process exited, code=exited, status=200/CHDIR
Oct 26 21:15:01 eticadigital.eu systemd[1]: umami.service: Failed with result ‘exit-code’.
```

jarod5001 · October 27, 2026, 1:18am

cat /etc/systemd/system/umami. service

Try running manually and see if there are other errors

yunohost app shell umami
/opt/node_n/n/versions/node/22.23.4/bin/node server.js

geoma · October 27, 2026, 1:53am

cat /etc/systemd/system/umami.service 

[Unit] 
Description=Umami: Web Analytics 
After=network.target 
 
[Service] 
Type=simple 
User=umami 
Group=umami 
WorkingDirectory=/var/www/umami/release 
Environment=NODE_ENV=production 
Environment="PATH=/opt/node_n/n/versions/node/22.23.4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" 
Environment=NEXT_TELEMETRY_DISABLED=1 
Environment=PORT=37111 
ExecStart=/opt/node_n/n/versions/node/22.23.4/bin/node server.js 
 
# Sandboxing options to harden security 
# Details for these options:  
NoNewPrivileges=yes 
PrivateTmp=yes 
PrivateDevices=yes 
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6 AF_NETLINK 
RestrictNamespaces=yes 
RestrictRealtime=yes 
DevicePolicy=closed 
ProtectClock=yes 
ProtectHostname=yes 
ProtectProc=invisible 
ProtectSystem=full 
ProtectControlGroups=yes 
ProtectKernelModules=yes 
ProtectKernelTunables=yes 
LockPersonality=yes 
SystemCallArchitectures=native 
SystemCallFilter=~@clock @debug @module @mount @obsolete @reboot @setuid @swap @cpu-emulation @privileged 
 
# Denying access to capabilities that should not be relevant for webapps 
# Doc:  
CapabilityBoundingSet=~CAP_RAWIO CAP_MKNOD 
CapabilityBoundingSet=~CAP_AUDIT_CONTROL CAP_AUDIT_READ CAP_AUDIT_WRITE 
CapabilityBoundingSet=~CAP_SYS_BOOT CAP_SYS_TIME CAP_SYS_MODULE CAP_SYS_PACCT 
CapabilityBoundingSet=~CAP_LEASE CAP_LINUX_IMMUTABLE CAP_IPC_LOCK 
CapabilityBoundingSet=~CAP_BLOCK_SUSPEND CAP_WAKE_ALARM 
CapabilityBoundingSet=~CAP_SYS_TTY_CONFIG 
CapabilityBoundingSet=~CAP_MAC_ADMIN CAP_MAC_OVERRIDE 
CapabilityBoundingSet=~CAP_NET_ADMIN CAP_NET_BROADCAST CAP_NET_RAW 
CapabilityBoundingSet=~CAP_SYS_ADMIN CAP_SYS_PTRACE CAP_SYSLOG 
 
[Install] 
WantedBy=multi-user.target

yunohost app shell umami

/usr/share/yunohost/helpers.v2.1.d/0-utils: line 501: cd: /var/www/umami/release: No such file or directory

/opt/node_n/n/versions/node/22.23.4/bin/node server.js

node:internal/modules/cjs/loader:1433
  throw err;
  ^

Error: Cannot find module '/root/server.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1430:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1040:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1045:22)
    at Function._load (node:internal/modules/cjs/loader:1216:25)
    at wrapModuleLoad (node:internal/modules/cjs/loader:254:19)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.23.4

orhtej2 · October 27, 2026, 8:12am

That’s peculiar the app directory is missing.

Can you try force-upgrading the app? Especially now that a new version came out?

geoma · October 27, 2026, 12:53pm

won’t upgrade nor start

yunohost app upgrade -F umami 
========== 
This release contains some security strengthening, namely ability to turn on 2FA. After the upgrade you may be prompted to log in again due to change of seed used for encrypting the
 session cookies. 
========== 
**INFO** Now upgrading umami… 
**INFO** Creating a safety backup prior to the upgrade 
**INFO** Collecting files to be backed up for umami… 
**INFO** Declaring files to be backed up... 
**INFO** Backing up the database... 
**WARNING** could not change directory to "/home/yunohost.backup/tmp/umami-pre-upgrade1/apps/umami/backup": Permission denied 
**INFO** Backup script completed for umami. (YunoHost will then actually copy those files to the archive). 
**INFO** Creating a backup archive from the collected files… 
**INFO** The archive will contain about 1.7GB of data. 
**SUCCESS** Backup created: umami-pre-upgrade1 
**INFO** Backup umami-pre-upgrade2 was deleted because it is replaced by a newer backup umami-pre-upgrade1 
**INFO** Updating sources... 
**INFO** Updating system_user... 
**INFO** Updating install_dir... 
**INFO** Updating permissions... 
**INFO** Updating ports... 
**INFO** Updating apt... 
**INFO** Updating database... 
**INFO** Updating nodejs... 
**INFO** \[++..................\] > Stopping umami's systemd service... 
**INFO** \[##+++...............\] > Ensuring downward compatibility... 
**INFO** \[#####+++............\] > Provisioning pgcrypto... 
**WARNING** NOTICE:  extension "pgcrypto" already exists, skipping 
**INFO** \[########+++.........\] > Upgrading system configurations related to umami... 
**INFO** \[###########+++......\] > Configuring and building the app... 
**INFO** '/var/www/umami/release' wasn't deleted because it doesn't exist.

orhtej2 · October 27, 2026, 12:56pm

I mean this log is incomplete (it concludes in neither success nor failure), if the operation is done can you share the full debug log?

jarod5001 · October 27, 2026, 2:10pm

It would be interesting to see if umami folder exists in /var/www
And the full log.
What hardware is it? Specs? Swap?

geoma · October 27, 2026, 3:10pm

sorry
here is the full log
https://paste.yunohost.org/raw/jiceyunojo

geoma · October 27, 2026, 3:17pm

ls /var/www/umami
build

cat /proc/swaps  
Filename                                Type            Size            Used            Priority 
/swap_drupal                            file            524284          524284          -2 
/dev/nvme0n1p3                          partition       999420          999420          -3

it is a mini pc.

CPU: 6-core AMD Ryzen 5 5500U with Radeon Graphics (-MT MCP-) speed/min/max: 1458/1400/4056 MHz
Kernel: 6.1.0-53-amd64 x86_64 Up: 13d 36m Mem: 11581.4/12869.1 MiB (90.0%)
Storage: 476.94 GiB (73.9% used) Procs: 384 Shell: Bash inxi: 3.3.26

orhtej2 · October 27, 2026, 9:18pm

Such a truncated log would indicate that either the operation was interrupted (try running upgrade under screen perhaps?) or the process was killed by OOM killer?

Is there any output of sudo journalctl -k | grep -i "oom|killed process" perhaps?

The specs seem more than adequate for building Umami - I’ve built it on old 2 core Xeon with 2GB RAM + 4GB swap no problem (although it takes ages).