New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Desktop client 2.5.0 won't sync files correctly #876

Open
carlfriedrich opened this Issue Nov 22, 2018 · 21 comments

Comments

@carlfriedrich
Copy link

carlfriedrich commented Nov 22, 2018

I upgraded my Nextcloud desktop client to the new 2.5.0 release today, on my Windows 8.1 desktop as well as on my Windows 10 tablet. My existing sync connections have been retained, but they are not working correctly anymore: Only files in the root folder are synced correctly. Files in subfolders are not synced.
Furthermore the client does not sync any files when I add a new sync connection. The subfolders are synced, though, but without any file contents.
All this used to work with the previous client version 2.3.3.
I am running Nextcloud server 14.0.3.0 on a hosted webspace.

Expected behaviour

The client should sync all files from the server.

Actual behaviour

The client syncs folders only, but without any file contents. For each file the activity log states "The file [...] could not be downloaded completely". In large folders I sometimes get "GOAWAY received, cannot start a request".

I tried to reduce this to a minimal example and found out that syncing works correctly if there aren't any subfolders at all. As soon as one subfolder exists, syncing files does not work anymore on new connections. So:

Steps to reproduce

  1. Create a new sync connection in the client
  2. Choose an empty local folder
  3. Choose an existing non-empty remote folder with at least one subfolder, e.g. with the following structure:
  • file.txt
  • subfolder
    • anotherfile.txt
  1. Wait for sync and see it fail for all files

Client configuration

Client version:
2.5.0

Operating system:
Windows 8.1 / Windows 10

OS language:
German

Qt version used by client package (Linux only, see also Settings dialog):

Client package (From Nextcloud or distro) (Linux only):

Installation path of client:
Default path

Server configuration

Operating system:

Web server:

Database:
mysql 5.7.24

PHP version:
7.2.12

Nextcloud version:
14.0.3.0

Storage backend (external storage):

Logs

  1. Client logfile: Output of nextcloud --logwindow or nextcloud --logfile log.txt
    https://gist.github.com/carlfriedrich/babe52f847ce3c5a85b2dbbd8a5efe7f

  2. Web server error log:
    no access

  3. Server logfile: nextcloud log (data/nextcloud.log):
    Nothing relevant in there

@Iolaum

This comment has been minimized.

Copy link

Iolaum commented Nov 23, 2018

I also experience a similar problem.

Expected behaviour

Client should sync files properly and not crash.

Actual behaviour

Files do not sync properly, for example moving a file causes the server to delete and re-download it instead of moving it (as I see through activity). Client has crashed a lot of times recently. I use Ubuntu MATE 18.04 and I have send error reports at least 4 times this week.

Steps to reproduce

  1. Start my laptop.
  2. Move or alter some files that are synced.
  3. Check activity logs to see what happened.

Client configuration

Client version:

$ apt policy nextcloud-client
nextcloud-client:
  Installed: 2.5.0-20181111.015125~bionic1
  Candidate: 2.5.0-20181111.015125~bionic1
  Version table:
 *** 2.5.0-20181111.015125~bionic1 500
        500 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

Operating system:

Ubuntu MATE 18.04:

$ uname -a
Linux shade 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

OS language:

Qt version used by client package (Linux only, see also Settings dialog):

Client package (From Nextcloud or distro) (Linux only):

