Dani258
Level 1 (12 points)
Mac OS X

Q: These error messages in console just keep running.

I've tested with an admin test user and still had problems with Safari and Keychain, and I reset Keychain with no success.  Safari runs slow, I'm consistently asked for passwords and Keychain has crashed and locked up, and when I was asked to fix iCloud in System Preferences yesterday, it was crashing, also.  Now this is what is running in the console now.

 

10/24/15 10:58:47.288 PM CloudKeychainProxy[346]:  __39-[UbiqitousKVSProxy doSyncWithAllPeers]_block_invoke_2 <UB--s--C---> syncWithAllPeers (null), rescheduling timer

10/24/15 10:58:58.770 PM mds[63]: (DiskStore.Normal:2382) 6001 1.000089

10/24/15 10:59:02.422 PM secd[271]:  __SOSCCProcessSyncWithAllPeers_Server_block_invoke sync with all peers failed: Error Domain=com.apple.security.sos.error Code=1032 "peer: HiSjqACOJW557HgqfMPAQu0Uly not found" UserInfo={NSDescription=peer: HiSjqACOJW557HgqfMPAQu0Uly not found}

10/24/15 10:59:02.426 PM CloudKeychainProxy[346]:  __39-[UbiqitousKVSProxy doSyncWithAllPeers]_block_invoke_2 <UB--s--C---> syncWithAllPeers (null), rescheduling timer

10/24/15 10:59:16.802 PM Safari[424]: tcp_connection_tls_session_error_callback_imp 40 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

10/24/15 10:59:17.636 PM secd[271]:  __SOSCCProcessSyncWithAllPeers_Server_block_invoke sync with all peers failed: Error Domain=com.apple.security.sos.error Code=1032 "peer: HiSjqACOJW557HgqfMPAQu0Uly not found" UserInfo={NSDescription=peer: HiSjqACOJW557HgqfMPAQu0Uly not found}

10/24/15 10:59:17.638 PM CloudKeychainProxy[346]:  __39-[UbiqitousKVSProxy doSyncWithAllPeers]_block_invoke_2 <UB--s--C---> syncWithAllPeers (null), rescheduling timer

10/24/15 10:59:25.743 PM mds[63]: (DiskStore.Normal:2382) 6001 1.000019

10/24/15 10:59:32.765 PM secd[271]:  __SOSCCProcessSyncWithAllPeers_Server_block_invoke sync with all peers failed: Error Domain=com.apple.security.sos.error Code=1032 "peer: HiSjqACOJW557HgqfMPAQu0Uly not found" UserInfo={NSDescription=peer: HiSjqACOJW557HgqfMPAQu0Uly not found}

MacBook Pro with Retina display, OS X El Capitan (10.11), 2.4 GHz Intel Core i5, 8 GB 1600 M

Posted on Oct 24, 2015 9:12 PM

by R C-R,Solvedanswer
R C-R R C-R
Level 6 (17,700 points)
A:

I have found that running Disk Utility's First Aid on your startup disk (usually named Macintosh HD) will eliminate a lot of system.log errors, particularly if you run it while booted into the Recovery System. (Be sure to run it on the indented volume name, usually the second item in the list on the left side of the Disk Utility window.)

 

According to an Applecare agent I spoke with recently, even though there is no indication that it is doing so, the new 'one-step' First Aid routine does permissions repairs as well as checking for file system errors. It also repairs file system errors, but like the old "repair disk" step only on volumes that can be unmounted. Since whatever volume you start up from cannot be unmounted, running First Aid on the normal startup disk while started up from the Recovery System's volume will repair both its permissions & any file system errors it finds.

 

Also, certain system.log errors can be eliminated simply by starting up in Safe Mode, & then restarting normally. This is normally just used as a diagnostic step, but since it deletes font caches & kernel & other system cache files, it can eliminate errors due to corruption of those files because they are rebuilt as needed when you restart. Note that because Safe Mode verifies the startup disk & disables non-essential kernel extensions, it takes much longer to start up than normal, & after it finishes starting up the Mac will be slower, particularly when drawing graphics. This is normal & nothing to worry about.

Posted on Oct 31, 2015 7:20 AM

Close
Dani258

