nextcloudcmd hangs with "[ info nextcloud.sync.engine ]: All the files are going to be changed, asking the user" #3144
Comments
FlexW
added
confirmed
|
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
|
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
|
Still an issue with 3.2.2 |
|
Getting this same hanging behavior. Attempted both with and without
Steps:
Result of |
|
The same for me with newest version |
|
Same error with latest version: |
|
I have the exact same problem! |
|
Still a problem |
|
Same problem: |
|
My current workaround is to have an empty file My main use case is to have Nextcloud as a file transfer platform using a group folder. We usually send only one single file and the receiver deletes it when he's done copying to his local drive. So the workspace gets emptied very often. Using this dummy hidden file helps circumventing this issue. Hope to get a fix soon! |
|
Problem still remains:
Workaround by @jeritiana works. |
|
Problem still remains also for me. The workaround from @jeritiana does not work for me. If you take a look at the code: https://github.com/nextcloud/desktop/blob/master/src/libsync/syncengine.cpp#L750 You can see that this program is always asking for the user when files have to be removed... ( I tried to use the nextcloud client for an automated replication/synchronization which is impossible because of that. |
|
Problem still exists |
|
Same Problem Here: |
|
Still persist. |
|
Problem still present. |
|
Still an issue, this should be a simple bool check to see if |
|
Problem still present. |
|
Problem still occurs. Nextcloud version 3.9.0-20230616.170352.c6c6c61f5-1.0~jammy1 |
|
Will this be solved anytime? If not I might need to drop Nextcloud as it doesn't have the ability to sync unattended |
|
I had the same error message leading me here, after I migrated to a new host/instance, with the same user and files. Fixed it by removing the .sync.xxx database files in the root directory of my user. Guessing the nextcloud instance identifiers in the database(s) are different. |
|
Also an issue for me. Please fix this. |
|
dfcsoftware's (August 12) answer worked for me as well - I went to the directory where I was trying to download the files to (specific user), removed the .sync_xxxxx files, nextcloudcmd was able to run after that without "asking the user". |
|
This is still an issue and deleting the .sync file is not working every time. I'll further investigate the exact behavior and report it here. |
|
Problem still present. |
|
Problem still exists |
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
…ing signal to display warning. The signal is not connected to any slot when running nextcloudcmd. The callback to finish the sync was never being called because the check for the config was done in the slot, which was never called. Signed-off-by: Camila Ayres <[email protected]>
and others
How to use GitHub
Expected behaviour
Nextcloudcmd completes a sync.
Actual behaviour
Nextcloudcmd sees that it is deleting the last file in a folder, issues a message:
04-15 20:05:02:389 [ info nextcloud.sync.engine ]: All the files are going to be changed, asking the user
and then hangs. No matter what the setting of --non-interactive.
This is new behavior in 3.2.
Steps to reproduce
Client configuration
Client version:
Operating system: Ubuntu focal
OS language:
Qt version used by client package (Linux only, see also Settings dialog):
Client package (From Nextcloud or distro) (Linux only):
Installation path of client:
/usr/bin/nextcloudcmd
Server configuration
Nextcloud version: 21.0.1
Storage backend (external storage):
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
Client logfile: https://gist.github.com/jchonig/ad74e517c88270bd3fe9a59b9a41b88f
Web server error log:
Server logfile: nextcloud log (data/nextcloud.log):
The text was updated successfully, but these errors were encountered: