You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I discovered that some files weren't synchronized. I can't say for sure if this problem was introduced with the latest client, version 3.15.3, or before. I tried various measure to solve this problem, but all of them failed. I then deleted the sync journal and tried again. The problem persists
Steps to reproduce
I the problem reoccurs on the production system, but I can't reproduce it on a test installation.
The log file says:
2025-03-06 17:35:08:052 [ info nextcloud.sync.discovery /usr/src/debug/nextcloud-client/nextcloud-client/src/libsync/discovery.cpp:553 ]: "Processing \"B*.pdf\" | (db/local/remote) | valid: false/true/false | mtime: 0/1741276452/0 | size: 0/3090179/0 | etag: \"\"//\"\" | checksum: \"\"//\"\" | perm: \"\"//\"\" | fileid: \"\"//\"\" | type: CSyncEnums::ItemTypeSkip/CSyncEnums::ItemTypeFile/CSyncEnums::ItemTypeFile | e2ee: false/false | e2eeMangledName: \"\"/\"\" | file lock: not locked// | file lock type: \"\"//\"\" | live photo: false//false | metadata missing: /false/"
2025-03-06 17:35:08:052 [ debug nextcloud.sync.discovery /usr/src/debug/nextcloud-client/nextcloud-client/src/libsync/discovery.cpp:1046 ] [ OCC::ProcessDirectoryJob::processFileAnalyzeLocalInfo ]: File "B*.pdf" - servermodified: false noServerEntry: true
2025-03-06 17:35:08:052 [ info nextcloud.sync.discovery /usr/src/debug/nextcloud-client/nextcloud-client/src/libsync/discovery.cpp:1347 ]: Not a move, no item in db with inode 3719329
2025-03-06 17:35:08:052 [ info nextcloud.sync.discovery /usr/src/debug/nextcloud-client/nextcloud-client/src/libsync/discovery.cpp:1700 ]: discovered "B*.pdf" CSyncEnums::CSYNC_INSTRUCTION_NEW OCC::SyncFileItem::Up CSyncEnums::ItemTypeFile
I redacted the file name because it included the name of applicants.
Expected behavior
The files that weren't syncronized should be syncronized.
Which files are affected by this bug
B*.pdf
Operating system
Linux
Which version of the operating system you are running.
Arch Linux
Package
Distro package manager
Nextcloud Server version
Nextcloud Hub 9 (30.0.6)
Nextcloud Desktop Client version
3.15.3
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Default internal user-backend
LDAP/ Active Directory
SSO - SAML
Other
Nextcloud Server logs
Can't access them. The server is not managed by me.
Additional info
No response
The text was updated successfully, but these errors were encountered:
Bug description
Today I discovered that some files weren't synchronized. I can't say for sure if this problem was introduced with the latest client, version 3.15.3, or before. I tried various measure to solve this problem, but all of them failed. I then deleted the sync journal and tried again. The problem persists
Steps to reproduce
I the problem reoccurs on the production system, but I can't reproduce it on a test installation.
The log file says:
I redacted the file name because it included the name of applicants.
Expected behavior
The files that weren't syncronized should be syncronized.
Which files are affected by this bug
B*.pdf
Operating system
Linux
Which version of the operating system you are running.
Arch Linux
Package
Distro package manager
Nextcloud Server version
Nextcloud Hub 9 (30.0.6)
Nextcloud Desktop Client version
3.15.3
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Can't access them. The server is not managed by me.
Additional info
No response
The text was updated successfully, but these errors were encountered: