Continuous 'Service Exited in system log

**** you apple. next machine I'm going back to Windows.

I don't need your buggy OS, constantly rebooting, overheating, kernel panicking OS anymore.

Windows is starting to look good again.

M1 stuff is majorly disappointing.

@steve626

totally agree with HWtech

Excellent post and advice… particularly amongst a typical collection of colourful, emotional, dumb, delusional, desperate

etc etc type responses which inevitably appear on these threads. Great bedtime reading if you are having trouble getting to sleep & you can’t get to a pharmacy for some decent sleeping medication.

Jokes aside, I’ve been using Mac’s for years and have owned several models over the years but tonight I happen to be unboxing and setting up a brand new iMac Model A2115 shipped with BigSur version 11.1

After working my way through the setup assistant including iCloud login the first thing I did was check System Preferences for an update.

Whilst waiting for the latest Big update to download I went into system report to remind myself of the machine specs etc & for no specific reason checked out the system logs… hence why I found this thread because my machine is spewing out the same repetitive SigKill etc junk that everyone else has encountered.

So just thought I’d throw my two cents worth in that it’s happening on a 100% brand new iMac with zero applications installed other than what it was shipped with.

No idea whether this IS actually an issue that I should be concerned about or not as you’ve subtly suggested but given my machine is out of the box I’ll submit the feedback to Apple so it is documented & on the record if it does turn out to be something potentially detrimental to a piece of tech I’ve parted with a nice wad of cash for…

Same Problem in Catalina MacBook Air 2017 after mi mac Shut Down Could Be the Fan?

ep 30 12:34:35 MacBook-Air- com.apple.xpc.launchd[1] (com.apple.metrickitd[628]): Could not find user/group associated with service: 0: Undefined error: 0 mobile/(null)

Sep 30 12:34:35 MacBook-Air- com.apple.xpc.launchd[1] (com.apple.metrickitd[628]): Service setup event to handle failure and will not launch until it fires.

Sep 30 12:34:35 MacBook-Air- com.apple.xpc.launchd[1] (com.apple.metrickitd[628]): Service exited with abnormal code: 78

Sep 30 12:34:53 MacBook-Air- com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0200-0000-0000-000000000000[620]): Service exited due to SIGKILL | sent by mds[111]

Sep 30 12:34:57 MacBook-Air- com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0D000000-0300-0000-0000-000000000000[623]): Service exited due to SIGKILL | sent by mds[111]

I'm wondering if anybody at Apple is reading these things, since this is a problem that has been around for several years now. And it's now impossible for me to fix anything using Terminal thanks to all the "security" features they keep adding.

Anything you can tell us, Apple?

Sometimes shutdown can take a long time. While that may be an indication that something is awry, it's better not to get impatient and interrupt it. I'm talking like 5 or 10 minutes here. Be patient and see if it will eventually shut down. That will be a better clue than simply crashing it, which might exacerbate things.

Don't open Console. You won't know it is there. Console is full of meaningless messages that often repeat.

Is there something else happening that made you look into Console?

If I hear anything I will - but most issues I've raised I've heard little more about :-(

Don't get your hopes up for 10.15.6: Service exited due to SIGKILL | sent by mds galore.

I also have the same issue.

Hi, on my MBP 16" I have also seen this log-Post. Seems that there were no problems.

Till 10.15.4 everything was fine. Didn't know if it starts with 10.15.5 or 6 but my system.log is flooded :-(

Too bad the second supplemental update to Catalina did not fix it either. Guess everybody's too busy with macOS Candy Crush™ (sorry, Big Sur).

I'm experiencing the same issue when connecting to my work's VPN.