Files not syncing to new Nextcloud 23.0.1 server

cryptoduke · February 16, 2022, 11:49pm

Support intro

Sorry to hear you’re facing problems

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can

Nextcloud version (eg, 20.0.5): 23.0.1
Operating system and version (eg, Ubuntu 20.04): Debian 11 (Bullseye)
Apache or nginx version (eg, Apache 2.4.25): Nginx 1.18.0
PHP version (eg, 7.4): 7.4.25

The issue you are facing:
The issue is that not all files are updated on the server that appear in the designated sync-folder on the desktop.
I have a newly installed Nextcloud instance running 23.0.1.
On my desktop, I am running the Nextcloud Desktop Client Version 3.4.2 (Arch).
I am able to use this same desktop client with Nextcloud servers running different versions and have not encountered this issue until using a 23.x version of Nextcloud.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

Create or move a file into desktop sync-folder.
Desktop either copies it to the server or not.
Even tried a fresh folder with rsyncing the files to it, but problem still occurs.
The files are on the desktop but not on the server.

The output of your Nextcloud log in Admin > Logging:

Level	App	Message		
Time
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-16T18:34:22-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-16T18:34:22-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-16T18:34:22-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-15T00:49:58-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-15T00:49:57-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-15T00:49:57-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T22:49:53-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T22:49:53-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T22:49:53-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T20:49:48-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T20:49:48-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T20:49:48-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T18:49:43-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T18:49:43-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T18:49:43-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T16:42:24-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T16:42:24-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T16:42:24-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T15:41:41-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T15:41:40-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T15:41:40-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T13:41:44-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T13:41:44-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T13:41:44-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T11:41:41-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T11:41:41-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T11:41:41-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T09:41:35-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T09:41:34-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T09:41:34-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T07:41:30-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T07:41:29-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T07:41:29-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T05:41:25-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T05:41:25-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T05:41:25-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T03:41:20-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T03:41:20-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T03:41:20-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T01:41:15-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T01:41:15-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-14T01:41:15-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T23:41:08-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T23:41:08-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T23:41:08-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T21:41:03-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T21:41:03-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T21:41:03-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T19:40:58-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T19:40:58-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T19:40:58-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-13T17:40:54-0500
Error	no app in context	Computed md5 hash is incorrect.		2022-02-13T17:40:12-0500
Error	no app in context	Computed md5 hash is incorrect.		2022-02-13T17:40:12-0500
Error	no app in context	"Documents/REMOVED-INFO" is locked, existing lock on file: exclusive		2022-02-13T17:40:12-0500
Error	no app in context	"Documents/REMOVED-INFO" is locked, existing lock on file: exclusive		2022-02-13T17:40:11-0500
Error	no app in context	"Documents/REMOVED-INFO" is locked, existing lock on file: 3 shared locks		2022-02-13T17:40:09-0500
Error	no app in context	Computed md5 hash is incorrect.		2022-02-13T17:40:09-0500
Error	no app in context	"Documents/REMOVED-INFO" is locked, existing lock on file: 3 shared locks		2022-02-13T17:40:05-0500
Error	no app in context	"Documents/REMOVED-INFO" is locked, existing lock on file: 2 shared locks		2022-02-13T17:40:05-0500
Error	no app in context	"Documents/FOIA-Requests/REMOVED-INFO" is locked, existing lock on file: 2 shared locks		2022-02-13T17:40:05-0500
-- removed lots of sensitive file info, but same errors as above about "locks" --
Error	no app in context			2022-02-10T00:48:26-0500
Error	no app in context			2022-02-10T00:47:59-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-10T00:41:55-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-10T00:41:55-0500
Fatal	webdav	Sabre\DAV\Exception: Unknown error while seeking content		2022-02-10T00:41:55-0500

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'passwordsalt' => 'RMVD',
  'secret' => 'RMVD',
  'trusted_domains' => 
  array (
    0 => 'localhost',
    1 => '*',
  ),
  'datadirectory' => '/mnt/dietpi_userdata/nextcloud_data',
  'dbtype' => 'mysql',
  'version' => '23.0.1.2',
  'hashingThreads' => 8,
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'filelocking.enabled' => true,
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' => 
  array (
    'host' => '/run/redis/redis-server.sock',
    'port' => 0,
  ),
  'overwrite.cli.url' => 'http://localhost/nextcloud',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_admin',
  'dbpassword' => 'RMVD',
  'installed' => true,
  'instanceid' => 'RMVD',
);

