On a fresh NS8 install, following the Disk migration guideline Disk usage, causes a number of issues when/after installing the Nextcloud App.
During install, i get the following error:
*{“error”:"_acontrol_task request attempt failed (WS reached EOF while waiting for module/traefik1/task/a785bd98-ba56-4b24-a103-635c7894d8cd). Retrying…\nCreated symlink /home/nextcloud1/.config/systemd/user/default.target.wants/nextcloud.service → /home/nextcloud1/.config/systemd/user/nextcloud.service.* … Warning: require_once(/var/www/html/lib/versioncheck.php): Failed to open stream: No such file or directory in /var/www/html/console.php on line 34\r\n\r\nFatal error: Uncaught Error: Failed opening required ‘/var/www/html/lib/versioncheck.php’ (include_path=‘.:/usr/local/lib/php’) in /var/www/html/console.php:34\r\nStack trace:\r\n#0 /var/www/html/occ(11): require_once()\r\n#1 {main}\r\n thrown in /var/www/html/console.php on line 34\r\n"}}
This error only occures only if /home have been migrated to an external mount(mounted as /home)
Although Nextcloud can be used afterwards, I encounter issues with adding email notification: A problem occurred while sending the email. Please revise your settings. (Error: Email could not be sent. Check your mail server log)
This is great. Although the solution, I’m sure, is just temporary.
That does not explain the issues I encountered in relation to the symlink problem, when the container had been moved to an external mount.
I tested the script, installed Nextcloud and it seems to work. Are there still issues regarding the mail notification? If yes, do you use a mail app instance or SMTP?
I got this error too but I think it can be ignored as traefik is working after installation.
This is not an error, the service for nextcloud was enabled which creates a symlink.
I didn’t get this one, can you reproduce it for example by restarting Nextcloud or click “Save” in the Cluster-admin Nextcloud app settings?
Thank you for your many questions. Really appreciate it.
I do not recall, I have a number of alias for the main IP, but I will try to use this next time.
Happy to see that I’m not the only one getting this. Just worried that this might cause issues down the road. I only get this error after I have migrated to an external disk. I have done this a couple of times, using the same procedure and domain information.
I tried both SMTP and mail app, none would go through.
I have tried with a different domain setup and I did not get the error.
At this point I must assume that I have an unresolved DNS in my original setup and as such the issue is not related to me migrating /home to an external HDD.
Thank you for your help so far!
