Endless waiting for database.

[igorechek06]

Nextcloud logs

2025-01-06T14:24:45.515826740Z Waiting for Nextcloud to start...
2025-01-06T14:24:50.520966734Z Waiting for Nextcloud to start...
2025-01-06T14:24:55.526177884Z Waiting for Nextcloud to start...
2025-01-06T14:25:00.531499004Z Waiting for Nextcloud to start...
2025-01-06T14:25:05.536692072Z Waiting for Nextcloud to start...
2025-01-06T14:25:10.541847303Z Waiting for Nextcloud to start...
2025-01-06T14:25:15.546949562Z Waiting for Nextcloud to start...
2025-01-06T14:25:20.552103870Z Waiting for Nextcloud to start...
2025-01-06T14:25:25.557223972Z Waiting for Nextcloud to start...
2025-01-06T14:25:30.562385847Z Waiting for Nextcloud to start...
2025-01-06T14:25:35.567602752Z Waiting for Nextcloud to start...

Database logs

2025-01-06T13:51:08.426451231Z Setting postgres values...
2025-01-06T13:51:08.434790619Z chmod: /var/run/postgresql: Operation not permitted
2025-01-06T13:51:08.436236733Z 
2025-01-06T13:51:08.436249288Z PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-01-06T13:51:08.436254522Z 
2025-01-06T13:51:08.622029133Z 2025-01-06 13:51:08.621 GMT [14] LOG:  starting PostgreSQL 16.6 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-01-06T13:51:08.622110183Z 2025-01-06 13:51:08.622 GMT [14] LOG:  listening on IPv6 address "::1", port 5432
2025-01-06T13:51:08.622140582Z 2025-01-06 13:51:08.622 GMT [14] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2025-01-06T13:51:08.668205342Z 2025-01-06 13:51:08.667 GMT [14] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-01-06T13:51:08.770306574Z 2025-01-06 13:51:08.770 GMT [24] LOG:  database system was shut down at 2025-01-06 13:44:18 GMT
2025-01-06T13:51:08.840998300Z 2025-01-06 13:51:08.840 GMT [14] LOG:  database system is ready to accept connections
2025-01-06T13:56:08.867015666Z 2025-01-06 13:56:08.866 GMT [22] LOG:  checkpoint starting: time
2025-01-06T13:56:09.389460409Z 2025-01-06 13:56:09.389 GMT [22] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.123 s, total=0.523 s; sync files=2, longest=0.067 s, average=0.062 s; distance=0 kB, estimate=0 kB; lsn=3/324EED38, redo lsn=3/324EED00

[szaimen]

Hi, can you post the output of sudo docker logs nextcloud-aio-nextcloud here?

[igorechek06]

What exactly dosnt work?

Same issue and logs.

[szaimen]

Hm... So recreating the docker network did not make it work again?

[igorechek06]

Hm... So recreating the docker network did not make it work again?

Yes, nothing has changed.

[szaimen]

Hm... can you post the output of sudo docker info here?

[igorechek06]

Client: Docker Engine - Community
 Version:    27.4.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.3
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.32.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 11
  Running: 11
  Paused: 0
  Stopped: 0
 Images: 11
 Server Version: 27.4.1
 Storage Driver: overlay2
  Backing Filesystem: btrfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 88bf19b2105c8b17560993bee28a01ddc2f97182
 runc version: v1.2.2-0-g7cb3632
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.0-130-generic
 Operating System: Ubuntu 22.04.5 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 31.19GiB
 Name: server
 ID: baafbfcf-54f6-40d8-867e-8b024fd4ce7c
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

[szaimen]

Hm... I just upgraded my test instance to docker v27.4.1 and after letting the containers start correctly, I even tried to reboot and all containers are connecting correctly so I fear I cannot reproduce the problem. Also I am out of ideas nwo what the problem could be.

Probably best to open a new thread for this in a docker forum as this looks like a bug in the dns resolution inside docker networks on your system.

[igorechek06]

I restored the backup on another OS (Arch) and the issue remains. After that, I deleted the database volume and everything worked.