Installed from the ppa provided by the nextcloud team (http://ppa.launchpad.net/nextcloud-devs/client/ubuntu )

Installation path of client:

$ which nextcloud
/usr/bin/nextcloud

Server configuration

NextCloudBox running on raspberry pi 2 with the updated NextCloudPi.

Operating system:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 9.6 (stretch)
Release:	9.6
Codename:	stretch

Web server:

$ apt policy apache2
apache2:
  Installed: 2.4.25-3+deb9u6
  Candidate: 2.4.25-3+deb9u6
  Version table:
 *** 2.4.25-3+deb9u6 500
        500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
        100 /var/lib/dpkg/status

Database:

$ apt policy mariadb-server
mariadb-server:
  Installed: 10.1.37-0+deb9u1
  Candidate: 10.1.37-0+deb9u1
  Version table:
 *** 10.1.37-0+deb9u1 500
        500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
        100 /var/lib/dpkg/status

PHP version:

$ php --version
PHP 7.2.12-1+0~20181112102304.11+stretch~1.gbp55f215 (cli) (built: Nov 12 2018 10:23:04) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.12-1+0~20181112102304.11+stretch~1.gbp55f215, Copyright (c) 1999-2018, by Zend Technologies

Nextcloud version: 14.0.3.0

Storage backend (external storage):

1 Tb external HDD (original provided by NextCloudBox)

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

Template for output < 10 lines

  1. Client logfile: Output of nextcloud --logwindow or nextcloud --logfile log.txt
    (On Windows using cmd.exe, you might need to first cd into the Nextcloud directory)
    (See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)

  2. Web server error log:

  3. Server logfile: nextcloud log (data/nextcloud.log):

@JanSvoboda

This comment has been minimized.

Copy link

JanSvoboda commented Nov 26, 2018

Hello,

I have encountered the same issue. What helped me was to disable e2e encryption application on nextcloud server. It seems that calling GetFolderEncryptStatus and the response to it with 404 distrupts the synchronization of files

@carlfriedrich

This comment has been minimized.

Copy link
Author

carlfriedrich commented Nov 29, 2018

I can confirm that deactivating the e2e app on my server made the client 2.5.0 correctly start syncing files again.
This can serve as a workaround for now, but since I would like to use e2e, the issue should be fixed.

@Ralayax

This comment has been minimized.

Copy link

Ralayax commented Nov 29, 2018

Same issue, same solution for me.

@Iolaum

This comment has been minimized.

Copy link

Iolaum commented Dec 2, 2018

I do not have neither server-side nor client side encryption but I am still getting sync problems. Often the client appears to not do anything. The solution is to close the program and re-start it. That helps the desktop client get in a state where it starts syncing files again. Still this is far from ideal and a regression compared to 2.3.3

@bjoernv

This comment has been minimized.

Copy link

bjoernv commented Dec 3, 2018

For me syncing itself works, but in 2.5.0 it is annoying. In my Nextcloud setup I excluded some folders (e.g. build directories for a software project) and Nextcloud 2.5.0 tells me every time after a sync run, that there are unsolved conflicts. The "conflicts" are in fact excluded files and directories. The "conflicts" are reported as desktop notifications even if server notifications are disabled. Also CPU usage is high and the client crashes after some hours. I do not have client or server side encryption enabled. It is an regression compared to 2.3.3.

@Iolaum

This comment has been minimized.

Copy link

Iolaum commented Dec 3, 2018

I 've also gotten conflicts that I resolved by either waiting until the client+server spoke again and resolved them or by restarting the client.

@tanghus

This comment has been minimized.

Copy link

tanghus commented Dec 4, 2018

I have somewhat of the same problem.
After updating the client, it disconnects shortly after.
I get a lot of failed logins in the server log

In the client log, it repeats the following for each folder:

[OCC::FolderMan::scheduleFolder 	Folder is not ready to sync, not scheduled!
[OCC::ownCloudGui::slotSyncStateChange 	Sync state changed for folder  "https://cloud.example.com/remote.php/webdav/Notes" :  "Not yet Started"
[OCC::ConfigFile::setupDefaultExcludeFilePaths 	Adding user defined ignore list to csync: "/home/tol/.config/Nextcloud/sync-exclude.lst"
[OCC::FolderMan::addFolderInternal 	Adding folder to Folder Map  OCC::Folder(0x55b19875a610) "5"
[OCC::FolderMan::scheduleFolder 	Schedule folder  "5"  to sync!
[OCC::FolderMan::scheduleFolder 	Folder is not ready to sync, not scheduled!
[OCC::ownCloudGui::slotSyncStateChange 	Sync state changed for folder  "https://cloud.example.com/remote.php/webdav/Photos" :  "Not yet Started"
[OCC::ConfigFile::setupDefaultExcludeFilePaths 	Adding user defined ignore list to csync: "/home/tol/.config/Nextcloud/sync-exclude.lst"
[OCC::FolderMan::addFolderInternal 	Adding folder to Folder Map  OCC::Folder(0x55b198781270) "6"
[OCC::FolderMan::scheduleFolder 	Schedule folder  "6"  to sync!
[OCC::FolderMan::scheduleFolder 	Folder is not ready to sync, not scheduled!
[OCC::ownCloudGui::slotSyncStateChange 	Sync state changed for folder  "https://cloud.example.com/remote.php/webdav/tanghus_dot_net" :  "Not yet Started"
[OCC::ConfigFile::setupDefaultExcludeFilePaths 	Adding user defined ignore list to csync: "/home/tol/.config/Nextcloud/sync-exclude.lst"
[OCC::FolderMan::addFolderInternal 	Adding folder to Folder Map  OCC::Folder(0x55b198781ec0) "7"
[OCC::FolderMan::scheduleFolder 	Schedule folder  "7"  to sync!
[OCC::FolderMan::scheduleFolder 	Folder is not ready to sync, not scheduled!
[OCC::ownCloudGui::slotSyncStateChange 	Sync state changed for folder  "https://cloud.example.com/remote.php/webdav/InstantUpload" :  "Not yet Started"
[OCC::ConfigFile::setupDefaultExcludeFilePaths 	Adding user defined ignore list to csync: "/home/tol/.config/Nextcloud/sync-exclude.lst"
[OCC::FolderMan::addFolderInternal 	Adding folder to Folder Map  OCC::Folder(0x55b1987873d0) "8"
[OCC::FolderMan::scheduleFolder 	Schedule folder  "8"  to sync!
[OCC::FolderMan::scheduleFolder 	Folder is not ready to sync, not scheduled!
[OCC::ownCloudGui::slotSyncStateChange 	Sync state changed for folder  "https://cloud.example.com/remote.php/webdav/Uploads" :  "Not yet Started"
[OCC::SyncJournalDb::checkConnect 	sqlite3 version "3.22.0"

It started to work again when I removed the account and added the sync connection one by one and let them sync one at a time.

After restarting the client it failed again.

@tanghus

This comment has been minimized.

@tanghus

This comment has been minimized.

Copy link

tanghus commented Dec 5, 2018

It could be related to #771

@mduller

This comment has been minimized.

Copy link

mduller commented Dec 10, 2018

Same here - only restarting the client (2.5.1 on Windows 10 1809) makes it pick up files in subfolders. I don't use e2e encryption.

Edit: add Windows version

@stratacast

This comment has been minimized.

Copy link

stratacast commented Dec 12, 2018

I couldn't get sync to work until I disabled e2e server side also. I was continually getting the GOAWAY errors as mentioned earlier.

@daftmilk

This comment has been minimized.

Copy link

daftmilk commented Dec 12, 2018

Same problem on Mac: Moving a folder with subfolders into Nextcloud or just renaming a hierarchical folder structure only syncs folders at the first level but not on the sublevel. I can work around the issue by removing the subfolders, wait for a few seconds and then drop them back in. However I need to repeat this for the subfolders within the subfolders and so on. Looks like somebody just forgot to put the recursive flag into the process that monitors changes. Something to the extend of forgetting to call ls instead of calling ls -R. Feels like it could be a really easy fix…

@Iolaum

This comment has been minimized.

Copy link

Iolaum commented Dec 12, 2018

@daftmilk Another solution after you move a folder with subfolders and only syncs the top level folder is to close/quit the client and re-open it. I learnt that neat trick because my client crashes so often that I noticed it synced properly after I restarted it. After it re-opens it will find and sync what it missed the first time.

@csharpner

This comment has been minimized.

Copy link

csharpner commented Dec 19, 2018

Same problem here. 2 desktops, both experiencing root folders sync the files and create the subfolders, but nothing in the subfolders gets synced, not even folders inside the subfolders.

@Peac

This comment has been minimized.

Copy link

Peac commented Dec 20, 2018

Same problem here on Ubuntu 18.04 and client version 2.5.1.
Quite annoying. Restarting the client does not help.
I'm not using e2e or server side encryption.

@mduller

This comment has been minimized.

Copy link

mduller commented Dec 29, 2018

Pausing synchronization before adding the folder structure and then resuming synchronization also works around the problem (Client 2.5.1 on Windows 10).
Edit: one detail that may be relevant: I copied the folder structure (from a mounted network share to the local folder set up for sync) instead of moving it!

@Iolaum

This comment has been minimized.

Copy link

Iolaum commented Jan 12, 2019

I 'm still having problems with the nextcloud client. I am basically checking the activity tab, that has also re-gressed UI wise from the 2.3.3 version, to make sure that files I changed have been updated on the server. I often find myself pausing and resuming sync or downright closing and restarting the client so that it picks up my changes.

System information:

$ apt policy nextcloud-client
nextcloud-client:
  Installed: 2.5.1-20181204.111806~bionic1
  Candidate: 2.5.1-20181204.111806~bionic1
  Version table:
 *** 2.5.1-20181204.111806~bionic1 500
        500 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic
@R8s6

This comment has been minimized.

Copy link

R8s6 commented Feb 7, 2019

As of 2019 Feb 07, I can confirm that I still have this error. Server running on ubuntu server 18.04.01 with nextcloud snap, and client version 2.5.1 running on Arch. I don't have server or client encryption. Only folders are synced but no files are synced. Only restarting the client solves the issue temporarily.

@alberto464

This comment has been minimized.

Copy link

alberto464 commented Feb 13, 2019

I have the same problem, when I load multiple files the subfolders are not synchronized. Has anyone found the solution?

@chaos-prevails

This comment has been minimized.

Copy link

chaos-prevails commented Feb 18, 2019

Server: 15.0.4, php 7.0 (ubuntu 16.04 server install)
Client: 2.5.1 same problem experiences on linux 18.04 ubuntu desktop and windows (10).

I second this problem as mentioned in #969. Moving or renaming folders deletes them on the server, and only recreates them with a restart of the nextcloud client (v 2.5.1). This problem is not happening with 2.3.3.1. This causes massive troubles in sync/resync/trash if staff is renaming a shallow folder.

This is a major problem, as it is non-trivial to change/downgrade all clients. Hope this can be solved on the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment