Skip navigation

'ubd' process huge cpu load

46213 Views 53 Replies Latest reply: Jul 11, 2013 5:34 PM by jessefromsanta barbara RSS
1 2 3 4 Previous Next
hamster116 Calculating status...
Currently Being Moderated
Oct 16, 2011 3:28 AM

Since updating to 7.2 I have a weird issue with a process called ubd. It has a huge and constant cpu load of between 50-99%. This generates a lot of extra heat and fan noise to accompany that. Quitting the process or rebooting doesn't help.

 

I read somewhere that the process is iCloud related, but I tried disabling some iCloud services but that didn't seem to help either.

 

The console displays these lines all the time:

16/10/2011 12:14:35.122 ubd: createSelfSignedCertificate - _createCert returned -25295

 

and after about 6 tries it exits with code: 254 and starts again.

 

I guess this isn't really normal, does anone know what might be up or how to fix this?

MacBook Pro, Mac OS X (10.7.2)
  • putnik Level 3 Level 3 (620 points)
    Currently Being Moderated
    Oct 16, 2011 4:28 AM (in response to hamster116)

    Here is a link about the ubd process.  Maybe the log file will give you information about your particular usage?

     

    http://www.macinside.info/process.php?name=ubd

  • vaguebond Calculating status...
    Currently Being Moderated
    Oct 16, 2011 5:44 AM (in response to hamster116)

    I'm having exactly the same problem.. but somehow worse. My MBP 13' heats until it crashes. This 'ubd' process is killing it. It's related to iCloud and it's services. I thought iCloud is not in beta anymore, but it seems it's still buggy. I would downgrade if I could.

     

    If you have any suggestions, please let us know.

  • Dirk43 Calculating status...
    Currently Being Moderated
    Oct 16, 2011 5:51 AM (in response to hamster116)

    I have the same issue with the UBD process.  I am running on 2011 15" MBP.  I get a different message in the console but the same problem with the cpu utilization and the excessive heat both being an issue.  This is what I get in my console:

    10/16/11 7:47:38.991 PM com.apple.launchd.peruser.502: (com.apple.ubd[423]) Exited with code: 254

     

    I am curious, did you have the developer version of 10.7.2 installed on your system at any point in time or is this issue as a result of the official update pushed out by Apple?

     

    Thanks

  • Dirk43 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 16, 2011 5:53 AM (in response to putnik)

    I don't see this log file on my system.  Anyone else able to find it?

  • vaguebond Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 16, 2011 7:17 AM (in response to hamster116)

    This did the trick! Thank YOU!

     

    I don't know what I've lost by resetting to default keychain, but the MBP is back to quiet operations as before.

     

     

     

    @ Dirk43 P.S. I found the certificate after resetting the keychain though. Before I could't find it either.

  • Dirk43 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Oct 16, 2011 12:25 PM (in response to hamster116)

    Any idea how I can delete this keychain?  I can't get into "Keychain Access" as I get the spinning beach ball of death.  Somehow I managed to get 44k items in there.  I let keychain access run for a while, but it just ends up using 3gb of memory before I get ****** and force quit.  Any ideas?

     

    I have already tried to repair it and fix the cert from another admin user account.

     

    Thanks

  • Mixel Calculating status...
    Currently Being Moderated
    Oct 17, 2011 5:26 AM (in response to hamster116)

    I've tried all these fixes.. Approving the certificate, resetting the keychain, deleting the keychain entirely, logging out of or disabling iCloud services. It's still coming back and doing the same.

     

    Is backing up and nuking my lion partition going to be the only solution? This is pretty frustrating. :(

  • devinreams Calculating status...
    Currently Being Moderated
    Oct 17, 2011 3:42 PM (in response to hamster116)

    hamster116 wrote:

     

    There is a certificate (not a key) in my keychain called 'com.apple.ubiquity.peer-uuid", which was marked as untrusted. I opened it's info dialog and set it to "always trust".

     

    Good eye. I noticed the extra keychain entries but didn't think to 'trust' the certficiate. Though this has not resolved the issue of ubd spiking CPU usage and more certificates/keys being created (no matter how many I "trust").

     

    FWIW: you can tail your ~/Library/Logs/Ubiquity/{username}/ubiquity.log and see the certficiate errors every few seconds.

    [ERROR]     5041c5de5e10 [11/10/17 16:35:56.047]  13116.main copy_mme_bag:156 copyPreferredMobileMeName failed

    [ERROR]     5041c5dfac36 [11/10/17 16:35:56.047]  13116.main ubd_main:2030 null personid

    [ERROR]     5041c70a0399 [11/10/17 16:35:56.067]  13116.main find_existing_identity_unsafe:963 error -25300 from SecItemCopyMatching

    [ERROR]     5041c79acafc [11/10/17 16:35:56.076]  13116.main find_existing_identity_unsafe:963 error -25300 from SecItemCopyMatching

    --[ERROR]     50422bafc893 [11/10/17 16:35:57.755]  13116.main find_existing_identity_unsafe:963 error -25300 from SecItemCopyMatching

    [ERROR]     5042825ac3de [11/10/17 16:35:59.209]  13116.main createSelfSignedCertificate:52 error: Error Domain=NSOSStatusErrorDomain Code=-25299 "The operation couldn’t be completed. (OSStatus error -25299.)" ( / The item already exists.)

    [ERROR]     5042825ff022 [11/10/17 16:35:59.209]  13116.main create_new_identity_unsafe:989 failed to find an existing identity and failed to create a new one

    [ERROR]     5042be133f3f [11/10/17 16:36:00.211]  13116.main find_existing_identity_unsafe:963 error -25300 from SecItemCopyMatching

    [ERROR]     5042e63362ea [11/10/17 16:36:00.884]  13116.main createSelfSignedCertificate:52 error: Error Domain=NSOSStatusErrorDomain Code=-25299 "The operation couldn’t be completed. (OSStatus error -25299.)" ( / The item already exists.)

    [ERROR]     5042e634918f [11/10/17 16:36:00.884]  13116.main create_new_identity_unsafe:989 failed to find an existing identity and failed to create a new one

    [ERROR]     504321ee3444 [11/10/17 16:36:01.886]  13116.main find_existing_identity_unsafe:963 error -25300 from SecItemCopyMatching

    [ERROR]     50440def58e3 [11/10/17 16:36:05.846]  13116.main createSelfSignedCertificate:52 error: Error Domain=NSOSStatusErrorDomain Code=-25299 "The operation couldn’t be completed. (OSStatus error -25299.)" ( / The item already exists.)

    [ERROR]     50440df08e7a [11/10/17 16:36:05.846]  13116.main create_new_identity_unsafe:989 failed to find an existing identity and failed to create a new one

    [ERROR]     504449a35eb8 [11/10/17 16:36:06.847]  13116.main find_existing_identity_unsafe:963 error -25300 from SecItemCopyMatching

    [ERROR]     5044a1993f0e [11/10/17 16:36:08.323]  13116.main createSelfSignedCertificate:52 error: Error Domain=NSOSStatusErrorDomain Code=-25299 "The operation couldn’t be completed. (OSStatus error -25299.)" ( / The item already exists.)

    [ERROR]     5044a19a6e77 [11/10/17 16:36:08.323]  13116.main create_new_identity_unsafe:989 failed to find an existing identity and failed to create a new one

    [ERROR]     5044dd4c1e33 [11/10/17 16:36:09.325]  13116.main find_existing_identity_unsafe:963 error -25300 from SecItemCopyMatching


  • goodfield Calculating status...
    Currently Being Moderated
    Oct 20, 2011 1:16 AM (in response to devinreams)

    Had the same issue ... after 3 hours i did a rm -r Mobile* in ~/Library/Application Support. Be careful i think there was an directory from MobileMe and one calles Mobile Sync ... i don't really know which one was the evil, but i think it was the Mobile Me directory.

  • kitsonk Calculating status...
    Currently Being Moderated
    Oct 23, 2011 11:18 PM (in response to hamster116)

    I "had" a similair issue.  I had enabled iCloud and things went fine, but I think the problem came in when I tottled off to a WiFi access point that required authentication prior to connecting to the Internet, using redirects.  Then essentially any SSL connection (including redirection to the click to accept redirect site) was becoming unavailable.  I took a look at my keychain and that was locked.  So I forced quit and rebooted and I noticed there were a large amount of com.apple.ubiquity* keys, a invalid self signed cert and an "Unknown" cert.  After a few moments my keychain locked up again and required a forcequit and reboot.

     

    I eventually got a bit of breathing room by going into a VMWare VM and accepting the T/C of the WiFi access and then rebooting one more time.  After that I cleaned up my keychain, signed out of iCloud and haven't had a problem since.

     

    My suspect is that iCloud tries to do it's security measures at startup, trying to generate some self signed certs, but needs something from the "internet" to generate them/validate them and then doesn't handle the redirection bad, locks the Keychain and causes all sorts of havoc.

     

    My only solution was to disable iCloud and clean up my keychain.

  • AKEH Calculating status...
    Currently Being Moderated
    Oct 24, 2011 1:55 AM (in response to kitsonk)

    My keychains are also rather a mess since the upgrade to iCloud. I would like to clean them up, but don't know which certificates I can safely delete.

    I have an unknown keychain, a number of com.apple.ubiquity keys (one has ssl in front of the name) which aren't trusted. Can these be deleted? Or should I set the computer to trust these?

    If I delete a keychain the computer needs, will it download/ make it again? Or can I restore it from the time machine?

     

    I also have some expired keychains (nothing to do with iCloud). Can I delete these?

1 2 3 4 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (5)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.