Q: These error messages in console just keep running.

  • All replies
  • Helpful answers

  • by sav_vancouver,

    sav_vancouver sav_vancouver Oct 28, 2015 8:06 PM in response to Dani258
    Level 1 (0 points)
    Oct 28, 2015 8:06 PM in response to Dani258

    I have the same setup as you. My computer would be locked up if I left for a few min. or closed the lid and opened.  The mouse works but I can't click anything.  I've also been seeing lots of these;

     

    2015-10-28 7:59:47.290 PM cdpd[1806]: KeychainGetICDPStatus: keychain: -25300

    2015-10-28 7:59:47.290 PM cdpd[1806]: KeychainGetICDPStatus: status: off

     

    So I opened my preference, iCloud ragged at me to re-enter my password (which is kinda weird). 

    I have turned off the keychain and the errors have gone away.

     

    Now I'm getting this:

     

     

    2015-10-28 7:59:47.290 PM com.apple.preferences.icloud.remoteservice[1789]: iCDP status for DSID 287753620 is DISABLED

    2015-10-28 7:59:56.412 PM com.apple.AddressBook.ContactsAccountsService[271]: [Accounts] Current connection, <NSXPCConnection: 0x7fbd88e19170> connection from pid 275, doesn't have account access.

    2015-10-28 7:59:56.413 PM sharingd[275]: [Accounts] Failed to update account with identifier 958D0B74-B614-4439-A780-563F57E1A5E7, error: Error Domain=ABAddressBookErrorDomain Code=1002 "(null)"

    2015-10-28 7:59:56.433 PM com.apple.AddressBook.ContactsAccountsService[271]: [Accounts] Current connection, <NSXPCConnection: 0x7fbd88e1c4f0> connection from pid 280, doesn't have account access.

    2015-10-28 7:59:56.433 PM CalNCService[280]: [Accounts] Failed to update account with identifier 958D0B74-B614-4439-A780-563F57E1A5E7, error: Error Domain=ABAddressBookErrorDomain Code=1002 "(null)"

    2015-10-28 7:59:56.516 PM com.apple.AddressBook.ContactsAccountsService[271]: [Accounts] Current connection, <NSXPCConnection: 0x7fbd88e1e590> connection from pid 443, doesn't have account access.

    2015-10-28 7:59:56.516 PM DataDetectorsDynamicData[443]: [Accounts] Failed to update account with identifier 958D0B74-B614-4439-A780-563F57E1A5E7, error: Error Domain=ABAddressBookErrorDomain Code=1002 "(null)"

    2015-10-28 8:01:55.946 PM WindowServer[153]: _CGXRemoveWindowFromWindowMovementGroup: window 0x62 is not attached to window 0x63

    2015-10-28 8:01:57.530 PM WindowServer[153]: _CGXRemoveWindowFromWindowMovementGroup: window 0x62 is not attached to window 0x63

    2015-10-28 8:02:00.630 PM WindowServer[153]: _CGXRemoveWindowFromWindowMovementGroup: window 0x62 is not attached to window 0x63

    2015-10-28 8:02:25.520 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:02:25.999 PM WindowServer[153]: _CGXRemoveWindowFromWindowMovementGroup: window 0x62 is not attached to window 0x63

    2015-10-28 8:02:37.365 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:02:55.787 PM WindowServer[153]: _CGXRemoveWindowFromWindowMovementGroup: window 0x62 is not attached to window 0x63

    2015-10-28 8:02:57.853 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:03:08.178 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:03:18.723 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:03:29.987 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:03:40.320 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:03:50.673 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:04:00.858 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:04:11.036 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:04:21.395 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:04:31.621 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:05:02.354 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:05:23.037 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:05:43.419 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

    2015-10-28 8:05:53.757 PM com.apple.WebKit.WebContent[1781]: CoreAnimation: failed to allocate IOSurface

  • by shogun88888888,

    shogun88888888 shogun88888888 Oct 28, 2015 8:15 PM in response to Dani258
    Level 1 (90 points)
    Oct 28, 2015 8:15 PM in response to Dani258

    Try logging out of iCloud restarting and logging back in to iCloud.

    THere is a permission problem somewhere and this may be the easiest first action

  • by AleG0,

    AleG0 AleG0 Oct 31, 2015 2:02 AM in response to shogun88888888
    Level 1 (0 points)
    Oct 31, 2015 2:02 AM in response to shogun88888888

    Even logging out and back in from iCloud would not resolve the issue (at least for me!).

    Still I have plenty (4000+) of those messages in console:

     

    31/10/15 09:48:39,082 secd[292]:  __SOSCCProcessSyncWithAllPeers_Server_block_invoke sync with all peers failed: Error Domain=com.apple.security.sos.error Code=1032 "peer: 4YCA7NWPqK4zIbCARr7gkWJ3WY not found" UserInfo={NSDescription=peer: 4YCA7NWPqK4zIbCARr7gkWJ3WY not found}

    31/10/15 09:48:39,083 CloudKeychainProxy[349]:  __39-[UbiqitousKVSProxy doSyncWithAllPeers]_block_invoke_2 <UB--s--C---> syncWithAllPeers (null), rescheduling timer

     

    Moreover, logging in/out from iCloud generates other messy problems (duplicate records in contacts db, continuity stop working, even iPhone hotspot won't resume)...

     

    After the "El Capitan" upgrade (both from last OS X and even with a fresh new install) I have had a lot of issues. To cite a few:

         - sandbox deny for whatever system services and other permission problems with Apple owns programs (wrestling with El Capitan...)

         - private/var/db/lsd issue (LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist) 

     

    All these are still present...

  • by shogun88888888,

    shogun88888888 shogun88888888 Oct 31, 2015 6:34 AM in response to AleG0
    Level 1 (90 points)
    Oct 31, 2015 6:34 AM in response to AleG0

    You did a clean install and still the errors?

     

    I am not familiar with these errors but it looks like a permissions problem authenticating with Apple cloud services. It also looks like the errors deal with communications with iCloud or keychain.

    Possible work arounds

     

    reset network card and check firewall, doubt it but maybe.

    already reset icloud so no go there

    reset keychain and / or password more info: Frequently asked questions about iCloud Keychain - Apple Support

    could be be an issue with the certificate key on the Apple server

     

    for troubleshooting purposes you could try logging out of both keychain and iCloud and check the errors then re-enable one at a time if no errors.

     

    really stumped but a few ideas for you

  • by R C-R,Solvedanswer

    R C-R R C-R Oct 31, 2015 7:20 AM in response to Dani258
    Level 6 (17,700 points)
    Oct 31, 2015 7:20 AM in response to Dani258

    I have found that running Disk Utility's First Aid on your startup disk (usually named Macintosh HD) will eliminate a lot of system.log errors, particularly if you run it while booted into the Recovery System. (Be sure to run it on the indented volume name, usually the second item in the list on the left side of the Disk Utility window.)

     

    According to an Applecare agent I spoke with recently, even though there is no indication that it is doing so, the new 'one-step' First Aid routine does permissions repairs as well as checking for file system errors. It also repairs file system errors, but like the old "repair disk" step only on volumes that can be unmounted. Since whatever volume you start up from cannot be unmounted, running First Aid on the normal startup disk while started up from the Recovery System's volume will repair both its permissions & any file system errors it finds.

     

    Also, certain system.log errors can be eliminated simply by starting up in Safe Mode, & then restarting normally. This is normally just used as a diagnostic step, but since it deletes font caches & kernel & other system cache files, it can eliminate errors due to corruption of those files because they are rebuilt as needed when you restart. Note that because Safe Mode verifies the startup disk & disables non-essential kernel extensions, it takes much longer to start up than normal, & after it finishes starting up the Mac will be slower, particularly when drawing graphics. This is normal & nothing to worry about.

  • by Dani258,

    Dani258 Dani258 Oct 31, 2015 4:49 PM in response to R C-R
    Level 1 (12 points)
    Mac OS X
    Oct 31, 2015 4:49 PM in response to R C-R

    I tried the disk utility and reset the keychain.  The error messages got a little better because I restored a backup that was from before any problems.  Once I updated to the current version of El Capitan, the problems and more came back so I think 10.11.1 has something to do with some of these errors.  This is showing in the keychain utility, "iMessage signing key," both private and public, and there must be over 50 private and 50 of the public keys so this must be contributing to part of the problem.  Please let me know if you have any suggestions for this that I can try.  I'm going to try disabling both iCloud and Keychain to see what difference that makes.

     

    Thank you!

  • by masc88,

    masc88 masc88 Nov 12, 2015 7:17 AM in response to Dani258
    Level 1 (5 points)
    Nov 12, 2015 7:17 AM in response to Dani258

    I had the same secd error and first aid in recovery mode with subsequent safe boot did not help.

     

    What actually resolved it for me was completely signing out of iCloud, confirming removal for all local iCloud data, then signing back in.

    After letting all data replicate and restarting the system the secd errors were gone for good.