ocspd -> 100% cpu

Question

ocspd -> 100% cpu

Lately i'm having some trouble with my CPU going to 100% at random.
Using iStat menu's i could see it was a kernel task using about 100% cpu.
So i checked the logs and noticed every time my Mac went to 100% it was because /usr/sbin/ocspd was started. As far as i could 'google' it, this has something to do with networking.

I'll add my network setup to be complete:

Airport Express configured as WDS main (connected to broadband cable modem)
Airport Extreme configured as WDS remote
Mac Mini connected via wire to Airport Extreme
Harddisk connected to airport extreme via USB (airdisk)

And finally a Macbook (the one with the problem) connected wireless

Can anyone give me some pointer to resolve this random cpu hog.

Macbook / Mac mini, Mac OS X (10.5)

Posted on Apr 15, 2009 12:24 PM

Reply

Answer 1

Kappy

Level 10

362,007 points

Apr 15, 2009 12:38 PM in response to Smolders Johan

You can view the man page for ocsp here.

Use Activity Monitor to force quit the daemon. That may be all that's required. However, if it continues to hog CPU time, then you may have a corrupted cache file or a bad preference file. You can try this to start:

Delete caches to resolve some problems:

Boot into single-user mode. After startup is completed you will be in command line mode and should see a prompt with a cursor positioned after it. At the prompt enter the following then press RETURN after each commandline:

/sbin/fsck -fy

If you receive a message that says " *** FILE SYSTEM WAS MODIFIED ***" then re-run the command until you receive a message that says "** The volume (name ofvolume) appears to be OK." If you re-run the command more than seven times and do not get the OK message, then the drive cannot be repaired this way.
If you were successful then enter:

/sbin/mount -uw /
rm -rf /System/Library/Caches/*
rm -rf /System/Library/Extensions.mkext
rm -rf /Library/Caches/*
reboot

I suggest you print out the above to be sure you do not make any errors when entering the commands. When in single-uwer mode you have 'root' access, so it's important that you not make any mistakes.

Reply