|
|
Brand New 13" MBA - errors in console
|
|
|
|
Mac Elite
Join Date: Sep 2006
Location: Back in the Good Ole US of A
Status:
Offline
|
|
So I got my new 13" MBA. I must confess I am loving this thing. It is blazing fast. Even running a Windows 7 VM is fast. This flash storage makes such a difference. Anyway, here's the weirdness. Right out of the box, without installing a single thing (it came with 10.6.5) I see these errors in the console every minute:
1/15/11 10:39:02 PM com.apple.launchd[1] (com.apple.batteryd[1319]) Exited with exit code: 1
1/15/11 10:39:02 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
1/15/11 10:39:12 PM com.apple.launchd[1] (com.apple.batteryd[1320]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
1/15/11 10:39:12 PM com.apple.launchd[1] (com.apple.batteryd[1320]) Exited with exit code: 1
1/15/11 10:39:12 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
1/15/11 10:39:22 PM com.apple.launchd[1] (com.apple.batteryd[1321]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
1/15/11 10:39:22 PM com.apple.launchd[1] (com.apple.batteryd[1321]) Exited with exit code: 1
1/15/11 10:39:22 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
1/15/11 10:39:32 PM com.apple.launchd[1] (com.apple.batteryd[1322]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
1/15/11 10:39:32 PM com.apple.launchd[1] (com.apple.batteryd[1322]) Exited with exit code: 1
1/15/11 10:39:32 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
1/15/11 10:39:42 PM com.apple.launchd[1] (com.apple.batteryd[1323]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
1/15/11 10:39:42 PM com.apple.launchd[1] (com.apple.batteryd[1323]) Exited with exit code: 1
1/15/11 10:39:42 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
1/15/11 10:39:52 PM com.apple.launchd[1] (com.apple.batteryd[1324]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
1/15/11 10:39:52 PM com.apple.launchd[1] (com.apple.batteryd[1324]) Exited with exit code: 1
1/15/11 10:39:52 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
1/15/11 10:40:02 PM com.apple.launchd[1] (com.apple.batteryd[1325]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
1/15/11 10:40:02 PM com.apple.launchd[1] (com.apple.batteryd[1325]) Exited with exit code: 1
1/15/11 10:40:02 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
1/15/11 10:40:12 PM com.apple.launchd[1] (com.apple.batteryd[1326]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
There is no /usr/local/libexec/batteryd file. I did a little googling and saw someone else had had this same issue. I ended up deleting the plist file that was pointing to this non-existant file. The plist in question: /System/Library/LaunchDaemons/com.apple.batteryd.plist
So here's a question for any of you who own a new 11" or 13" MBA. Do you have either of these two files in your system:
/usr/local/libexec/batteryd
/System/Library/LaunchDaemons/com.apple.batteryd.plist
|
|
|
|
|
|
|
|
|
Moderator
Join Date: Oct 2001
Location: San Jose, CA
Status:
Offline
|
|
You don't need to worry about every little warning or error in the console. Just enjoy your new computer. This is not a big deal.
Steve
|
Celebrating 10 years and 4000 posts on MacNN!
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jun 1999
Location: Las Vegas, NV, USA
Status:
Offline
|
|
|
|
|
|
|
|
|
|
|
Mac Elite
Join Date: Sep 2006
Location: Back in the Good Ole US of A
Status:
Offline
|
|
Originally Posted by ibook_steve
You don't need to worry about every little warning or error in the console. Just enjoy your new computer. This is not a big deal.
Steve
I beg to differ. The reason I noticed this in the first place was because every 10 seconds my CPU would spike. Not something I'm keen on ignoring.
|
|
|
|
|
|
|
|
|
Posting Junkie
Join Date: Mar 2004
Location: UK
Status:
Offline
|
|
I'm with Atheist (in more ways than one). I had a similar repeating issue caused by a dodgy install of Carbonite.
Its not just the CPU either, mine was writing 3-5 messages a second every few seconds to my log files so it affects disk performance too.
|
I have plenty of more important things to do, if only I could bring myself to do them....
|
|
|
|
|
|
|
|
Moderator
Join Date: Oct 2001
Location: San Jose, CA
Status:
Offline
|
|
Originally Posted by Atheist
I beg to differ. The reason I noticed this in the first place was because every 10 seconds my CPU would spike. Not something I'm keen on ignoring.
Well, you didn't mention that.
I usually wipe the disk and do a clean install on a new machine. If deleting the file mentioned didn't help, that's what I'd try.
Steve
|
Celebrating 10 years and 4000 posts on MacNN!
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jun 1999
Location: Las Vegas, NV, USA
Status:
Offline
|
|
Originally Posted by ibook_steve
I usually wipe the disk and do a clean install on a new machine.
That's extreme and in my opinion, unproductive. It's a new machine! If you wipe it and do a clean install you'll have exactly the same software configuration afterward as you had before.
|
|
|
|
|
|
|
|
|
Mac Elite
Join Date: Sep 2006
Location: Back in the Good Ole US of A
Status:
Offline
|
|
Removing the errant plist file did the trick. I've got two friends with brand new 11" MBAs and neither had that file.
Odd to say the least. I assumed the OS image was the same regardless of the device.
|
|
|
|
|
|
|
|
|
Moderator
Join Date: Oct 2001
Location: San Jose, CA
Status:
Offline
|
|
Originally Posted by chabig
That's extreme and in my opinion, unproductive. It's a new machine! If you wipe it and do a clean install you'll have exactly the same software configuration afterward as you had before.
Not necessarily. The final image put on at the factory may have been put on the machines before the final disks were pressed for distribution. The disks also do not include factory debugging code, which is used for testing before wiping the drive and replacing with a final image on the assembly line.
They should be identical, but there is a chance that they are not, causing the issue found here, which could be fixed with an OS reinstall from optical disk.
Steve
|
Celebrating 10 years and 4000 posts on MacNN!
|
|
|
|
|
|
|
|
Mac Elite
Join Date: Sep 2006
Location: Back in the Good Ole US of A
Status:
Offline
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|