Continuous 'Service Exited in system log

Google Drive File Stream

and/or

Google Drive Sync

Do any of you have that installed?

I read something on here mentioning TimeMachine. I cancelled the current backup, which slowed up the errors. There were still several coming through, but many less. I closed out of Drive File Stream, and it slowed up more.

I then ran this in terminal again:

sudo mdutil -E /

ERRORS STOPPED!

So, as others have mentioned, this must be something related to network mounting and/or virtual /Volumes. They're saying that Drive File Stream still is not compatible with the M1 chips, but I'm gathering that really means not compatible with Big Sur 😕

In case anyone NEEDS to use Drive File Stream, here's a quick workaround:

https://github.com/slw07g/googledrivefs-patch

the errors still roll through, but DFS works.

Wild.

I don't think i have Google Drive installed and still have on both my Catalina Macbooks.

I have been here since the early start of this discussion and it goes back to Mojave and High Sierra with some Security Updates and ever since.

I'm not on Big Sur yet but it sounds like it's there too.

I had to disable my Spotlight completely to get this error to stop.

P.S Any easy way to check if i have any Google Drive stuff on my computer ? I don't have the Google Drive app installed now but i did back in time.

But on my other Mac i never installed Google Drive from what i remember so if there is a easy trick to search for it other that a normal search. (I use Find Any File) now when Spotlight is disabled.

Hey! Haven't read all the replies (there are a lot of them lmao) but i came here looking for something similar. Sometimes mi mac wont turn off (i have to force shutdown). Reading the log i found the same error message ifestos posted. At first i thought it was the mail app being a piece of sh#t as always has been, but reading some of your comments i agree it might be Google Drive File Stream doing weird things on my computer. Under System Preferences i disabled Spotlight search on my google drive virtual disk and ~/Library/Application Support/Google/DriveFS (cache folder). Just wanted to 'take a sit' so i receive mail updates from this thread

MyMacIta wrote:

Please can I help me, I have same problem.

<macbook pro.log>

Another contributor has already mentioned in this thread that these errors occur even on a clean install of macOS without migrating/restoring from backup and without any third party apps installed which proves it is an Apple issue with macOS. It is up to Apple to resolve the issue. It may have even occurred on a brand new system just out of the box with no third party apps.

Just ignore all of the macOS system logs as they are no longer useful for troubleshooting purposes. The only useful remaining macOS log is the Kernel Panic log when your Mac has a kernel panic. Otherwise don't even bother looking at any of the system logs.

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

MyMacIta wrote:

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

What has led you to believe that the SIGKILL log messages are related to your sleep problem? On two Catalina MacBook Pros, I see this same SIGKILL message a number of times per minute and it seems to have no impact on either computer's operation. I also see it on a MacBook Air with High Sierra, also, no discernible impact from it.

Have you tried an SMC reset? That is one approach to address power issues. Or have you tried booting into Safe Mode to see if sleep behaviors are normal in Safe Mode?

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

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

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?

There seem to be three categories of people posting in this thread:

(1) People whose computers are running poorly

(2) People who have been alerted to this SIGKILL message in the system.log and looked and found many such messages in their system logs

(3) People who have some other problem

The existence of many of these messages in the system log is not necessarily connected to a problem with the computer. These may well be debug or informational messages for Apple programmers. My MacBook Pro 16-inch, obtained new in May of 2020, had those system log messages when brand new and still does, sometimes 10 per second, sometimes fewer. The computer runs fine and has no issues at all.

Meanwhile, scores of people in categories (1) or (3) are also posting here, but this may have no connection to the system log messages of (2). Some have improved their computer performance by stopping file indexing for Spotlight, but that may have nothing to do with (2). Of course the messages in (2) go away when one does that since those messages come from the MDS process.

People are confusing the fact that two things happen together with there being a causal relationship between them.

If your computer is sluggish or crashing, look elsewhere for the cause than this system log message because it appears (at least on mine) in normal computers that are running well.

To try to narrow down the cause of the sluggishness, have you booted into Safe Mode and checked in Safe Mode, is the issue still there? Have you logged out and logged in as another user to see if it is user-specific or system-wide? Have you run Disk Utility in Recovery mode to repair the file system? Also, posting the output from Etrecheck may provide clues, lots of people can pore over the Etrecheck output and find things, sometimes poor performance is connected to something that was installed, or inherited from an old operating system or installation from long ago.

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.

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.

AxeBox360 wrote:

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.

When you do the fresh install, consider (you of course don't have to do this, and it does take longer, but I think it will enable you to identify the root cause of your problem and get back to a smoothly running Mac faster) backing up everything (two backups, for safety), spot-check that you can restore from the backups, and then you can reformat the disk and do a brand new MacOS install, from Recovery mode. On first boot, you can create one admin user with a different name from any of your previous ones. Then run all the MacOS updates and check that the problem is gone, on a fresh vanilla install with no third party software or extensions. If the problem is still there, you may have a hardware problem. If the problem is gone, run Migration Assistant and migrate over your old user accounts and their files, but no software and no settings. Then you can install the latest versions of third party software one or two at a time and retest. The goal is to find the item that, when installed, is conflicting with the smooth running of Catalina. I have followed this procedure myself, and it fixed the issue, which for me was a computer that would hang when booting. I only reinstalled the software I needed, hence a number of older mostly unused items were never reinstalled, and I am guessing one of them was the culprit because the problem was gone.