Continuous 'Service Exited in system log

I get the following continuously in my system log. Any advice on what it is and how to stop it?


Thanks



Jun 5 16:57:09 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0500-0000-0000-000000000000[2292]): Service exited due to SIGKILL | sent by mds[168]

Jun 5 16:57:12 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0700-0000-0000-000000000000[2286]): Service exited due to SIGKILL | sent by mds[168]

Jun 5 16:57:12 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0700-0000-0000-000000000000[2289]): Service exited due to SIGKILL | sent by mds[168]

Jun 5 16:57:13 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0500-0000-0000-000000000000[2285]): Service exited due to SIGKILL | sent by mds[168]

Jun 5 16:57:13 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0500-0000-0000-000000000000[2291]): Service exited due to SIGKILL | sent by mds[168]

Jun 5 16:57:47 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0600-0000-0000-000000000000[2324]): Service exited due to SIGKILL | sent by mds[168]

Jun 5 16:57:48 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0400-0000-0000-000000000000[2326]): Service exited due to SIGKILL | sent by mds[168]

Jun 5 16:57:49 [MY MAC NAME] com.apple.xpc.launchd[1] (com.apple.mdworker.single.01000000-0400-0000-0000-000000000000[2325]): Service exited due to SIGKILL | sent by mds[168]

MacBook Air 13″, OS X 10.11

Posted on Jun 5, 2020 9:07 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 6, 2021 4:23 PM

This can also occur when migrating from a version of OS X/MacOS that didn't require signed mdimporters (usually provided by apps claiming file name suffixes). They'd be found in /Library/Spotlight/ and they can be deleted by sudo from someone with administrator access. Like throwing a switch and those messages stop in the system log.


Found out by forcing a Spotlight re-index and got a pop-up message saying the UID mdworker.shared.0A000000-0500-0000-0000-000000000000 or so, the second numerical field would be a volume that can't be scanned by an unsigned mdimporter and the process gets killed (too fast for you to get the identifying info in the Activity Monitor).


The one I recall adding in Mavericks was epub.mdimporter (an archive). Managed to pass all the way through the Migration Assistant for Big Sur 11.1 (on a Macbook Air M1).


Getting rid of the messages made my day.


Similar questions

144 replies

Sep 22, 2020 2:53 AM in response to tholu

Yea guy's i'm super surprised to.

I'm sure it's not only some of us who have this. It's everyone people just don't know it happen.

It is only us geeks who goes into logs and stuff who notices this.

Normal people don't know this and just use there Mac's but i'm also sure if this keeps doing this in the background. It slows things down.

So yes we need to tell Apple every 2 weeks otherwise they don't mind i think.

It would have been fixed long time ago if they did. Think about about it. Now also in Big Sur ???? What

Sep 22, 2020 9:49 PM in response to CAW68

CAW68 wrote:

Having this same issue which is causing frequent slow downs, beach balling, crashes (especially in Lightroom). Having big issues with Lightroom--drains battery faster than ever before and will go black in the middle of working in the program.
Read through the replies and ran EtraCheck. Could someone give me some input based on my report, please? I've already deleted some of the files listed in the report such as Flip4Mac, Wacom files, etc.
Thanks,
CAW

Run Disk Utility First Aid on the SSD. I would even run First Aid on the Container which will require you to click on "View" within Disk Utility and selecting "Show All Devices" so that the Container and the physical drive appear on the left pane of Disk Utility so you can select the Container. Even if First Aid shows everything as "Ok" click on "Details" and look to see whether there are any unfixed errors. If there are any unfixed errors, then you need to backup the drive and erase it to put down a fresh file system before restoring the backup.


See if your laptop qualifies for this free Apple SSD repair program:

https://support.apple.com/13-inch-macbook-pro-solid-state-drive-service


FYI, here is the current list of the publicly acknowledged free repair programs for various Apple products (some products such as your laptop have multiple programs available):

https://support.apple.com/service-programs

Sep 23, 2020 3:58 PM in response to Ifestos

I can confirm this is still happening on Big Sur Beta 8.


I used dtruss to get a bit more info


sudo dtruss -n mds


 ...

 2800/0xe4de:  open_nocancel("/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Resources\0", 0x1100004, 0x0)		 = 6 0
 2800/0xe4de:  fstatfs64(0x6, 0x70000CACAC78, 0x0)		 = 0 0
 2800/0xe4de:  getdirentries64(0x6, 0x7FC60C026C00, 0x0)		 = 2080 0
 2800/0xe4eb:  workq_kernreturn(0x100, 0x70000CBD3B80, 0x1)		 = 0 Err#-2
 2800/0xe4ec:  workq_kernreturn(0x100, 0x70000CC56B80, 0x1)		 = 0 Err#-2
  263/0xe157:  workq_kernreturn(0x100, 0x700003378B80, 0x1)		 = 0 Err#-2
 2800/0xe4e9:  read(0x5, "\002\0", 0x23FE0)		 = 2152 0


The last line is where the mds process crashes with SIGSEGV for me, repeatedly.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Continuous 'Service Exited in system log

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.