Nextcloud fails to configure on NS8

Hi all,

on a test instance of NS8, today I uninstalled my nextcloud instance, and later on added a new one. However, configuration of the newly installed application fails, and I am no longer able to install another nextcloud instance. I tried over again several times, but configuration always fails.
{92E6BE7D-8711-41A0-9002-0A2424A4117F}

Under settings I just copied what was used in the previously deleted nextcloud instance, so the settings should be correct. The hostname points to a CNAME entry that resolves to the IP of the NS8 host, I manually gave an admin password, and use my internal ldap user domain.

Underlying rocky linux has all updates installed, also the NS8 system has all updates applied successfully.

Any ideas how to solve this issue?

Thank you!

I tried to reproduce on a Rocky test VM and wasn’t successful. After removing an Nextcloud instance I installed another one and configuration was OK.

Please check the system logs page for errors in the Nextcloud app.
You could follow the log and then try to reconfigure Nextcloud…

Hi,

thank you. I deleted all nextcloud instances in the affected system and installed a new instance. It still fails during configuration.

In the logs after starting configuration of the app, I find this:

2024-11-01T22:12:15+01:00 [1:nextcloud7:nextcloud-db] 2024-11-01 21:12:15+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.19+maria~ubu2004 started.
2024-11-01T22:12:15+01:00 [1:nextcloud7:podman] a597f6e078b51773df5e4f868dd1dfe2516487479f9b88c855e846bede144419
2024-11-01T22:12:15+01:00 [1:nextcloud7:systemd] Started Podman nextcloud-db.service.
2024-11-01T22:12:15+01:00 [1:nextcloud7:nextcloud-db] 2024-11-01 21:12:15+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2024-11-01T22:12:15+01:00 [1:nextcloud7:nextcloud-db] 2024-11-01 21:12:15+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.19+maria~ubu2004 started.
2024-11-01T22:12:15+01:00 [1:nextcloud7:nextcloud-db] ls: cannot open directory ‘/docker-entrypoint-initdb.d/’: Permission denied
2024-11-01T22:12:15+01:00 [1:nextcloud7:systemd] nextcloud-db.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2024-11-01T22:12:15+01:00 [1:nextcloud7:podman] a597f6e078b51773df5e4f868dd1dfe2516487479f9b88c855e846bede144419
2024-11-01T22:12:15+01:00 [1:nextcloud7:systemd] nextcloud-db.service: Failed with result ‘exit-code’.

Consequently, the nextcloud-db container is not running after configuration.

Any idea what could be causing this issue?

Thank you!

Looks like a permission issue.

Let’s try to reproduce the error:

Enter environment:

runagent -m nextcloud7

Execute the ls command in the container to check if you get another permission error:

As the container is stopped we need to use podman run:

podman run --rm -ti -v nextcloud-db-data:/var/lib/mysql -v ./restore/:/docker-entrypoint-initdb.d/:z mariadb:10.6.19 ls /docker-entrypoint-initdb.d/

Maybe it helps to check the nextcloud-db service status:

systemctl --user status nextcloud-db

Thank you for your support.

This command runs without error when executed within the runagent -m nextcloud7 environment. However, it shows no output, the directory is empty.
Executing ls -ld in the same command shows

drwxr-x—. 2 root root 4096 Nov 1 21:12 /docker-entrypoint-initdb.d/

I don’t know whether these are the correct permissions.
Checking systemctl --user status nextcloud-db shows that this service is failed. This is what I expected, because the failed state for nextcloud-db service is also shown in the NS8 UI.

Something seems to be pretty wrong here, and I cannot explain why. All I did was to install NS8 on a fresh Rocky Linux installation a few months ago and installed some apps including nextcloud. At that time, everything was working. Now I switched the machine back on, updated everything (at that point the original nextcloud install was still working), then removed nextcloud and tried to re-install it. Since then, it is failing. I do not see anything that could/should have caused this issue.
The VM has 6GB RAM and 20GB hard disk (root), 100G hard disk (/home), with the root disk having 17G available, the /home disk having 85G available, and 1.7G free RAM, 1.8G buffer, no swap used. So it does not seem to be a resource problem.
When moving /home to a second disk, I followed the tutorial here: Disk usage — NS8 documentation

Could be a Selinux problem?