Bug: post-restore script 20configure fails on line 39 - Nextcloud database not ready

[stephdl]

Steps to reproduce

• Restore NethServer backup of nextcloud with collabora enabled
• System automatically runs the post-restore script (20configure)
• The restore process tries to configure collabora

Expected behavior

Nextcloud configuration should proceed only when the related database is fully restored and available.

2026-05-02T16:51:43+02:00 [1:nextcloud1:podman] c983b51f6232ba2a4fc3bda9244e9b5fe7dd132a0d51eeb628c405da7e6cf6f3
2026-05-02T16:51:43+02:00 [1:nextcloud1:systemd] Started Podman nextcloud-nginx.service.
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
2026-05-02T16:51:43+02:00 [1:nextcloud1:systemd] Started libcrun container.
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] /docker-entrypoint.sh: Configuration complete; ready for start up
2026-05-02T16:51:43+02:00 [1:nextcloud1:podman] 3da405884e5dab26eeed839877ec85ac6359074fb6e0a575a045abecb9a3ad79
2026-05-02T16:51:43+02:00 [1:nextcloud1:systemd] Started Podman nextcloud-notify_push.service.
2026-05-02T16:51:43+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0832fad4-1bc0-4487-ada1-f601ba322852: configure-module/80configure_collabora is starting
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: using the "epoll" event method
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: nginx/1.29.2
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: built by gcc 14.2.0 (Alpine 14.2.0)
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: OS: Linux 5.14.0-611.5.1.el9_7.x86_64
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 524288:524288
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: start worker processes
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: start worker process 25
2026-05-02T16:51:43+02:00 [1:nextcloud1:nextcloud-nginx] 2026/05/02 14:51:43 [notice] 1#1: start worker process 26
2026-05-02T16:51:45+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/0832fad4-1bc0-4487-ada1-f601ba322852: action "configure-module" status is "aborted" (1) at step 80configure_collabora
2026-05-02T16:51:45+02:00 [1:nextcloud1:agent@nextcloud1] _acontrol_task request recovered successfully at attempt 2
2026-05-02T16:51:45+02:00 [1:nextcloud1:agent@nextcloud1] The configure-module subtask failed!
2026-05-02T16:51:45+02:00 [1:nextcloud1:agent@nextcloud1]   File "/home/nextcloud1/.config/actions/restore-module/20configure", line 39, in <module>
2026-05-02T16:51:45+02:00 [1:nextcloud1:agent@nextcloud1]     agent.assert_exp(configure_retval['exit_code'] == 0, "The configure-module subtask failed!")
2026-05-02T16:51:45+02:00 [1:nextcloud1:agent@nextcloud1] task/module/nextcloud1/4d6338ba-d627-4f05-a7d6-39f564a410ce: action "restore-module" status is "aborted" (2) at step 20configure
2026-05-02T16:52:02+02:00 [1:nextcloud1:nextcloud-db]
2026-05-02T16:52:02+02:00 [1:nextcloud1:nextcloud-db]
2026-05-02T16:52:02+02:00 [1:nextcloud1:nextcloud-db] 2026-05-02 14:52:02+00:00 [Note] [Entrypoint]: Stopping temporary server
2026-05-02T16:52:02+02:00 [1:nextcloud1:nextcloud-db] 2026-05-02 14:52:02 0 [Note] mariadbd (initiated by: unknown): Normal shutdown

see : 2026-05-02T16:52:02+02:00 [1:nextcloud1:nextcloud-db]

Actual behavior

The 20configure script fails on line 39 because it attempts to configure collabora before the completion of database restoration. This leads to an error as some required database resources are not yet present.

Components

• NethServer 8
• Module: Collabora + Nextcloud

See also

• community.nethserver.org discussion

---

thank canduccimauro

[stephdl]

QA

Version: nextcloud:1.7.1-dev.3
Purpose: Restore must not configure Collabora until the Nextcloud DB is ready.

Steps

1. Install Nextcloud (nextcloud:1.7.1-dev.3) and finish initial setup.
2. Install Collabora.
3. In Nextcloud settings, enable/configure Collabora/Office integration.
4. Verify it works: upload a .docx/.odt and open/edit it in the browser.
5. Backup the Nextcloud instance.
6. Restore that backup onto the same instance (self-restore).
7. During restore, watch the task/logs: it must wait for DB readiness before running Collabora configuration.

Pass criteria

• Restore completes successfully (no abort on restore-module/20configure or configure-module/80configure_collabora).
• After restore:
  • Nextcloud login works
  • Your files are present
  • Collabora still opens/edits documents from Nextcloud

Fail criteria (this issue)

• Restore aborts because Collabora configuration runs too early (DB not ready), like the previous failure at 20configure / 80configure_collabora.