Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

joedec

macrumors 6502
Original poster
Jul 25, 2014
443
51
Cupertino
Anyone keeping an eye on syslog, etc. I get the following error every 10 seconds, and I do NOT have keychain syncing enabled.

7/28/14 2:00:13.513 PM CloudKeychainProxy[516]: ckdproxymain Running as root, exiting..
7/28/14 2:00:13.514 PM com.apple.xpc.launchd[1]: (com.apple.security.cloudkeychainproxy3) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

I am on Beta, OS X 10.10 (14A299l)

... Jeff
 

colourfastt

macrumors 65816
Apr 7, 2009
1,047
964
Anyone keeping an eye on syslog, etc. I get the following error every 10 seconds, and I do NOT have keychain syncing enabled.

7/28/14 2:00:13.513 PM CloudKeychainProxy[516]: ckdproxymain Running as root, exiting..
7/28/14 2:00:13.514 PM com.apple.xpc.launchd[1]: (com.apple.security.cloudkeychainproxy3) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

I am on Beta, OS X 10.10 (14A299l)

... Jeff

I get that error about every 10 seconds.
 

joedec

macrumors 6502
Original poster
Jul 25, 2014
443
51
Cupertino
I started getting this yesterday, and at the same time, however maybe not related, mail constantly crashes and BLE keeps looking for an airplay device.

My installation is running really well for the most part. I don't notice any issues from these errors.

Mail crashes consistently when I try and open "Previous Recipients", reported that.
 

opfor

macrumors member
Jul 27, 2014
30
37
I also have those errors every 10s since I installed Yosemite about a week ago. Tried do disable iCloud keychain but it did not go away. I have reported to Apple but they go away if you disable/move the plist file.

At first look it seems that the process detects if it is run by root and exits if that is the case (it is usually not a good idea to run such a process with root privileges). Launchd on the other hand detects that the process exited quickly and tries to start it again in 10s...
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
I got the error resolved, I think...

I deleted these, but I am sure that the #3 was the problem.

com.apple.security.cloudkeychainproxy.plist
com.apple.security.cloudkeychainproxy 2.plist
com.apple.security.cloudkeychainproxy 3.plist
com.apple.security.cloudkeychainproxy.keysToRegister.plist

I you open the file with TextEdit it makes reference to a "dirtykey", I am not sure what the dirty key is, why it dirty, or how I could clean it.

I am no longer getting that error spamming my console, but there are still others about BTLE and airplay.
 

matiseek33

macrumors newbie
Aug 9, 2014
1
0
I got the error resolved, I think...

I deleted these, but I am sure that the #3 was the problem.

com.apple.security.cloudkeychainproxy.plist
com.apple.security.cloudkeychainproxy 2.plist
com.apple.security.cloudkeychainproxy 3.plist
com.apple.security.cloudkeychainproxy.keysToRegister.plist

I you open the file with TextEdit it makes reference to a "dirtykey", I am not sure what the dirty key is, why it dirty, or how I could clean it.

I am no longer getting that error spamming my console, but there are still others about BTLE and airplay.

Can you please point me to the location where i can find these files?
 

smithrh

macrumors 68030
Feb 28, 2009
2,743
1,790
I started getting this yesterday, and at the same time, however maybe not related, mail constantly crashes and BLE keeps looking for an airplay device.

Same here. I reported these issues to Apple within 45 minutes of the beta being released so hopefully this is fixed next public beta.
 

colourfastt

macrumors 65816
Apr 7, 2009
1,047
964
I got the error resolved, I think...

I deleted these, but I am sure that the #3 was the problem.

com.apple.security.cloudkeychainproxy.plist
com.apple.security.cloudkeychainproxy 2.plist
com.apple.security.cloudkeychainproxy 3.plist
com.apple.security.cloudkeychainproxy.keysToRegister.plist

I you open the file with TextEdit it makes reference to a "dirtykey", I am not sure what the dirty key is, why it dirty, or how I could clean it.

I am no longer getting that error spamming my console, but there are still others about BTLE and airplay.

The only one i had was chainproxy3. I deleted it and rebooted; on reboot OS X recreated it, so I'm back to the original problem.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.