Unable to restart nextcloud AIO after update because of database failure

ℹ️ Support
, , ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

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. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Nextcloud AIO v11.2.1
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu 24.04.2 LTS
  • Web server and version (e.g, Apache 2.4.25):
    • don't know
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Caddy
  • PHP version (e.g, 8.3):
    • don't know
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • After nextcloud AIO update
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

After an AIO update (stop containersandstart and update container`), i can’t start my nextcloud instance anymore. It seems that nextcloud database is the component failing to start and avoiding other nextcloud components to start correctly.

Here is the logs of the nextcloud database:

Database export failed the last time. Most likely was the export time not high enough.
Please report this to https://github.com/nextcloud/all-in-one/issues. Thanks!

I tried to stop nextcloud-aio-database, remove it and prune. After that i restarted nextcloud-aio-mastercontainer but i had the same issue.

Steps to replicate it (hint: details matter!):

  1. Open AIO interface
  2. Stop containers
  3. Start and update containers

Log entries

Nextcloud

My nextcloud.log is empty in the nextcloud data directory

1 Like
2

Hi, can you restore a backup?

3

Hello, thank for your reply.
Unfortunately i didn’t backup my setup until now.

4

This is bad…

Can you post the output of sudo docker info here?

5

Yes, i know it’s a shame, i delayed the moment i will do it and ended up never doing it.

Here is the ouptut:

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

Server:
 Containers: 25
  Running: 20
  Paused: 0
  Stopped: 5
 Images: 25
 Server Version: 27.1.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  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: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8fc6bcff51318944179630522a095cc9dbf9f353
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.8.0-63-generic
 Operating System: Ubuntu 24.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 15.47GiB
 Name: nas
 ID: H4EX:BWXT:Q7ML:AHU6:YH2R:RM5D:7YHL:D27R:FDNU:YJG5:Z5P3:NCKI
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
``
6

It sounds like the database container is failing due to an incomplete or failed export during the update. Try increasing the database export timeout if possible. Since removing and pruning the database container didn’t help, you might need to restore from a backup if available. Otherwise, check the AIO GitHub issues for similar reports and consider reporting your logs there. Also, verify disk space and permissions on your host, as these can cause database startup failures. Make sure all containers are properly stopped before updating to avoid corruption.

7

OK thanks for your help, i will try this when i will be at home

8

I have this permission for my data folder: drwxr-x--- 19 www-data root 4096 juil. 4 11:56 nextcloud_data .
As far as i know it always worked like that but maybe it’s wrong.