"Can't update non existing placeholder info" multiple messages #4274
Comments
|
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! |
|
Upon adding a folder to sync in Windows 11 to my Nextcloud 22.2.5 a few files gave this error also:
The files were uploaded, so in effect nothing seems wrong, only the error itself!? I could resolve the error in a crummy way:
I also tried "occ files:scan --all" This did not fix the error. I think there was something going wrong in the desktop application? |
|
AD: what I noticed was that most of the dozen errors were images where windows did not show a preview of. Opening the file did work however and showed an image (one was a wmv file). Might it be something with content type (detection) preview? |
|
I have the same issue on a fresh install of 23.0.3 and Windows 10 client 3.4.4 but it's only failing on one file, a 4GB .iso file. I thought maybe it was something to do with the default limits on file sizes so I increased the max memory to 2GB, and max filesize and max POST size to 10GB in php.ini (system resources aren't an issue), but it's still failing on that one file with the "Can't update non existing placeholder info" error. |
|
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! |
|
I replicated the problem on Windows 11 NC client 3.5.1 connected to NC 24.0.0 running on TrueNAS Scale (official repo). |
|
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! |
|
I also have this issue on Windows. The file should be synced to external storage. It is not a large file (<10MB). |
|
Same issue here. Running Win 10 21H2 with Nextcloud Client 3.5.1. Get this for thousands of files (and various file-types). Does this error-message has something to do with the virtual files?
Not sure which way was chosen here, but the error message sounds more like 1.). Please let me know if I could help by testing something. |
|
it is annoying as it just stops the sync... |
|
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! |
|
I have the same issue, usually it's a single, rather random file (e.g. some file last modified 2 months ago)... |
|
I have had same or similar errors. I suspect that in my case, the problem could be related to editing metadata of selected photos. Reconstruction of what I did, if anyone is interested on:
From this point on the issues with the synchronization started, first with the error message "Can't update non-existing placeholder info" for mentioned photos, but also with never closing file download process messages or also with remaining status bars on the Windows Explorer for long since completely downloaded files - the whole synchronization mechanism apparently didn't quite cope with the situation anymore. I solved the problems by moving away the mentioned modified files, which, by the way, were easy to recognize by their status with the two blue arrows pointing in opposite directions (sync pending?), in order to move them back after a short waiting period to assure that the synchronization of the moving outside step had been completed. My environment: Debian Sid (Testing V12, Bookworm); Redis Server 7.0.5; MariaDB 10.5.12; STUN/TURN Server (coTURN) 4.5.2 'dan Eider'; PHP 8.0.24; NGINX 1.23.1; Nextcloud Server 25.0.0.18; Nextcloud Desktop Client V3.6.1 on Windows 10.0.19045 There is also the following open issue, which has similarities with the case described here: [Bug]: Couldn't convert to placeholder #4401. It may well be that this error is a rare corner case, but I think it would be good if someone from the development team (@mgallien, @allexzander, @claucambra) would briefly look into this. Best regards. |
|
I have the same issue with a 2gig video, altough the video uploads correctly, I still have the error msg on the client. Nextcloud 25 version. |
|
yes I have the same issue, please fix |
|
I got this error for hundreds of files when I replaced them with identical files containing older timestamps than the previously synced files. |
|
Seems this and the related Bug are automatically closed because no one cared to solve it. |
|
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
|
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
|
if I get it, this bug is known and will eventually get a fix so let's reopen |
|
I have the same issue. A fix would be great! |
|
I have seen some pattern in this. When dragging a folder to nextcloud folder, and a windows want's an "folder exists, do you want to merge" to happen ... if you choose yes and replace existing files - sync is OK, if you choose to skip existing files, the error Can't update non existing placeholder info results. |
|
Experiencing the same with: the error logs on the server are not realy conclusive |
|
Experiencing the same with: clientVersion=3.8.1stable-Win64 (build 20230419) uninstallation, installation of the client doesnt fix the issue Any update, workaround ? |
|
We have the same issues with some windows clients. client= 3.9.0 |
|
Same here with Server = 26.0.3 / Client 3.9.0.20230613 Real nasty - houndreds of lines with
|
|
In our case, the NC client has errors, but the data was synced to the NC Server successfully We found a workaround In the Nextcloud client : 1 Re-add the same account that encountered the issue At this point, the "new" account in the new folder will have the new data synced without the error |
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes nextcloud#4274
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes nextcloud#4274 Signed-off-by: Dries Mys <[email protected]>
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes nextcloud#4274 Signed-off-by: Dries Mys <[email protected]>
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes nextcloud#4274 Signed-off-by: Dries Mys <[email protected]>
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes nextcloud#4274 Signed-off-by: Dries Mys <[email protected]>
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes nextcloud#4274 Signed-off-by: Dries Mys <[email protected]>
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes nextcloud#4274 Signed-off-by: Dries Mys <[email protected]>
When replacing an OnlineOnly file by another one, the file maintains it OnlineOnly pin state, but it is converted to a regular file. So, the dehydration should convert the regular file to a (dehydrated) placeholder instead of trying to update the (non-existing) placeholder. Closes #4274 Signed-off-by: Dries Mys <[email protected]>
|
Having this issue on latest stable version on W11 |
|
Latest Release, still this error occurs. |
|
@alexx-ftw This was releaed in v3.10.0 (#5890) and v3.9.1 (via a backport: #5906). If you're still experiencing this it's a different or additional issue. Please open a dedicated issue. |
|
fresh installation, win11 and not VFS folder with all the files from previous cloud solution.
|
and others
Expected behavior
That the client will synchronize without error message.
Actual behavior
Well, yes. It just doesn't. Displays the message for multiple files and freezes.
Steps to reproduce
Not known
Client configuration
Client version: 3.4.2
Operating system: Windows 11
OS language: German
Client installation path: Standard
Server configuration
Nextcloud version: 23.0.0 (according to server version display)
Storage backend (external storage): No
Logs
The text was updated successfully, but these errors were encountered: