Sync Service App

[Socorro Henson]

Forthe last 2 days my phone displays a notification, which says "Explore Sync Service" and nothing else. It cannot be dismissed, and when I tap it, the Garmin Explore app starts, and the notification disappears, but reappears as soon as I close the app. What does this notification mean and how do I get rid of it?

I cannot find a "Device Connectivity" setting, which is mentioned in point 7, so I'm not sure if the guide from the Connect app applies to the Explore app. Anyway, I'll try to fiddle with the other Notification settings for the Explore app and see if it makes any difference.

Another thing that bugs me is that this guide is quite old. I've been using the Explore app for over a year, and this issue appeared just a couple of days ago, and I haven't changed any settings recently, and another thing that I noticed is that Connect stopped sending notifications to my watch at about the same time. I already tried restarting the phone, and even updated the Explore app today in the morning, but it did not help. All this makes me wonder if there's perhaps a deeper issue with the Explore/Connect/Android combination.

I initially thought that I had disabled some Explore notifications, but now I checked and i have enabled all, but i do not get this notifications that you mentioned. On which version of Explore are you? I am on Version 3.3.3 currently.

I ended up turning off all notifications for the Explore app, and now the "Explore Sync Service" notification is gone. I'm assuming that other notifications from the Explore app will be suppressed as well, but I don't care.

Garmin Explore runs in the background so that you can stay connected with key features such as smart notifications and weather on your Garmin device. It also enables your phone to automatically sync data from your device to your Garmin Explore account.

So does Garmin Connect. And yet Garmin Connect does not display such notification. There are several apps on my phone running in the background, and Garmin Explore seems to be the only one that causes such problems.

Most of the times my computer is getting extremely slow. I open my task manager and I see Wd Sync Service with 100% cpu usage. In the windows (Windows 10) tray icon is no information that a sync is occurring. I can only solve this restarting the service.

Can anyone tell me how can i get to the source of the problem? Or anyone experience some problems like this?

Thank you

I too am a facing the same issue with the WD sync service consuming all the CPU and pushing it to 100% utilization.

This happening when a file is actually syncing still makes sense, but this remains full all the time.

Tried to reinstall the application as well. That too did not help.

For no known reason the WD Sync spikes the processor to nearly 100%, and the fan goes crazy and it gets very hot. It is the ONLY app running, and I do not use the WD MyCloud as a backup drive. I use it as a media drive, and mainly for other equipment to use (AVR system, DVD/Bluray player, files for iPad to access, etc)

I am having the same issue as well. I have a Microsoft Surface Book and WD Sync is jumping from 50-100% CPU time and I am backing up very little. Any suggestions from WD would be appreciated. Thanks, LTK

This worked for me as it appears my issue was the executable was getting stuck in a loop causing the high CPU usage and restarting it cleared it up and once restarted it worked fine syncing my files as normal and sitting idle at 0% when not syncing. It will pole every few seconds or so but just very briefly and CPU usage below 5%. That appears to be the norm.

Naturally, I restarted the service in task manager, with no change.

Then I wanted to perform the step 1 given by gjb in above post, but I realized that clicking WD sync had only one option Help and there was no way to pause syncing or look at details.

The, I looked at sync files and it appeared that the last sync files are 0.5 year old!

WD sync reinstallation and reconfiguration worked and the processor usage is small and the files are synced.

If I try to disable this function it says "Are you sure you want to disable the persistent notification? This may lead to loss of connectivity to your device". Have you had any connectivity issues with this function disabled?

