Continuous 'Service Exited in system log

That's your way of ignoring things happening.

Nothing is happening to my Mac. I do get some of those messages in the logs, but there is no adverse affect on my Mac.

Focusing on the log entries won't provide any solution. You may be able to find a way to stop it logging those entries, but it won't fix whatever underlying problem you have.

Since I don't have whatever is installed that causes the errors with Spotlight, I have little way of knowing what it might be. You must determine what you have installed that is causing the underlying problems. There is really no way for any of us who do not suffer from the actual problem finding the solution for you. But, we do know that the symptoms are not the cause.

If you go back and look at the original post to which I replied, there is no implication that there is any other problem. It's only a bunch of log entries. I have many of those entries, also, but I have no other problems.

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.

The issue of this mds sigkill that I think it affects my performance.

I notice a little bit of lag (unresponsiveness for 1-2 seconds) periodically. I think it happens every time these mds workers start to work and get killed. And the most noticeable one is the decrease of my battery life (or this is just big sur?? But it’s around 60% of previous performance).

I thought the same that I could have a hardware issue because clean install didn’t help.

Hi. I got the same bug on my new iMac. Only a few weeks of use and this BS pops up in my console and everywhere. Any tips from anyone on how to literally delete this thing!?

Im getting beach balls in every single Apple program, especially finder. It is embarrassing to open anything that is an Apple program on this glorious machine because of how extremely slow the programs are. It might be something wrong with the fusion drive but I have barely messed around with storage options, backups, etc.

I have the iMac 27' 2019 (i5 hexa-core 3,6Ghz - 5Ghz, 16gb ram, Radeon RX580/Radeon Pro 580X, 2tb fusion drive)

I definitely have all of what they are describing up there, the continuous barrage of spotlight running, beachballs,I have repeatedly asked support regarding the inability to update apps etc. With no luck they seem to only agree with what App Store spits out instead of maybe guiding me in the background to find out why. I mean this is the first Mac I have owned, and essentially just began using my Mac more than 2 times a year. So any helpful advice would be great and much appreciated.

Thank you Mr HW Tech

I greatly appreciate your advice and quick response, sorry it has taken me so ,long to get back to the community and to this topic. Yes sir I had no prior experience with apple's way of life and customer support as well as the clandestine operations of keeping guard of their proprietary operating systems. I respect that as a customer and a novice iMac operator. My first phone call to apple support was so complex I'm assuming, they passed me to an engineer. So I will definitely look to that in the future for oddities or continuously running programs. I learned on a hand built slapped together PC with windows XP 2000 professional edition. 🤣 I was use to the extensive detail in the help/support windows. so essentially I went from that when they booted service directly to iMac 2014 Retina 5K. I was definitely shocked by the difference and not expecting that.

But I am constantly coming upon with and finding questions and roadblocks so hopefully y'all can bear with my dumb questions. Thank you again for your concern.

thanks for your interest. Any act does not unravel from sleep giving Sleep Wake failure in EFI (code :: 0xffffffff 0x0000001f). In addition, the dock bar during shutdown does not go down but siblocks in half

I have imac pro. First it doesn't go out, then sometimes it doesn't wake up. I have been in attendance with second level tencinco for two months. We have done everything, We have recently formatted and imported only my user but sometimes he still does not wake up. Now after last two updates, it seems to be fine. There is only the dock that does not descend when closed, it remains blocked in the middle

i don’t understand the conversation here. I think Brecht summarized what I’m seeing, might be seeing the same independently since it isn’t in response to me. Will someone respond with suggestions or potential fixes?

Thank you, you have a lot more ideas than I do and I will follow up, but I only posted because so many SIGKILL commands seems like a problem. Frankly, I think the sluggishness has to do with my WiFi network as much as my machines. I have errors dropping connections. Today it got bad. I had Mac laptop machine working fine, Second machine Mac mini hanging, not finding network. I brought up a terminal and pinged google with about 60% timeouts. I’ll contact Netgear support tomorrow and see what they say. Thanks again for your ideas.

I changed my mind and decided to not rebuild my system.

1) it take a really long time and I need my computer for other tasks.

2) My Spotlight is returning the correct results now.

The errors still bug me. If you know me, I'm very against alerts and/or notifications that are not actionable. If it doesn't require an action, I don't want to hear about it. The removes noise and allows me to focus on the important things. That's why I always put a log level( DEBUG, INFO, CRITICAL, etc) in my application logs to tell the user if the event is important, a warning, or just informational.

I'm surprised that Apple doesn't do the same. We get to read the messages and decide the importance for ourselves without being familiar with the source code or the design of the application.

e.g. this is what I see now.

Apr 25 09:41:35 redacted com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0300-0000-0000-000000000000[59634]): Service exited due to SIGKILL | sent by mds[97]

It sounds critical, but is it? If I was doing the logging and the message wasn't important, I would mark the message's importance

Apr 25 09:41:35 INFO redacted com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0300-0000-0000-000000000000[59634]): Service exited due to SIGKILL | sent by mds[97]

"INFO" would tell you that the message is merely informational and does not require any action on the end user's part.

An Apple developer should chime in on this, but they probably won't.

Zonker did you get a resolution?

I am watching this thread as I have the same over-abundance of

com.apple.xpc.launchd[1] (com.apple.mdworker.shared.....00[1945]): Service exited due to SIGKILL | sent by mds[96]

normally before a fan frenzy and shut down.

I blamed Big Sur and have tried to stop Spotlight indexing. Ran from a clean Boot SSD of Big Sur.

It will hide them, but what to do to stop this activity? My computer seems to put all his skills to play with himself and this stupid message and ignore the fact that I try just to open some program - Davinci - it does nothing, than quit, and what I see is this message all the times.

Really, well I'm getting about 20 of these messages a second in my log and its chewing up 70% of my system ... which is impacting me ... the only user of this computer, who also owns the computer, so I'm the hardcore sys admin that has to fix this stuff ... How does someone with any kind of "points" on this blog come up with an answer like "nothing in the console intended for the user" ... Really pretty obnoxious ...

Same problem here.

I come home every day to find my machine has rebooted and all my work lost.

System log is full of SIGKILL mds worker errors.

Big Sur is the ONLY MacOS I've used where I get kernel panics (and they happen on a regular basis)

Apple is going seriously downhill. Spoiled with all their money.