Continuous 'Service Exited in system log

Do u use some kind of virtual disk? For example, mountain duck, Google Drive, Onedrive....?

I have a brand new Macbook Pro 16" running 10.15.5, it is barely one week old and while I have installed Office 365 and it inherited Lightroom from the older Mac, it doesn't have much else installed yet and when I'm not running Office 365, or a browser or email, it's often sitting mostly idle. But I see that same" Service exited due to SIGKILL sent by MDS" in the Log Reports within Console. The computer is exceptionally fast and responsive when asleep, awakening from sleep, running any software. So I don't think the presence of that message is necessarily a clue to something that is wrong.

If you computer is not behaving properly (slow to wake up, fans running high all the time), I would suggest some standard troubleshooting steps such as: SMC reset, creating a new vanilla user to see if the problem repeats under that user, booting into safe mode, run Disk Utility to check file system.

I think this message is harmless. I see it in my logs on a brand new computer. Have you shown any harmful impact on something? Someone can make it go away by shutting down Spotlight, but why do that? You can also make it go away by shutting down your computer! There are many other log messages, this could be an endless project to make them go away. But unless they cause harm to your computer, there is no need.

I can confirm that this problem appeared right after installing Security Update 2020-003 on Mojave 10.14.6

Apart from filling up the system.log this also results in mds_stores running wild keeping the fans on my Mid 2015 MB-Pro running continuously.

It's horrible. I tried rebuilding the Spotlight Index. For the local SSD, this was done in a very short time. However, the index of the TM backup is now also rebuilt. This has been running at just 230GB (on NAS via WLAN) for 3 days and no end in sight. You cannot exclude the TM savings bundle either :-)

Now I've started a new TM backup.

It's exciting to see when there will be a solution here

johndoo_helo wrote:

Just ignore this helpful Barney-15E guy.

By the way, I have done a clean install of Big Sur on my MBP 2017, the issue still appears persistently as soon as the clean install finished (without installing any new apps). I did it after wiping the disk. So this is issue is really weird, haven’t had any working solution yet for me.

What is "the issue" for your situation? Is the computer working ok but you still see the SIGKILL messages? I saw the SIGKILL messages on a brand new Mac.

If you see the SIGKILL messages but the computer runs fine after a disk wipe and clean install, I'd move on and not worry about or be distracted by those SIGKILLs. If your computer is running poorly even after the disk wipe and clean install (fans high, overheating, beach balls ...) then there could be a hardware issue. (What else could it be?)

These were posted June 2020. Now it's March 2021 and the world should have changed by now. Any good reason I'm seeing the same problem? I wasn't getting anything done so I went into spotlight and unticked most all data types. I don't use spotlight anyway so why should I let it mess me up so bad.

Small sample of the log

Mar 20, 2021 at 2:24:30 PM timed[115]: settimeofday({0x60563dde,0x16bf4}) == 0

Mar 20, 2021 at 2:24:32 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:24:59 PM syslogd[66]: ASL Sender Statistics

Mar 20, 2021 at 2:25:09 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:09 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:10 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:25:11 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:50 PM galileod[85]: <FBMegaDumpService: 0x101a058a0>: No dongles connected, cancelling MegaDumps.

Mar 20, 2021 at 2:30:51 PM timed[115]: settimeofday({0x60563f5b,0xaf79}) == 0

Mar 20, 2021 at 2:30:53 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:54 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:54 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:54 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:55 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:55 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:55 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:30:55 PM remindd[14407]: objc[14407]: Class REMCDChangeTrackingState is implemented in both /System/Library/PrivateFrameworks/ReminderKit.framework/Versions/A/ReminderKit and /usr/libexec/remindd. One of the two will be used. Which one is undefined.

Mar 20, 2021 at 2:30:56 PM remindd[14407]: objc[14407]: Class REMDAAccountInfo is implemented in both /System/Library/PrivateFrameworks/CDDataAccess.framework/Frameworks/DACalDAV.framework/Versions/A/DACalDAV (0x7fff89d59360) and /System/Library/PrivateFrameworks/CDDataAccess.framework/Frameworks/DACalDAV.framework/DADaemonCalDAV.bundle/Contents/MacOS/DADaemonCalDAV (0x1057a1948). One of the two will be used. Which one is undefined.

Mar 20, 2021 at 2:31:29 PM com.apple.xpc.launchd[1]: Service exited due to SIGKILL | sent by mds[99]

Mar 20, 2021 at 2:31:29 PM com.apple.xpc.launchd[1]: Service exited du

It sounds like you have other things going on that need to be addressed. When they are, I expect that you won't care about the SIGKILL messages anymore because your Mac will be working fine then. Those messages will still be there, here is from one second in the system log (however this was a particularly busy 1 second internal, sometimes a number of seconds go by with no SIGKILL messages) of a healthy and responsive Mac -

If your network is problematic that can absolutely cause a machine to "hang" or stutter as it retries over and over to re-establish the connection, and of course browsers and email etc. will appear slow or erratic. This entire thread about the SIGKILL messages has diverted a number of people from troubleshooting their problems because they feel that the SIGKILL messages are somehow the cause, which I am convinced is not the case because I see those messages on multiple healthy Macs.

Some have found that killing the MDS process or Spotlight or indexing "fixes" the poor performance, but that is a clue about root cause because Spotlight and indexing works properly and well on maybe 99.99% of Macs. When it does not work, there can be an underlying problem with the disk, the file system, or a custom installation or configuration that interferes. Those are the clues I would follow up[ on.

Go to system preferences and see what has full disk access . I have the same problem and I've been dealing since augustish myself. If there is anything in there that u don't remember giving access to , by physically going in there unlocking ,ticking ,and granting then post what u see . We'll compare I just think I found my demon. hopefully , not not at same time. Its scary

The problem still exists on Big Sur. I would be great to have a more detailed log that explains why Spotlight won't index files and why the threads keep crashing. I've been troubleshooting this for a week.

Disk utility doesn't find any problems

Rebuilding using the GUI - doesn't fix it.

Rebuidling with the mdutil command - doesn't fix it.

At this point I'm going to do a fresh install on my Macbook.

That's normal. It's associated with Spotlight, probably indexing. I have the exact same entries in my system log. It's nothing to be concerned about.

There's nothing in the Console that's intended for the user. It's more for the hardcore software engineers at Apple for diagnostics, etc.

I'm wondering if anybody at Apple is reading these things,

No need to wonder at all. Apple is not here looking for things to fix.

Also, the log entries in and of themselves are not a problem. An excessive number of them seems to be related to third-party software interfering with spotlight.

thank you @HWTech, though I am not looking for assistance. I was just chiming in with a similar experience. FWIW I did use Etrecheck, and it could not identify the runaway process. A kernel task, diagnosticd and suggestd were all suspiciously high, but based on my error... it seems like spotlight is the culprit (at least indexing issues with mdworker).

I decided to re-install, but in the process ended up briefly on base Catalina (no updates).

This problem did not occur.

Went back to 10.15.5 and 10.15.6b2 and it does.

Seems somewhat endemic

I also experimented with exclusions, and addressed some cores I was seeing in /Library/DiagnosticLogs from mds (relating to indexing safari tech preview cache) but the error logs persist.

Surprised this one slipped apple by, and as yet not seen how to avoid.

This will no doubt leech away slightly at resources due to the constant restarting though admittedly the impact seems low for now