Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Messages in "system.log"

In "system.log" file of My MacBookPro(OS 11.1), I keep having the following messages. What shall I do?

Jan 31 22:39:48 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master[8944]): Service exited with abnormal code: 1


Jan 31 22:39:48 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.


Jan 31 22:39:58 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master[8949]): Service exited with abnormal code: 1


Jan 31 22:39:58 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.


Jan 31 22:40:08 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master[8950]): Service exited with abnormal code: 1


Jan 31 22:40:08 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.


Jan 31 22:40:18 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master[8952]): Service exited with abnormal code: 1


Jan 31 22:40:18 KyoRyu com.apple.xpc.launchd[1] (com.apple.postfix.master): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.


Jan 31 22:40:26 KyoRyu com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0500-0000-0000-000000000000[8948]): Service exited due to SIGKILL | sent by mds[89]


Jan 31 22:40:26 KyoRyu com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0300-0000-0000-000000000000[8947]): Service exited due to SIGKILL | sent by mds[89]


Jan 31 22:40:26 KyoRyu com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0400-0000-0000-000000000000[8946]): Service exited due to SIGKILL | sent by mds[89]


Jan 31 22:40:26 KyoRyu com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0200-0000-0000-000000000000[8945]): Service exited due to SIGKILL | sent by mds[89]

MacBook Pro 15″, macOS 11.1

Posted on Jan 31, 2021 6:42 PM

Reply
Question marked as Best reply

Posted on Feb 1, 2021 8:57 PM

The system logs on recent versions of macOS are no longer useful for troubleshooting system issues. The system logs are now flooded with useless junk which mostly contains debugging messages meant only for the developers (none of those messages should be left active on a released OS or app). The only useful macOS log is for Kernel Panics errors. Otherwise just stay out of the Console app. That Spotlight "SIGKILL" error is a known issue even with a clean install of macOS. There is a very long thread about this error appearing in the system log here:

https://discussions.apple.com/thread/251433748


If you are not having any specific problems, then just ignore the error messages.


If you are having a specific problem, then you should start a new thread with a relevant subject line so you can get more contributors to help you. Make sure to provide the exact model of your Mac and OS plus as many details of the issue including any error messages. You may want to run EtreCheck and post the report here using the "Additional Text" icon which looks like a piece of paper.


You may also want to run the Apple Diagnostics and try booting into Safe Mode to see if the issue still occurs.


Similar questions

1 reply
Question marked as Best reply

Feb 1, 2021 8:57 PM in response to Iwata_Suehiro

The system logs on recent versions of macOS are no longer useful for troubleshooting system issues. The system logs are now flooded with useless junk which mostly contains debugging messages meant only for the developers (none of those messages should be left active on a released OS or app). The only useful macOS log is for Kernel Panics errors. Otherwise just stay out of the Console app. That Spotlight "SIGKILL" error is a known issue even with a clean install of macOS. There is a very long thread about this error appearing in the system log here:

https://discussions.apple.com/thread/251433748


If you are not having any specific problems, then just ignore the error messages.


If you are having a specific problem, then you should start a new thread with a relevant subject line so you can get more contributors to help you. Make sure to provide the exact model of your Mac and OS plus as many details of the issue including any error messages. You may want to run EtreCheck and post the report here using the "Additional Text" icon which looks like a piece of paper.


You may also want to run the Apple Diagnostics and try booting into Safe Mode to see if the issue still occurs.


Messages in "system.log"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.