So if anyone wants to figure this notification thing that won't let you remove or swipe it away (like when taking screenshots of the lock screen!!) and it's bothering you here are some ideas to help you through it. (P.S. I'm nowhere near calling myself an admin just kinda figured this out on my own...

It seems that Fitbit wants to mentally mess with us, you can either turn off the weird notification /sync page notification that stays on each day while on the lock screen or you can keep the notifications and get rid of the "keep alive widget" as mentioned above but it looks like you can't do both, which, in turn, bothers me because it would be good to have that as a separate setting in the section...

For those who want to have notifications on and but turn off "keep-alive" (which allows communications and does the background syncing, albeit without syncing any new info or syncing very often). please follow the next few answers...

I started using VSCode Insiders and wanted to sync my Stable version extensions to Insider. According to the official documentation, I need to select "Stable" as the sync service. However I didn't notice this the first time I started Settings Sync and chose "Insiders". I cannot find how to change this to "Stable" in Settings/VSCode Command Palette; logout and re-login doesn't work; reinstalling VSCode Insiders doesn't work.

Also there is a minor typo in the archlinux-keyring-wkd-sync.service in ConditionFileIsExecutable and ExecStart. The path: /usr/bin//archlinux-keyring-wkd-sync is happily executed and the typo makes no difference here, wondered why.

What's odd, there is no different output of archlinux-keyring-wkd-sync no matter how often it is invoked via systemd timer or manually. Does this seem right to you?

I had the impression, after refreshing certain keys, that those keys would be skipped and the process of keyring synchronization would end quicker.

My current theory for Salkay's situation would be that the timer hits before the network is up and that causes the error w/ a bogus status - nothing in #3 suggests any problem w/ the key or keyserver or Salkay's configuration.

I wonder if that was just a random network error. I suspect you are correct, and it's a network issue that is causing most of the errors. I do use a VPN, so perhaps it just takes a little while to establish network, which sometimes causes issues for the service.

The error messages should output the IP for the failing refresh so we can confirm it isn't part of a block that is in iptables. With many of the Arch servers spread all over the world, and part of IP blocks that in the past have been suspect within RIPE or other bodies, that would be helpful.

It's to combat all the "Q: helps, update failed!!! / A: pacman -Sy archlinux-keyring; pacman -Syu" situations.

You're better off w/ the script "failing" on individual keys (typically because of local flaky network) and have them hopefully just sanitized than running into the keyring errors whenever you occasionally update. But you can mask it and then just remember to pre-update the keyring when you get related failures.

So, for some reason searching the forums for "archlinux-keyring-wkd-sync" returned no results, but with in internet search engine I found this thread. On this machine "archlinux-keyring-wkd-sync.service" has been failing for a few days now, and executing it manually reveals:

It's not the last entry that fails (tpke...@archlinux.org's key refreshed successfully). $error is a counter for the number of failed "key refresh" iterations. Your patch hides the actual error count from the main script so it always exits with the initial error=0:

Gaah, I should've known this would've been to easy :-) So, yeah...disregard that diff then. Still, I feel " break" would be more appropriate then, or a more descriptive error message which key actually failed. With that:

I had the same problem while running "archinstall" to create a new clean archlinux on a new old SSD.

"archinstall" stopped and stayed waiting to finish retrieving the keys... for hours...

And I had some same problems with previous installations of some packages, from AUR or not...

PS: my full gpg.conf for pacman.

I commented the ubuntu keyserver as I think it is not the place to put this instruction

and that could limit the keyservers where keys will be search... Will see...

The Microsoft Entra Connect synchronization services (Microsoft Entra Connect Sync) is a main component of Microsoft Entra Connect. It takes care of all the operations that are related to synchronize identity data between your on-premises environment and Microsoft Entra ID. Microsoft Entra Connect Sync is the successor of DirSync and Azure AD Sync.

This topic is the home for Microsoft Entra Connect Sync (also called sync engine) and lists links to all other topics related to it. For links to Microsoft Entra Connect, see Integrating your on-premises identities with Microsoft Entra ID.

The sync service consists of two components, the on-premises Microsoft Entra Connect Sync component and the service side in Microsoft Entra ID called Microsoft Entra Connect Sync service.

Microsoft Entra Connect cloud sync is a new offering from Microsoft designed to meet and accomplish your hybrid identity goals for synchronization of users, groups, and contacts to Microsoft Entra ID. It accomplishes this by using the Microsoft Entra cloud provisioning agent instead of the Microsoft Entra Connect application. Microsoft Entra Connect cloud sync is replacing Microsoft Entra Connect Sync, which will be retired after cloud sync has full functional parity with Microsoft Entra Connect Sync. The remainder of this article is about Microsoft Entra Connect Sync, but we encourage customers to review the features and advantages of cloud sync before deploying Microsoft Entra Connect Sync.

3a8082e126