After Nextcloud AIO update (v7.13.0 to v7.13.1) - "Update needed" Message #4368
-
|
After I updated Nextcloud AIO from v7.13.0 to v7.13.1 I get the Message:
How I updated:
But after some time using the new Nextcloud version, the following message is displayed:
I followed #2726 and just restarted the nextcloud-aio-nextcloud container. But since the message came back, I restarted the whole system. But no luck, after some time, the message comes back Then I tried: #1787 and run: After that I restarted all containers from the Nextcloud AIO interface But again, no luck - after some time the message comes back. Than I disabled all optional containers from the Nextcloud AIO interface and restarted all containers. Then I disabled a bunch of apps like e.g. related_resources. (Remaining) enabled Apps: But again, no luck - after some time (2-5 minutes), the message comes back. Info: Host OSDebian 12.5 Docker VersionDocker version 25.0.4, build 1a576c5 Nextcloud AIO versionNextcloud AIO v7.13.1 Current channelYou are running the latest channel. Other valuable infoNo errors in Nextcloud ~/settings/admin/logging Security & setup warningsTest were always green but now I get the following error:
and if I click on "List of invalid files" I get:
INFO: Please cf.: nextcloud-aio-nextcloud logs below where it states: nextcloud-aio-apache logsnextcloud-aio-database logsnextcloud-aio-nextcloud logsnextcloud-aio-notify-push logsnextcloud-aio-redis logsFurther Notes
Starting master container with: docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 127.0.0.1:8080:8080 \
--env APACHE_PORT=11000 \
--env APACHE_IP_BINDING=127.0.0.1 \
--env NEXTCLOUD_MEMORY_LIMIT=2048M \
--env AIO_DISABLE_BACKUP_SECTION=true \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latestPlease help to troubleshoot further, are there any other logs, that I could check? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
FYI: I found the issue, a customized script, that was triggerd by cron corrupted the config.php of nextcloud-aio-nextcloud Problem solved, thus closing the discussion |
Beta Was this translation helpful? Give feedback.
FYI: I found the issue, a customized script, that was triggerd by cron corrupted the config.php of nextcloud-aio-nextcloud
Problem solved, thus closing the discussion
Thanks anyway