Nethserver 8 Nextcloud unable to save configuration

wahmed · April 27, 2024, 8:21pm

NethServer Version: NS8
Module: Nextcloud

Next up in the test is Nextcloud. I am happy to say the app install of Nextcloud finished without issue. But when i tried to save configuration, it produced this error:

I added a FQDN, typed in password, selected User Domain for authentication which is samba on NS8.
I have the complete log of Nextcloud app in a txt file. How do I send it Dev team?

mrmarkuz · April 27, 2024, 8:30pm

I don’t think you can send it to a team. If there’s no private information in the logs you could use a pastebin site like https://gist.github.com/ or https://privatebin.info/ etc

wahmed · April 27, 2024, 8:37pm

Good idea.
Here is the privatebin link for the nextcloud app.

mrmarkuz · April 27, 2024, 9:14pm

From the log it seems the nextcloud-app service doesn’t start (in time) but I’m still in learning stage as regards reading NS8 logs…

Did you enter a FQDN like “nextcloud.domain.tld” that points to your server in DNS? Don’t know if it really matters, just an idea…

Does it contain special chars? If yes please try a simpler password.

wahmed · April 27, 2024, 10:46pm

Yes i did enter full hostname as FQDN.

I tried both complex and simple password also tried with default neth password as is. Tried it both Samba and local nextcloud authentication option. Same result in all scenario. Nextcloud simply wont finish configuration.

However, i am able to Uninstall the broken instance of nextcloud.

stephdl · May 2, 2024, 6:52am

Hello

Nextcloud-app got a timeout to start, could you reproduce we normally set a 70seconds timeout

This could be done by slow spinners or slow cpu but we could trick the systemd service to wait for this case

No offense on my side

Could you try to reproduce the issue on your side if yes in the nextcloud-app service i could point you where to add more time.

In fact at the first boot we create the sql database and other services before to start nextcloud-app…it takes a long time for that

github.com

NethServer/ns8-nextcloud/blob/e91966aba0c92e701727098e004ea912f5082bc1/imageroot/systemd/user/nextcloud-app.service#L11


      
          
          [Unit]
          Description=Podman nextcloud-app.service
          BindsTo=nextcloud.service
          After=nextcloud.service
          
          [Service]
          Environment=PODMAN_SYSTEMD_UNIT=%n
          EnvironmentFile=%S/state/environment
          Restart=always
          TimeoutStopSec=70
          ExecStartPre=/bin/rm -f %t/nextcloud-app.pid %t/nextcloud-app.ctr-id
          ExecStartPre=-runagent discover-smarthost
          ExecStartPost=runagent wait-startup
          ExecStartPost=runagent setup-smtp
          ExecStart=/usr/bin/podman run --conmon-pidfile %t/nextcloud-app.pid --cidfile %t/nextcloud-app.ctr-id --cgroups=no-conmon --pod-id-file %t/nextcloud.pod-id --replace -d --name nextcloud-app --env-file=%S/state/config.env --env-file=%S/state/smarthost.env -v nextcloud-app-data:/var/www/html -v %S/state/zzz_nethserver.conf:/usr/local/etc/php-fpm.d/zzz_nethserver.conf:z ${NEXTCLOUD_APP_IMAGE}
          ExecStop=/usr/bin/podman stop --ignore --cidfile %t/nextcloud-app.ctr-id -t 10
          ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile %t/nextcloud-app.ctr-id
          PIDFile=%t/nextcloud-app.pid
          Type=forking

bjarnet · July 28, 2024, 7:32pm

I experienced the same issue and think that the timeout is too short.

In my case, the Nextcloud configuration step failed on NS8 running in a virtual machine on Proxmox, with /home being a mounted partition from a (qcow) drive on NFS storage. After I moved that drive from NFS to PVE local storage, the installation and configuration completed successfully.