![]() ![]() Or for longer, use three backticks above and below the code snippet: longer Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces: example In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. If you’re running a business, paid support can be accessed via where we can ensure your business keeps running smoothly. 18:43:48:694 : Last exec affected 0 is for home/non-enterprise users. ![]() 18:43:48:694 : SQL exec "DELETE FROM flags WHERE path != '' AND path NOT IN (SELECT path from metadata) " 18:43:48:694 : SQL exec "SELECT path FROM conflicts" 18:43:48:692 : PropagateRootDirectory::slotSubJobsFinished emit finished OCC::SyncFileItem::NormalError 18:43:48:692 : OCC::SyncFileItem::NormalError slotSubJobsFinished OCC::PropagatorJob::Running pending uploads 0 subjobs state OCC::PropagatorJob::Finished 18:43:48:692 : PropagateDirectory::slotFirstJobFinished emit finished OCC::SyncFileItem::NormalError 18:43:48:692 :Ğrror successfully added to the notification list: "Cannot sync due to invalid modification time" 18:43:48:692 : Item "Documents" retrieved resulted in error "Cannot sync due to invalid modification time" 18:43:48:692 : Item "Documents" retrieved resulted in "Cannot sync due to invalid modification time" 18:43:48:692 : Item completed "Documents" OCC::SyncFileItem::NormalError CSyncEnums::CSYNC_INSTRUCTION_ERROR 18:43:48:692 :Ĝould not complete propagation of "Documents" by OCC::PropagateIgnoreJob(0x19f124febe0) with status OCC::SyncFileItem::NormalError and error: "Cannot sync due to invalid modification time" 18:43:48:692 : Starting CSyncEnums::CSYNC_INSTRUCTION_ERROR propagation of "Documents" by OCC::PropagateIgnoreJob(0x19f124febe0) Here're the log lines from Desktop Client that appear to point to the issue: click Leaving this at it today, perhaps tomorrow someone will find a solution. No way to solve this error with the sh files provided by Nextcloud so far. However, I don't know why this resulted in a broken timestamp on Nextcloud's database, and I don't know why it cannot get the correct one from the filesystem, since it is all there and correct.Īlso tested solvable_files.sh with list argument, but no output/no files detected. I usually never do this (always remove the files on harddisk and let it sync). I assume this happened because I deleted a single photo through the web app today. Deleting trash on the server for this user does not workĪtm.Rescanning the whole folder ( sudo -u www-data php occ files:scan -path "user/files/Documents") does not work (error persists), same with files:scan -all.It is really making me stop recommending this (potentially) amazing product to anyone.ĭrwxr-xr-x 39 www-data www-data 49 08:31:30.803407858 +0100 Documents I am spending hours on trying to move files, rescan them, whatever. I can see that it had ruined many people's files back in 2021 īut I am not sure if I was using the same instance back then. Qt version used by client package (Linux only, see also Settings dialog):Ĭlient package (From Nextcloud or distro) (Linux only): Wait a few months, it eventually starts corrupting your files.Fill up your nextcloud instance with terabytes of files.It should be able to sync files with no issues Actual behaviourĬomplains about invalid modification time while basically everything else works perfectly with the same files Steps to reproduce Subscribe to receive notifications on status change and new comments.It's just extra noise for everyone subscribed to this issue. Please don't comment if you have no relevant information to add.Please use the □ reaction to show that you are affected by the same issue. ![]()
0 Comments
Leave a Reply. |