Lots of error messages in system.log

[frank-ger]

Hi guys,

I've received my MBA 8/16/512 yesterday at after some problems with Photos app I've checked the system.log in the Console. Unfortunately I found a lot of error messages there:

Jan 28 22:45:54 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0100-0000-0000-000000000000[1743]): Service exited due to SIGKILL | sent by mds[257]
Jan 28 22:46:14 MacBook-Air com.apple.xpc.launchd[1] (com.apple.quicklook[1754]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklookd.xpc
Jan 28 22:46:14 MacBook-Air com.apple.xpc.launchd[1] (com.apple.quicklook[1754]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Jan 28 22:46:17 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0400-0000-0000-000000000000[1752]): Service exited due to SIGKILL | sent by mds[257]
Jan 28 22:46:56 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0500-0000-0000-000000000000[1756]): Service exited due to SIGKILL | sent by mds[257]
Jan 28 22:46:59 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.06000000-0200-0000-0000-000000000000[1748]): Service exited due to SIGKILL | sent by mds[257]
Jan 28 22:46:59 MacBook-Air AccountProfileRemoteViewService[1760]: objc[1760]: Class AOSUISpyglassAccountChangeHelper is implemented in both /System/Library/PrivateFrameworks/AOSUI.framework/Versions/A/AOSUI and /System/Library/PrivateFrameworks/AOSUI.framework/Versions/A/XPCServices/AccountProfileRemoteViewService.xpc/Contents/MacOS/AccountProfileRemoteViewService. One of the two will be used. Which one is undefined.
Jan 28 22:47:08 MacBook-Air syncdefaultsd[1780]: objc[1780]: Class SYDClient is implemented in both /System/Library/PrivateFrameworks/SyncedDefaults.framework/Versions/A/SyncedDefaults and /System/Library/PrivateFrameworks/SyncedDefaults.framework/Support/syncdefaultsd. One of the two will be used. Which one is undefined.
Jan 28 22:47:08 MacBook-Air syncdefaultsd[1780]: objc[1780]: Class SYDJournal is implemented in both /System/Library/PrivateFrameworks/SyncedDefaults.framework/Versions/A/SyncedDefaults and /System/Library/PrivateFrameworks/SyncedDefaults.framework/Support/syncdefaultsd. One of the two will be used. Which one is undefined.
Jan 28 22:47:09 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0100-0000-0000-000000000000[1749]): Service exited due to SIGKILL | sent by mds[257]
Jan 28 22:47:14 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.10000000-0700-0000-0000-000000000000[1747]): Service exited due to SIGKILL | sent by mds[257]

Because I've just started to transfer my data and setting up everything, I've decided to make a clean installation. But unfortunately even after fresh installation the same error messages comes up.

Is it just me, or anybody else have such error messages in system.log?

 

[chabig]

Everyone's log is full of messages like that. They are more meaningful to developers than users.

 

[frank-ger]

Really? That sounds strange for me, but I'm a new Mac user...
Then my fresh installation was unnecessary, but now I know, how it works

 

[theSeb]

Really? That sounds strange for me, but I'm a new Mac user...
Then my fresh installation was unnecessary, but now I know, how it works

i am not sure why an operating system logging perfectly normal information in its logs sounds strange to you. I recommend that you do not study windows or Linux system logs, because they are very frightening too.

 

[frank-ger]

Not sure, if I'm posted the correct line in my first post, but messages like this:

Jan 28 23:35:44 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0000-0000-0000-000000000000[2241]): Service exited due to SIGKILL | sent by mds[257]
Jan 28 23:35:44 MacBook-Air com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0100-0000-0000-000000000000[2242]): Service exited due to SIGKILL | sent by mds[257]
Jan 28 23:35:47 MacBook-Air com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.com.apple.systempreferences.1152921500311955792.1152921500311955797(501)> [1982]
Jan 28 23:35:47 MacBook-Air AccountProfileRemoteViewService[2245]: objc[2245]: Class AOSUISpyglassAccountChangeHelper is implemented in both /System/Library/PrivateFrameworks/AOSUI.framework/Versions/A/AOSUI and /System/Library/PrivateFrameworks/AOSUI.framework/Versions/A/XPCServices/AccountProfileRemoteViewService.xpc/Contents/MacOS/AccountProfileRemoteViewService. One of the two will be used. Which one is undefined.
Jan 28 23:35:59 MacBook-Air com.apple.xpc.launchd[1] (com.apple.preference.notifications.remoteservice[2256]): Service exited due to SIGKILL | sent by com.apple.preference.notificatio[2256]
Jan 28 23:36:06 MacBook-Air VTDecoderXPCService[2073]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug
Jan 28 23:36:06 MacBook-Air VTDecoderXPCService[2073]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug

doesn't seems to be normal for a fresh installed OS, not even for MS Windows.

 

[chabig]

It is normal. The OS is undergoing continuous development and those logs are useful to developers. They mean nothing for users.

 

[frank-ger]

ok, I‘ll try never ever open the Console app

Thx

 

[theSeb]

ok, I‘ll try never ever open the Console app

Thx

In all honesty, that is the best thing to do for normal users

 

[jdb8167]

In all honesty, that is the best thing to do for normal users

Occasionally you can debug a problem with the console logs but there is so much extraneous logging that usually it is useless. In the past, I've had problems shutting down and I was able to use the logs to see that a particular kernel extension was hanging up the shutdown process. But that is a kind of special case because you can easily track down where the computer was shutting down. Mostly I agree with your assessment.