• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 12 December 2024 It's Lightroom update time again! See What’s New in Lightroom Classic 14.1, Mobile & Desktop (December 2024)? for Feature updates, new cameras and lenses, and bug fixes.

Sync Sync issues: I went from 4,800 stuck images to zero to one and I want Adobe to listen

Status
Not open for further replies.

atolkachev

Member
Joined
Mar 21, 2020
Messages
88
Lightroom Version Number
13.5.1
Operating System
  1. macOS 14 Sonoma
I should be taking this to Adobe, but I think most of you know how their support forums are. I believe they are paying attention to this forum, and I feel there are enough people here who know at least as much about troubleshooting LrC, and certainly seem to care more.

I have posted in several threads on my sync issues, which started before 13.3 and got progressively worse under 13.4 and 13.5. At the height, I had 4,800+ images stuck. LrC never let my MacBook go to sleep (I have Prevent system sleep during sync ON), the laptop was always hot, memory and threads used by LrC were always goin up, etc. When checking the Sync status on the web, I was seeing 900+ broken files, all with a message to open LrC to compete sync. The discrepancy between web and LrC numbers of stuck files was not encouraging, either.

Having failed (and having been warned that I would fail) to improve the situation by first clicking Rebuild Sync Data and then deleting the lrsync.data file, I decided to fix the issue manually.

Thanks to Adobe for bringing back the Sync Activity grid in 13.5 (I think). When they had removed it in 13.4 (I think), that stunk of desperation mixed with arrogance: "Nothing to see here, move on!"

I scrolled through the Sync Activity grid and identified large chunks of failed uploads. Thank goodness for my 3-4-year old practice of renaming (in PhotoMechanic) of all ingested files to something meaningful like 20240905 NHS Cheer v Pacifica 0504.JPG prior to culling and importing into LrC. Because of that, swaths of pending files stuck out visually. The only thing that would have been better is if Adobe made the grid sortable by file name, because I could spot 30 files from a shoot stuck here and 50 from the same shoot there. Sorting by file name would have made file name patterns easier to see.

If I saw a shoot where 50+ files were listed as stuck, I ruthlessly unsynced the entire shoot gallery. I found it necessary to also remove the files from the All Synced Photographs collection at the top of LrC catalog. It was more important to me to wipe the slate clean than to retain any given file (or 1000) in the cloud. I figured I can try syncing them again later, and I will.

The numbers of stuck files started going down. I ended up unsyncing about 7000 photos. Most of these were from August-September of this year. Some of them HAD synced to the cloud, but there were strange gaps, some of which were almost explainable. Like, in a gallery of 500 images, 50 had synced to the cloud, and it just happens to be that those 50 had ratings or pick flag (game highlights as it were). Now, if you think I had not tried applying ratings, flags, color flags and even minor edits to the remaining 450 to help them along, I had. This hack was working a month or so ago, but eventually stopped helping.

All told, I unsynced about 10 galleries with about 7000 photos. Many successfully synced files have been removed from the cloud, but at the same time, the unsynced files were removed from the queue. Now my stuck file count was down to about 500 and encouragingly the counts in LrC and on the web in the Sync Issues query were the same.

Having gone through all large swaths of stuck files identifiable visually in the Sync Activities grid, I also found a few dozen files that resided on my removable drive, which I had connected for this project. These had a warning about metadata not having been written something or another. I chose the resolution option without fully understanding or caring, and these, too, dropped off the stuck report.

I spent the next two hours switching from Sync Activity in LrC to Sync Issues on the web going almost file by file (or five files or ten if I could detect a pattern in the unsorted list) and removing them all from synced galleries as well as from All Synced Photographs.

For a subset of photos based on how much I cared and was getting tired/impatient, I simply deleted them on the web using check boxed and delete button in the Sync Issues gallery.

This process eventually emptied out Sync Issues on the web and turned the sync status green in LrC.

I then imported and synced my latest shoot: a 600 and a 300 photo galleries. After a period of Develop module unresponsiveness and bugginess, which is lately associated with every medium size import or bigger, all photos synced to the cloud within reasonable time, greatly improved from pre-13.3 when sync could take a day or longer.

I went through the 300-image gallery copying and pasting develop settings for a consistent looks, fixing cropping and exposure. At the end, the coveted green checkbox turned to the dreaded blue circle with the "Syncing 1 photo" message (or "Uploading 1 photo" pop-up). This photos has been "uploading" for the past 12 hours.

All my troubles started with the "Syncing 1 photo" months ago. So, this time I am not taking it. I tried removed the stuck photo from the synced gallery and All Synced Photos. That turns the checkbox green. Re-adding the photo to the synced gallery again gets it stuck. I could remove it from the catalog and reimport, but first I want to report the exact issue and see if Adobe (or anyone here with the next level of understanding of the sync process) can identify the issue which may FINALLY lead to the fix. Here is the issue:

Binary Uploader​

  • chunkFileAtSize: 5242880
  • chunkSize: 5242880
  • needsBinaryUpload:
    • 1:
      • _id: fc4aa9fd2ab14519a5256e825ea9accc
      • binaryType: xmp_develop
      • captureDate: 2024-09-05T21:41:00-07:00
      • fileName: 20240905 NHS Cheer v Pacifica 0504.JPG
      • fileSize: 5590
      • isReadyToUpload: 0
      • typeSubtype: asset/image
    • 2:
      • _id: fc4aa9fd2ab14519a5256e825ea9accc
      • binaryType: proxy
      • captureDate: 2024-09-05T21:41:00-07:00
      • fileName: 20240905 NHS Cheer v Pacifica 0504.JPG
      • fileSize: 618232
      • isReadyToUpload: 0
      • typeSubtype: asset/image
  • numberOfScheduledBinaryUploads: 0
  • recentErrors:

I have attached the log file renamed to TXT as @Victoria Bampton had requested the last time she tried helping with my sync issues. Yesterday, this report was absolutely clean, something I had never seen in my life -- probably because there is no reason to generate it when sync is working. Today, there is one error. This should help crystalize troubleshooters' vision. I don't think there is anything I am doing "wrong" or could be doing differently -- except continuously watching the sync status and manually removing stuck files from sync.

Thanks to all who read this far. Hope my approach helps someone clear their sync issues as well as helps direct troubleshooting efforts by those who actually have a chance of fixing them.
 

Attachments

  • lrsync_log.txt
    1.8 MB · Views: 48
Last edited:
One thing worth mentioning is that when we see no progress in the being synced numbers over a period of time with a number we say "xxxx images are stuck". This implies that there are xxxx images with problems. In reality this is usually not the case. Most times one image is stuck and that stuck image is blocking others from being processed. Then, once we get that one stuck image out of the way, things start flowing again till another image gets stuck and clogs the works again.
 
True. I would like to capitalize (?) concentrate (?) on a situation when exactly one image is stuck. Someone should be able to sink their teeth into it, and it may well need to be Adobe. Otherwise, I will just keep removing or reimporting stuck images and will grow bitter and jaded in the process.
 
Yeah, the old sync process was problematic for some folks. Adobe, I guess, got tired of dealing with stuck images issues and decided to re-architect the sync process in order to make it less prone to problems. It seems they were pretty confident that they had succeeded as they took out the list of in-process images as with the new structure no one would need that anymore (my opinion). Unfortunatly the new architecture seems to suffer from many of the same problems as the old one did (maybe not the same problems, but the same symptoms).

I do believe that they are putting a significant effort into figuring this out as it is costing them a fair amount of time dealing with customers with stuck images that don't seem to get un-stuck through the normal fixes one finds here and on other sites. But, apparently it is a somewhat thorny problem that so far has only seen imcremental improvements but not a global fix. From this, I infer that there may be multiple techical issuse each of which has to be solved in a different way - and that takes time to both figure out the root cause of each one and then devising/testing a fix.

But, while all that is going on, users wind up with high blood pressure.
 
Honestly, Adobe support needs to get logs on these issues so that Adobe can fix the causes. They went through hundreds of logs between 13.3 and 13.5 and fixed dozens of bugs, which is why 13.5 is much more stable on sync, but there are still going to be some outliers. I suspect most of the remaining issues are coming from photos that were already in the cloud but had some kind of issue that the v1 sync skipped over and v2 is being more strict about.

FWIW, binaryType: aux makes me think it might be an issue with a mask or generative ai remove.
 
I totally understand the point that bugs are obvious when they have been found... (been there myself) ..... but .....

It seems crazy to me that a serious software developer would allow blockage of a single image to be a log jam for the remaining images in a queue for a catalog system that has 100's of thousands of images... especially when this area has been such a critical focus and source of serious pain for so many people.


I am still on 13.1 because I am scared to upgrade.... and successive comforts and messages that " it is working now" have such a hollow ring.

I sense I will be waiting for Ver 14.1 or 14.2 (ie not 14.0) or longer.... so be it.
 
