I gave a try to nextcloud on a raspberry pi 4B I wasn’t using (I installed freedombox with the installer on an external USB SSD).
It usually works, but it happened twice that it wasn’t working, and on the nextclould page in plinth, there was an indication that it was inactivate. After disabling and re-enabling it from that page, it was working again.
Is it something that happens for others too? I wonder whether it happens after some kind of update, and the app fails to start again.
This just happened again.
It occasionally also happens on mine. Haven’t found a pattern at all. I am running diagnosis and repair to have it running again. Last time this happened some weeks ago.
I only disable and re-enable it, then it works.
It just happened again.
Noticed this in the journal today (it is repeating), which was not in the journal yesterday:
mars 15 06:25:35 freedombox systemd[1]: Starting nextcloud-cron-freedombox.service - Nextcloud cron.php job...
mars 15 06:25:35 freedombox podman[19107]: Error: no container with name or ID "nextcloud-freedombox" found: no such container
mars 15 06:25:35 freedombox systemd[1]: var-lib-containers-storage-overlay.mount: Deactivated successfully.
mars 15 06:25:35 freedombox systemd[1]: nextcloud-cron-freedombox.service: Skipped due to 'exec-condition'.
mars 15 06:25:35 freedombox systemd[1]: Condition check resulted in nextcloud-cron-freedombox.service - Nextcloud cron.php jo>
$ sudo journalctl --no-pager | grep "no container" | grep "^[a-z]" | cut -d" " -f1-2 | sort | uniq -c
5 nov. 07
38 nov. 08
206 nov. 16
24 nov. 17
103 janv. 03
35 janv. 11
12 janv. 29
53 mars 15
Notes:
I did not write down each time nextcloud was off, but looking back at my messages on the forum, it looks like the above message could happen exactly when nextcloud is no more running.
I can provide the full journal for investigation if useful.
EDIT: Corrected the command above.
I also noticed this issue this morning. It happened after a number of packages were upgraded (due to Debian stable point release):
2026-03-15 06:32:19,218 INFO Starting unattended upgrades script
2026-03-15 06:32:19,219 INFO Allowed origins are: origin=Debian,codename=trixie,label=Debian, origin=Debian,codename=trixie,label=Debian-Security, origin=Debian,codename=trixie-security,label=Debian-Security, origin=Debian,codename=trixie-updates, o=Debian Backports,n=trixie-backports,l=Debian Backports
2026-03-15 06:32:19,219 INFO Initial blacklist:
2026-03-15 06:32:19,219 INFO Initial whitelist (not strict):
2026-03-15 06:32:51,685 INFO Packages that will be upgraded: apache2 apache2-bin apache2-data apache2-utils augeas-lenses augeas-tools base-files bash catatonit dirmngr dpkg e2fsprogs ejabberd erlang-asn1 erlang-base erlang-crypto erlang-dialyzer erlang-eunit erlang-inets erlang-mnesia erlang-odbc erlang-os-mon erlang-public-key erlang-runtime-tools erlang-ssl erlang-syntax-tools erlang-tools erlang-xmerl gnupg-utils gpg gpg-agent gpg-wks-client gpgconf gpgsm gpgv grub-common grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub-efi-amd64-unsigned grub2-common ifupdown libaugeas0 libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libcap2 libcap2-bin libcom-err2 libext2fs2t64 libldb2 libmariadb3 libmpg123-0t64 libpq5 libsndfile1 libsqlite3-0 libss2 libssl3t64 libtalloc2 libtdb1 libtevent0t64 libwbclient0 linux-base linux-sysctl-defaults locales locales-all logsave mariadb-client mariadb-client-core mariadb-common mariadb-plugin-provider-bzip2 mariadb-plugin-provider-lz4 mariadb-plugin-provider-lzma mariadb-plugin-provider-lzo mariadb-plugin-provider-snappy mariadb-server mariadb-server-compat mariadb-server-core nscd openssh-client openssh-server openssh-sftp-server openssl openssl-provider-legacy passt postgresql-17 postgresql-client-17 python3-cryptography python3-fonttools python3-jaraco.context python3-ldb python3-requests python3-samba python3-talloc python3-tdb samba samba-common samba-common-bin samba-libs sudo tdb-tools tzdata wireless-regdb
2026-03-15 06:32:51,685 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2026-03-15 06:38:10,173 INFO All upgrades installed
During these upgrades, plinth.service was restarted twice, and freedombox-privileged.service was restarted over 20 times.
The “no such container” error appeared in the logs until I disabled and re-enabled the Nextcloud app.
The same here … Restart does fix it