Hi all,
we set up a file server for a small office to share files via Samba. The files directory is then synced via nextcloudcmd
to a Nextcloud instance running at some hosting provider.
nextcloudcmd
is running on the Samba server, so it’s all local files, no remote mounts or similar. The reason behind that setup is that the users prefer to have file server semantics while at the office, still have a copy of all the files available in the cloud when they are on the road. Main work is done on the file server, that’s why we picked a setup like this.
Worked great and has been running for a couple of weeks, now. Suddenly users complain that certain files are not showing up in the “web cloud” while they are definitely on the file server.
Simple things we checked:
- system time, NTP, timestamps of files - OK
- we use a single dedicated nextcloud user for this synchronization
- we wrote a shell wrapper that guarantees that there are no multiple jobs running in parallel
When a nextcloudcmd
sync job is running, it is invoked like this:
/usr/local/bin/nextcloudcmd -n --non-interactive --logdebug /var/nextcloud https://url.of.my.cloud >>"${LOGFILE}" 2>&1
I see INSTRUCTION_NEW
entries for new files, but somehow they never make it to the server or they appear literally days later. We currently run one sync per hour and this is sufficient to process the entire file tree …
Any hints what I should look for greatly appreciated.
Patrick