I sense I will be waiting for Ver 14.1 or 14.2 (ie not 14.0) or longer.... so be it.
Be aware that minimum sync version will change to 13.5 sometime this fall... I would imagine sometime between 14.0 and 14.1, so if you want to continue syncing, you'll have to upgrade.
 
Be aware that minimum sync version will change to 13.5 sometime this fall... I would imagine sometime between 14.0 and 14.1, so if you want to continue syncing, you'll have to upgrade.

Very good point and thanks for this head's up.

I am lucky I can (and have removed) synching from my workflow and mindset for the moment. I will manually load low volume travel pics using the web interface if needed.
 
I am still on 13.1 because I am scared to upgrade.... and successive comforts and messages that " it is working now" have such a hollow ring.

You can upgrade to 13.5 and see if you like it. If you don’t you have a 13.1b catalog to fall back on.


Sent from my iPad using Tapatalk
 
All my troubles started with the "Syncing 1 photo" months ago. So, this time I am not taking it. I tried removed the stuck photo from the synced gallery and All Synced Photos. That turns the checkbox green. Re-adding the photo to the synced gallery again gets it stuck. I could remove it from the catalog and reimport, but first I want to report the exact issue and see if Adobe (or anyone here with the next level of understanding of the sync process) can identify the issue which may FINALLY lead to the fix. Here is the issue:
I have had this dreaded problem quite a few times. Mainly it was just 1 photo but sometimes it was 2 or 3 or even more. It usually occurs with photos that I have previously un-synced and then tried to re-synced. I often did this because I had changed the keywords and wanted to sync them to the smart previews in the cloud (an option we dont seem to have anymore, but I digress).

When the sync problem issue occurred I removed the photo(s) from sync (again) and repeated. After further failures I tried all sorts of things. This included deleting smart previews, editing keywords, removing keywords, editing the photo, cropping the photo, renaming the photo, removing the photo from LRc and reimporting and finally saving metadata to file.

The photos would all eventually sync, sometimes after several attempts, and the magical green tick would re-appear. When the photos did eventually sync they only took seconds.

I am really not sure whether any of the things I tried actually resolved the issue. However, the photos did sync immediately after cropping the photo on quite a number of times (but not every time).

Something was obviously blocking the sync and that something magically went away eventually.
 
I totally understand the point that bugs are obvious when they have been found... (been there myself) ..... but .....

It seems crazy to me that a serious software developer would allow blockage of a single image to be a log jam for the remaining images in a queue for a catalog system that has 100's of thousands of images... especially when this area has been such a critical focus and source of serious pain for so many people.


I am still on 13.1 because I am scared to upgrade.... and successive comforts and messages that " it is working now" have such a hollow ring.

I sense I will be waiting for Ver 14.1 or 14.2 (ie not 14.0) or longer.... so be it.
I understand your reluctance. However, once you have made it through the process you will find that syncing is much more responsive and much faster than before, apart from the odd issue as i mentioned in another post above.
 
Rikk,

As an Adobe employee can you create or facilitate a process for people to upload bug reports with log files? It's really in Adobe's interest to get inputs from people in this group.

Phil
 
Rikk,

As an Adobe employee can you create or facilitate a process for people to upload bug reports with log files? It's really in Adobe's interest to get inputs from people in this group.

Phil
Why would I? As @Paul McFarlane replied, the procedure is well-documented, and the Assisted Support Channel is well-equipped to handle this.

I am afraid some will need to get beyond the 'I don't want to have to contact support' mindset. It is harsh-sounding, I know, but it is the way things are.
 
I am afraid some will need to get beyond the 'I don't want to have to contact support' mindset. It is harsh-sounding, I know, but it is the way things are.
I understand but I was trying to "reduce the friction" in reporting a problem. I also hate to be harsh, but sometimes "that's the way things are" impedes innovation and works against long-term corporate goals such as market share, reputation, and even revenue growth
 
I guess the question is whether people want help to solve their issue, in which case they have to go through Support, or whether they want to submit their logs to the engineers for analysis to help them fix bugs. I can see the argument from both sides. The engineers are missing out on seeing logs from advanced users who don't have time to spend hours on the phone with support redoing things they've already done in their own troubleshooting. A form akin to the old "black hole" bug report form could be interesting for the latter group if the engineers considered those additional logs valuable. Still, it could also create a lot of additional work for the engineers if they didn't have an automated way of picking up unusual glitches in the logs.
 
Status
Not open for further replies.
Back
Top