Continuous 'Service Exited in system log

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).

j.nerdy wrote:

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).

If you post the EtreCheck report here the regular contributors can analyze the report for you to point out software that is known to cause problems. The EtreCheck report only checks to make sure the software is "legit" and does not provide information about the quality of the apps since that is more subjective and the developer of EtreCheck would be sued. While EtreCheck will show anti-virus apps and cleaning apps as "OK" this means they are from a "legitimate" developer and are not technically considered malware although some are considered as such by some of the regular contributors here. AV & cleaning apps typically cause more problems than they solve and usually interfere with other apps and impact performance.

@HWTech, thank you.

I do not use any cleaning apps, nor use any AV packages. I believe that in my case that it is due to a kext issue with my ThunderBay and softraid driver. I have it mounted as an SMB share with another server and the handshake seems to be causing an issue.

Should that be the case I will update my post.

Again, many thanks

aokubo wrote:

<beach balling and etre check report--please help.log>

Try uninstalling Webroot by following the developer's instructions. Anti-virus and third party security products are not needed on a Mac and they usually cause more problems than they solve. Plus they impact system performance. If the AV software is required by your school or employer, then contact your school/employer for assistance in troubleshooting your issue.

Also make sure your Seagate software is up to date. Instead of installing the third party proprietary software for managing your external drive you should have initially had macOS configure and manage the external drive. Third party proprietary drivers for external drives can cause problems especially when an OS update is installed.

It may also help if you can provide us a copy of the Kernel Panic log(s). Launch the Console app and look in the folders on the left pane of the Console app with names similar to: "Diagnostic Reports", "System Reports", "/var/log", or "/private/var/log". I'm sorry I cannot be more specific, but Apple has changed their locations a few times over the years. The Kernel Panic file name will begin with "kernel" and end in ".panic". If you more than one Kernel Panic log, then attach several of the most recent ones. Attach the logs in the same manner you attached the EtreCheck report.

The Spotlight errors concern me since they appear to be possible memory related errors, but until Webroot is uninstalled it is to hard to tell for certain.

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.

Count me in.

The same log error all over

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0100-0000-0000-000000000000[1364]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0700-0000-0000-000000000000[1361]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0100-0000-0000-000000000000[1358]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0600-0000-0000-000000000000[1363]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0700-0000-0000-000000000000[1362]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0000-0000-0000-000000000000[1367]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0300-0000-0000-000000000000[1359]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:04 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0100-0000-0000-000000000000[1368]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:05 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0100-0000-0000-000000000000[1369]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:05 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0100-0000-0000-000000000000[1371]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:05 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0200-0000-0000-000000000000[1370]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:05 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0600-0000-0000-000000000000[1372]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:05 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0300-0000-0000-000000000000[1374]): Service exited due to SIGKILL | sent by mds[115]

Jun 10 16:04:05 MBA13-2020 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0700-0000-0000-000000000000[1373]): Service exited due to SIGKILL | sent by mds[115]

I'm sure this started after 10.15.5, i never saw it under 10.15.4 !

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

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.

Thats what i found out too.

Turn off spotlight and it stops. The thing is. If you have spotlight on.

It never stops writing that log. It keeps going 24/7 :( not exactly nice.

The message is harmless as you say. But it must use lot of system resources

to keep doing that over and over ?

I just found out something else.

I though it was only 10.15.5+ related but it's not.

I updated both my Macbook Pro's the same day. One with Catalina 10.15.4 and one with 10.14.6

and both my Mac's do this now.

So i think it's a combination of 10.15.5 update and the Security Update 2020-003 for Mojave.

Why else would both my Mojave and Catalina now do this and not only the 10.15.5 ? Only way.

Some of the changed things in 10.15.5+ is also in the Security Update 2020-003 for Mojave.

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.

I wonder whether this is related to regular crashes I have when using my MBP in clamshell mode. The last messages I get in system.log are those spotlight kill messages. After that, the system will just lock up and need a cold start.

Ok today the new Security Update 2020-004 for Mojave and 10.15.6 came out.

I updated both on my 2 Macbook Pros one running Cataline and another running Mojave

and this still goes on. They didn't fix it in either of them :(

System log still running crazy 24/7 if you have Spotlight active. Turn Spotlight completely off and it goes away as before.

It have to take some system resources and battery so my Spotlight is off, totally. Sucks.

Jul 16 01:58:06 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0000-0000-0000-000000000000[1130]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:06 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0000-0000-0000-000000000000[1142]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:06 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0000-0000-0000-000000000000[1141]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:06 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0000-0000-0000-000000000000[1132]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:06 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0000-0000-0000-000000000000[1134]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:08 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0000-0000-0000-000000000000[1144]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:09 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0000-0000-0000-000000000000[1145]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:09 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0000-0000-0000-000000000000[1143]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:13 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0000-0000-0000-000000000000[1146]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:14 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0000-0000-0000-000000000000[1147]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:14 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0000-0000-0000-000000000000[1148]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:14 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[1149]): Service exited due to SIGKILL | sent by mds[81]

Jul 16 01:58:14 MBPr15-2018 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0F000000-0000-0000-0000-000000000000[1150]): Service exited due to SIGKILL | sent by mds[81]

after reading your post , I did the command below for each of my /Volumes/

mdutil -vEsa -i on -d /Volumes/Google\ Chrome/

mdutil -vEsa -i on -d /Volumes/VolumeName1

mdutil -vEsa -i on -d /Volumes/VolumeName1

issue seems to be resolved, will monitor for days though.

I'm not particularly familiar with mdutil.

I tried

sudo mdutil -vEsa -i on -d /Volumes/Macintosh\ HD

but I get lots of errors

2020-07-23 17:29:23.588 mdutil[250:1286543] mdutil disabling Spotlight: / -> kMDConfigSearchLevelOff

Error: unable to perform operation. (-405)

Error: invalid operation.

Error: unknown indexing state.

and then

/System/Volumes/Data:

2020-07-23 17:29:23.786 mdutil[250:1286543] mdutil disabling Spotlight: /System/Volumes/Data -> kMDConfigSearchLevelOff

Indexing and searching disabled.

So I'm not 100% sure what the right invocation would be