hwmond high cpu load after 10.6.8 update

I can't recommend anything except to wait it out; that's the only quasai-official thing to do. I simply tried this and wanted to post the results of it back, what you do has to be your own judgement call as an admin. The harm is guessing whether or not an Xserve will properly reboot with this bug in place. It's also a question of performance; if your server is normally under high load you are potentially doing your customers, users, or yourself a disservice. Some of the posters on here have Premium Service & Support, I don't, but those that do haven't posted back any solid fixes from Apple, which is unfortunate. If you disable 'hwmond' then you lose reporting, losing the LEDs stinks, but LEDs don't make AFP respond any faster or slower!

Doing this restored the overall state & functionality of my server before the 10.6.8 update and that's what is most important to me. So, is it more important to you to have something official from Apple, which may happen tonight, tomorrow, or never, or is it more important to restore functionality now at the risk of loading a binary & kext's that are a version behind?

You must choose. But choose wisely.

Got a response from Apple, it's a known bug, they're working on it.

Went back to 0 on its own . . . what's up with that?

Kind of a sad truth isn't it. I miss the days when apple at least attempted to seem like they supported and used OS X server

First off, I get the frustration. That said, any server, if you rely on it, nees to be backed up regularly and reliably. I get that folks don't expect updates to break stuff, but sometimes it happens. It's a maddening lesson to learn, but a server can crash for a variety of reasons at any given moment. I remember updating a server to 10.3.8 and found out that it was not uncommon for that update to crash AFP.Luckily, there was a fix and I didn't have to resort to a backup, but I could have....

Jeff

Yeah that's odd.. I think there was one other poster who said he had the same thing happen. Maybe taking up a core for a week or so was intended? No clue.

Well said Jeff. My servers are mission critical as im sure most others are, and have learned the hard way, no updates for me untill they have been in production for a week or so for ample time to see if issues crop up. These forums are the basis of which I use to determine issues/fixes most of the time and am thankful for all the folks that take the time to troubleshoot.

CCC is a wonderful tool if your company (or if you) can afford extra disks. CCC clones my HD's every hour to spare disks. This is my redundancy, then use BRU for incremental backups.

Look forward to seeing the post letting me know this has been fixed so I can update!

Thanks for all the work here guys. I (as i know others as well) greatly appreciate it. this community is what makes these products worth while for me, not so much the vendor.

I can report my affected Xserve did the same thing, and now the CPU % is hovering around 0.2% with an occasional spike to around 3%.

Hello!

Same here

Xserve 94% CPU hwmond

updated via Delta-Update

Thanks IntraredAD!! This fix works great on my Xserver1,1 2006 version

You Rock!

@ryjguy7 .. you're welcome. Glad a few of us could be of help. I got to thinking about if and when Apple will fix this bug (again, it's been confirmed by Apple), and if you've replaced your hwmond binary & kext's with the 10.6.7 versions, re-updating to 10.6.8 and then with the official fix shouldn't be hard.

All you should have to do is use something like Pacifist again with the 10.6.8 delta or combo, I'd use the combo since I think we've clarified that it wasn't the combo that done-did it, to get everything up to 10.6.8 specs, then apply the (would-be) official fix using ASU, Installer.app, etc.

I can confirm the same drop in CPU usage on a co-worker's 2009 Xserve; he basically let it be for a week and found hwmond taking up 0.5% an hour ago, but after a restart (and it did restart), it went back to 94%. He had not replaced his files with 10.6.7 versions as described in this thread.

Same Problem here! After a few weeks(!!) normal operations the CPU-usage of hwmond raises up to 95%!

I updatet three servers with the Combo-Updater from 10.6.7 to 10.6.8! Only one of the xserves is showing the problem.

I dont want to try the fix of InfraredAD. I'll wait a few days and will watch the server. I hope it will go back to normal operations. If not, I will kill the hwmond process with

sudo launchctl unload /System/Library/LaunchDaemons/com.apple.hwmond.plist

Apple should fix the problem soon...

regards,

Peter

Hello!

Does any one have any update on this? I am still holding off on updating my servers.

Thanks,

Funny you should ask, yesterday I checked on the status of the bug report I filed and it's now listed as a duplicate of another issue and that one has a status of "Open". So, not fixed. I hope Apple hasn't decided to "fix" this by releasing 10.7.

Edit: Whoops, signed in with my MobileMe account.

If you depend on hwmond and have an AppleCare Support contract they can "help" you with this problem right away. Otherwise I think you'll be waiting for either 10.6.8 v1.1 or a separate update just for Xserve. I don't know what's taking so long myself. I'd like to think it'll pop out this week. AppleCare "helped" us a week or two ago.