Continuous 'Service Exited in system log

I was working on troubleshooting a different problem when I came across this thread. Thank god I did because disabling Spotlight on my 2016 MacBook Pro just stopped the system log from incrementing, cooled my laptop way down and quieted the fan, and the battery life has been massively better. Night and day.

I kind of like the Spotlight feature though so I hope they fix this.

I have this issue as well on a Mac mini running Catalina 10.15.6. I believe it's related to issues I've had with mouse jerkiness and lag. I can't say for 100% but when I've run with Spotlight disabled I hve not seen the jerkiness. It's unfortunate becasue Spotlight is a great feature.

I tried a variety of suggestions and then went into the Spotlight Preferences and turned off all the checkboxes in the Search Results tab.

Now, instead of getting 5 of these per second in the System Log, I'm getting about 1 per minute.

Now I'm seeing another odd one.

error 15:36:38.154385-0700 mdworker_shared All kCFPreferencesCurrentUser domains in this process will be volatile, because homeDirPath starts with /var/empty

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

I'm getting the same thing.

Aug 24 07:23:29 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0000-0000-0000-000000000000[42259]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:23:29 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[42261]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:24:44 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0000-0000-0000-000000000000[42266]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:24:56 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0000-0000-0000-000000000000[42272]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:25:02 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.mail.01000000-0000-0000-0000-000000000000[42270]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:25:02 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.mail.06000000-0000-0000-0000-000000000000[42269]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:25:02 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.mail.03000000-0000-0000-0000-000000000000[42268]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:25:02 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.mail.02000000-0000-0000-0000-000000000000[42271]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:25:40 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[42273]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:26:45 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[42279]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:27:44 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[42284]): Service exited due to SIGKILL | sent by mds[94]

Aug 24 07:30:12 static-27-96-67-159 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[42290]): Service exited due to SIGKILL | sent by mds[94]

I opened a case with Apple and they said it was normal and not anything to worry about. I don't understand that, since it seems to be killing the mdworker indexing process every few seconds.

I'm having the same issue since Big Sur Developer Beta 7. I disabled Spotlight after disabling SIP by doing:

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

The constant crashes did not allow to use mdutil to disable the Spotlight indexing.

I also submitted some feedback to Apple about it in FB8725224.

Good to contacted Apple with feedback. Now it's hilarious. It's been going one on the last many builds.

Crazy and now in Big Sur as well. That *****

I also disabled anything Spotlight and it's gone so for sure that's the problem.

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

The SIGSEGV prevented Spotlight from working at all, while it is happily reindexing now I noticed the SIGKILLs. This could just be a way how mds communicates with its workers and thus not necessarily be a bug, if everything else works.

Turned out that the reason of multiple mdworker.shared.xxxx sigkills was qualys cloud agent. Uninstalled - 'sudo /Applications/QualysCloudAgent.app/Contents/MacOS/qagent_uninstall.sh', errors gone. BUT: I rebought my MacBookPro from ex-employer, so had all rights to do it, for some people it might be not an option.

P.S. The reason I ever looked in system log was an annoying sound card muffling after some 10-15 seconds of playing. Decided to see what's happening in my system, found mdworker.shared.xxxx errors, eliminated, sound muffling gone with it...

Have the same errors with my brand new MacBook Air. Saw some references to Office 360, I'm also running that. But the problem I have is that MacOS tells me there's a Software Update, I choose to download and install, it starts, but just never gets there, at some time aborts and is back at the notification in System Preferences saying there's an Update available. At this point I try to use Safari - to search the error message, for example - and nothing, it doesn't even start connecting to the internet. Have to reboot.

Hi. I am new to this forum. I am seeing this in my activities monitor. I Know I have a virus on my computer that keeps re directing my browser to "bing" and I am trying to stop it. I belive I accidentally uploaded this virus while updating adobe flash or acrobat. I believe the ap it is disguising it self as is "common business" I have deleted & uninstalled this ap and it is right back on my computer. The parent process seems to be this "launchd (1)" . Now that being said, I know nothing about computers and how they process, so I may have this all wrong?!? But if anyone knows please chime in!!! Thanks so much.

Because of this there is a substantial decrease of battery hours. Hence it's good to fix

Opening Console stops the battery drain? How is that. It uses a lot of energy tracking all the messages.

If you don't open it, there is no query for the logs.

Lol I thought you were kidding with your response. But you are truly clueless.

Opening console or not, those exited process are happening in the background. Those failed tasks belong to Spotlight. It continuously trying to index something but abruptly killed. It keeps trying to index the files every few minutes. It uses several workers that you can check in activity monitor under mdworker name, it can have more than 2 processes. These continuous failed attempts to index the files in the background that drains your battery more.

I see this as well including when I have closed my lid while on power adapter.

I see about 100 such errors every hour, 24 hours a day if the macbook is on power adapter.

My laptop also gets really warm while closed and on power adapter. I suspect it is this error which suggests it is running things and causing my laptop to be warm while closed.

I have unticked 'Prevent computer from sleeping automatically when the display is off' and disabled power nap in power settings.