The output of your Apache/nginx/system log in /var/log/____:

the nginx logs are empty files on this Nextcloud 23.0.1 server

SimonWolf · February 18, 2022, 3:53pm

I am having the same issue!

github.com/nextcloud/desktop

Windows and Linux (AppImage) clients 3.4.1 Freezing When Uploading Files

opened 05:25PM - 22 Dec 21 UTC

appliedbarrel

bug regression package: appimage os:

Windows os:

Linux feature:

sync engine approved crash

### How to use GitHub * Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue. * Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue. * Subscribe to receive notifications on status change and new comments. ### Expected behaviour Client should upload files to server and notify the user of conflicts, server issues, or other errors with the upload. ### Actual behaviour Client freezes when trying to upload a file. Folder sync connections which don't have changes work fine. Downloads from the server also work. Pausing folders which have pending uploads prevents the client from freezing, but the client still freezes when resuming. Cannot reproduce this problem on version 3.3.6 of the client. ### Steps to reproduce 1. Start client version 3.4.1 2. Resume sync on one or more folders which have upload jobs 3. Observe client beginning upload and progress bar moving 4. Client freezes at the end of the upload 5. Client program is completely unresponsive, has high CPU usage, and must be killed ### Client configuration Client version: 3.4.1  Operating system: Kubuntu 21.10 OS language: en-US Qt version used by client package: ubuntu-5.13.0-22-generic Client package: Nextcloud-3.4.1-x86_64.AppImage from this Github repo Installation path of client: /home/[username] /Applications/Nextcloud-3.4.1-x86_64_5cbe3362585cfaace861289d8773450b.AppImage ### Server configuration  Nextcloud version: 23 Storage backend (external storage): No external storage, Filesystem: ext4 ### Logs Please use Gist (https://gist.github.com/) or a similar code paster for longer logs. 1. Client logfile: I won't upload a debug archive as it does not obfuscate sensitive information. [Here is the final 10 lines of the log produced by the client (GIthub Gist).](https://gist.github.com/appliedbarrel/45fffa24d6291d9deb4c7c5b27fe3ec6) The final line of the logs is usually the same type of message: > [ info nextcloud.sync.networkjob /home/user/src/libsync/abstractnetworkjob.cpp:361 ]: OCC::PutMultiFileJob created for "https://[mywebsite.url]" + "" "OCC::BulkPropagatorJob" Judging by other log messages, it looks like the empty string above "" is where a path should go. I don't know enough to know whether this is useful information or not. There was one instance (could not reproduce) where the above line was followed by: > [ info nextcloud.sync.propagator.root.directory /home/user/src/libsync/owncloudpropagator.cpp:1214 ]: scheduleSelfOrChild OCC::PropagatorJob::Running pending uploads 0 subjobs state OCC::PropagatorJob::Running 2. Web server error log (formatted) It spits this error out each time: > [webdav] Fatal: Unknown error while seeking content > POST /remote.php/dav/bulk > from [IP ADDRESS] by [nextcloud username] at 2021-12-22T16:13:18+00:00 3. Server logfile: nextcloud log (data/nextcloud.log): I can possibly provide this in the future if necessary.

Mornsgrans · February 19, 2022, 4:06pm

First of all you should try a desktop client, wich works reliable e.g. version 3.3.6 or older. - Version 3.4.x still seems not to work properly.