I am used to the constellation nextcloud (20.0.8) + nc-data directory on server.
I either access via web interface or by accessing desktop client synced data (not directly accessing the nextcloud files).
the desktop client is installed on a ubuntu 20.10 vm I use to work on.
this desktop client uses a dedicated share on the server and gives me trouble.
syncing 9 GB Data to the new nextcloud (I filled the nc client’s share with the data to get it into the nc-server) took about three days. In this time I repeadedly had to restart the sync client. all (work vm, nextcloud docker and the data directories reside on the very same, new, xeon based server).
now, after an update and reboot of the ubuntu 20.10 I am getting the error the nextcloud client couldn’t create the sync-database (sync-datenbank) … please make sure there are write permissions for the sync folder (roughly translated from "Bitte sicherstwellen, dass Schreibrechte für den zu synchronisierenden Ordner existieren.)
so this is the fstab line (the other mounts on the same server don’t give me problems):
//unraid/data/nc_workdir /mnt/nc_local cifs credentials=/this_cifspw_work,noperm,iocharset=utf8 0 0
and this is the ll /mnt of the sync-mount:
drwxr-xr-x 2 root root 0 Feb 26 19:23 nc_local/
So I think I have a problem in my mount strategy?
Your help is really welcome.
hi @Stefanle nextcloud need read and write ( maybe execute ) access to your mount:
sudo chown -R root:www-data /nc_local ( replace www-data by your http/nextcloud user )
sudo chmod -R 775 /nc_local
Several revolutions of fstab settings later (some including lots of 7s) I still expire hanging desktop sync client as crashing or not being able to write to .sync…db as is.
Perhaps this is accounted to not using a LTE, perhaps just the client on linux (see below).
I’ll plain work online for now and wait for nextcloud 21 and the new desktop client to get stable.
In the past I havent’t had a clear understanding if the mount parameters in fstab user (uid) refer to
the one logged on to the machine running the nextcloud client
the file host’s user
the nextcloud server itself
I suppose it is the first one.
Here is what I work with:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-root’
Nextcloud version 3.1.3-20210218.151938.3842d306f-1.0~groovy1
Using Qt 5.14.2, built against Qt 5.14.2
Using Qt platform plugin ‘xcb’
Using ‘OpenSSL 1.1.1f 31 Mar 2020’
Running on Ubuntu 20.10, x86_64
Thanks for your answer. Before I run into the same on the next version:
Which nextcloud user do you exactly mean?
Since the filer server uses another share and user for my sync & work pc than the share where the nextcloud server stores the nc data and is mounted to.
Then there is a user with another uid and name on the machine i mounted the nc work directory to. This one I used instead of www_data.
//unraid/nc_workdir /mnt/nc_local cifs credentials=/home/clientuser/.cifspw,uid=0,gid=1000,file_mode=0777,dir_mode=0777,noperm,iocharset=utf8 0 0
drwxrwxrwx 2 root clientuser 0 Feb 28 21:51 nc_local/
Yes, too many 7s, but the desktop sync client still is unstable.
This one really got me…
sorry I misread the post at the time I wrote it. I thought it was the data directory of your nextcloud server. You can reset root:root (
sudo chown -R root:root /nc_local).
Have you more logs into your nextcloud client ?? (settings > create a debugging archive > unzip the archive and go to logs )