Support intro
Sorry to hear you’re facing problems ![]()
help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
example
Or for longer, use three backticks above and below the code snippet:
longer
example
here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can ![]()
Hi community,
I am having troubles with the database container after the update to AIO v9.0.1.
Nextcloud version (eg, 29.0.5): NA
Operating system and version (eg, Ubuntu 29.04): Debian GNU/Linux 12 (bookworm)
Apache or nginx version (eg, Apache 2.4.25): NA
PHP version (eg, 8.3): NA
The issue you are facing:
After the update to v9.0.1 the database container is not getting to a healthy state. From the logs it appears that the database never gets initiated. I have already tried restoring from a previous back up. I even tried resetting the entire instance by deleting all of the containers and volumes and then restoring from backup.
...
+ psql -d postgresql://oc_nextcloud:<pg_pass>@127.0.0.1:11000/nextcloud_database -c 'select now()'
psql: error: connection to server at "127.0.0.1", port 11000 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
+ echo 'Waiting for the database to start.'
Waiting for the database to start.
+ sleep 5
...
root@docker-host-01:~# docker exec -it nextcloud-aio-database ps aux
PID USER TIME COMMAND
1 postgres 0:00 /sbin/docker-init -- /start.sh
7 postgres 0:04 {start.sh} /bin/bash /start.sh
10 postgres 0:01 tee -i /mnt/data/database-import.log
12613 postgres 0:00 /bin/bash
12629 postgres 0:00 sleep 5
12630 postgres 0:00 ps aux
Is this the first time you’ve seen this error? (Y/N): Yes
I wonder if it has anything to do with the update to PostgreSQL but I have no clue where to start looking.