System.log flood by strange messages

Hi all, I've see this strange messages on my system.log it is a real flood:
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:51:00 Melchior-1 kernel[0]: m71482545 0
anyone known which process is doing that ?

Yup. Same issue here. It's quite disconcerting.

Similar Messages

System.log flooding - strange loop every 10sec.

Unfortunately for us, we decided to update the computers in our office to 10.5.
Among other problems our server has become unstable - it has spontaneusly crashed twice in two weeks.
I tried to find the reason by looking at logs and I found it quite difficult since now a couple of processes are for some reason looping all the time and flooding the system logs.
Can someone tell what this means? Something about MySql but we aren't supposed to running any as I know...
Feb 13 15:39:21 COMPUTERNAME /Applications/Server/Server Admin.app/Contents/MacOS/Server Admin[240]: Warning: accessing obsolete X509Anchors.
Feb 13 15:39:22: --- last message repeated 1 time ---
Feb 13 15:39:22 COMPUTERNAME org.mysql.mysqld[4715]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:39:22 COMPUTERNAME org.mysql.mysqld[4715]: Use --help to get a list of available options
Feb 13 15:39:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4715]): Exited with exit code: 1
Feb 13 15:39:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:39:32 COMPUTERNAME org.mysql.mysqld[4716]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:39:32 COMPUTERNAME org.mysql.mysqld[4716]: Use --help to get a list of available options
Feb 13 15:39:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4716]): Exited with exit code: 1
Feb 13 15:39:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:39:42 COMPUTERNAME org.mysql.mysqld[4717]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:39:42 COMPUTERNAME org.mysql.mysqld[4717]: Use --help to get a list of available options
Feb 13 15:39:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4717]): Exited with exit code: 1
Feb 13 15:39:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:39:52 COMPUTERNAME org.mysql.mysqld[4718]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:39:52 COMPUTERNAME org.mysql.mysqld[4718]: Use --help to get a list of available options
Feb 13 15:39:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4718]): Exited with exit code: 1
Feb 13 15:39:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:40:02 COMPUTERNAME org.mysql.mysqld[4719]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:40:02 COMPUTERNAME org.mysql.mysqld[4719]: Use --help to get a list of available options
Feb 13 15:40:02 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4719]): Exited with exit code: 1
Feb 13 15:40:02 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:40:12 COMPUTERNAME org.mysql.mysqld[4724]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:40:12 COMPUTERNAME org.mysql.mysqld[4724]: Use --help to get a list of available options
Feb 13 15:40:12 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4724]): Exited with exit code: 1
Feb 13 15:40:12 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:40:21 COMPUTERNAME /Applications/Server/Server Admin.app/Contents/MacOS/Server Admin[240]: Warning: accessing obsolete X509Anchors.
Feb 13 15:40:22 COMPUTERNAME org.mysql.mysqld[4739]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:40:22 COMPUTERNAME org.mysql.mysqld[4739]: Use --help to get a list of available options
Feb 13 15:40:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4739]): Exited with exit code: 1
Feb 13 15:40:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:40:22 COMPUTERNAME /Applications/Server/Server Admin.app/Contents/MacOS/Server Admin[240]: Warning: accessing obsolete X509Anchors.
Feb 13 15:40:32 COMPUTERNAME org.mysql.mysqld[4744]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:40:32 COMPUTERNAME org.mysql.mysqld[4744]: Use --help to get a list of available options
Feb 13 15:40:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4744]): Exited with exit code: 1
Feb 13 15:40:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:40:42 COMPUTERNAME org.mysql.mysqld[4745]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:40:42 COMPUTERNAME org.mysql.mysqld[4745]: Use --help to get a list of available options
Feb 13 15:40:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4745]): Exited with exit code: 1
Feb 13 15:40:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:40:52 COMPUTERNAME org.mysql.mysqld[4748]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:40:52 COMPUTERNAME org.mysql.mysqld[4748]: Use --help to get a list of available options
Feb 13 15:40:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4748]): Exited with exit code: 1
Feb 13 15:40:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:40:58 COMPUTERNAME mDNSResponder[45]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00811800 en0/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 13 (Permission denied) 766687827
Feb 13 15:41:02 COMPUTERNAME org.mysql.mysqld[4749]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:41:02 COMPUTERNAME org.mysql.mysqld[4749]: Use --help to get a list of available options
Feb 13 15:41:02 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4749]): Exited with exit code: 1
Feb 13 15:41:02 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:41:12 COMPUTERNAME org.mysql.mysqld[4754]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:41:12 COMPUTERNAME org.mysql.mysqld[4754]: Use --help to get a list of available options
Feb 13 15:41:12 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4754]): Exited with exit code: 1
Feb 13 15:41:12 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:41:22 COMPUTERNAME org.mysql.mysqld[4755]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:41:22 COMPUTERNAME org.mysql.mysqld[4755]: Use --help to get a list of available options
Feb 13 15:41:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4755]): Exited with exit code: 1
Feb 13 15:41:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:41:22 COMPUTERNAME /Applications/Server/Server Admin.app/Contents/MacOS/Server Admin[240]: Warning: accessing obsolete X509Anchors.
Feb 13 15:41:32: --- last message repeated 1 time ---
Feb 13 15:41:32 COMPUTERNAME org.mysql.mysqld[4769]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:41:32 COMPUTERNAME org.mysql.mysqld[4769]: Use --help to get a list of available options
Feb 13 15:41:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4769]): Exited with exit code: 1
Feb 13 15:41:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:41:42 COMPUTERNAME org.mysql.mysqld[4770]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:41:42 COMPUTERNAME org.mysql.mysqld[4770]: Use --help to get a list of available options
Feb 13 15:41:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4770]): Exited with exit code: 1
Feb 13 15:41:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:41:52 COMPUTERNAME org.mysql.mysqld[4772]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:41:52 COMPUTERNAME org.mysql.mysqld[4772]: Use --help to get a list of available options
Feb 13 15:41:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4772]): Exited with exit code: 1
Feb 13 15:41:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:42:02 COMPUTERNAME org.mysql.mysqld[4773]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:42:02 COMPUTERNAME org.mysql.mysqld[4773]: Use --help to get a list of available options
Feb 13 15:42:02 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4773]): Exited with exit code: 1
Feb 13 15:42:02 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:42:12 COMPUTERNAME org.mysql.mysqld[4778]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:42:12 COMPUTERNAME org.mysql.mysqld[4778]: Use --help to get a list of available options
Feb 13 15:42:12 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4778]): Exited with exit code: 1
Feb 13 15:42:12 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:42:22 COMPUTERNAME org.mysql.mysqld[4779]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:42:22 COMPUTERNAME org.mysql.mysqld[4779]: Use --help to get a list of available options
Feb 13 15:42:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4779]): Exited with exit code: 1
Feb 13 15:42:22 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:42:23 COMPUTERNAME /Applications/Server/Server Admin.app/Contents/MacOS/Server Admin[240]: Warning: accessing obsolete X509Anchors.
Feb 13 15:42:32: --- last message repeated 1 time ---
Feb 13 15:42:32 COMPUTERNAME org.mysql.mysqld[4793]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:42:32 COMPUTERNAME org.mysql.mysqld[4793]: Use --help to get a list of available options
Feb 13 15:42:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4793]): Exited with exit code: 1
Feb 13 15:42:32 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:42:37 COMPUTERNAME mDNSResponder[45]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00811800 en0/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 13 (Permission denied) 766786499
Feb 13 15:42:42 COMPUTERNAME org.mysql.mysqld[4796]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:42:42 COMPUTERNAME org.mysql.mysqld[4796]: Use --help to get a list of available options
Feb 13 15:42:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4796]): Exited with exit code: 1
Feb 13 15:42:42 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:42:52 COMPUTERNAME org.mysql.mysqld[4797]: /usr/libexec/mysqld: Too many arguments (first extra is '').
Feb 13 15:42:52 COMPUTERNAME org.mysql.mysqld[4797]: Use --help to get a list of available options
Feb 13 15:42:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld[4797]): Exited with exit code: 1
Feb 13 15:42:52 COMPUTERNAME com.apple.launchd[1] (org.mysql.mysqld): Throttling respawn: Will start in 10 seconds
Feb 13 15:42:56 COMPUTERNAME /Applications/Server/Server Admin.app/Contents/MacOS/Server Admin[240]: Warning: accessing obsolete X509Anchors.

It seems pretty clear that mysql is trying to load, but failing for some reason ('Too many arguments').
I doubt that's the cause of your instability, but it's easy to stop MySQL from loading. Open a terminal window and run:
sudo launchctl unload -w org.mysql.mysqld
Hopefully that'll clear up the logs and make it easier to spot the issue.

System.log flooded by mail

Hi
To analyze a crashing program, I looked into system.log and saw that it's flooded by messages from mail.
When I googled this I had almost no results, am I the only one bugged by this or am I missing something.
Is there a way to make mail logging less verbose?
The enormous IMAPMessageDetails are non informative and make the log unreadable.
The other entries I can live with, but is also too much for my taste.
Enormous blocks with
Oct 12 22:08:34 macbook Mail[268]: [LogIMAPMailboxSyncEngineActivity] <mail.net, INBOX>: Start sync. Message list is synchronized. Message details:
        <details>(
            "<IMAPMessageDetails: 0x608003228d80> libraryID=126909 uid=106 flags=0x2000005"
<lot of lines>
            "<IMAPMessageDetails: 0x60000142ebc0> libraryID=132741 uid=631 flags=0x2000001"
        )</details>
Oct 12 22:08:34 macbook Mail[268]: [LogIMAPMailboxSyncEngineActivity] <mail.net, INBOX>: Responses need to be processed
Oct 12 22:08:34 macbook Mail[268]: [IMAP Pool] INBOX <0x60000088d200> available to yield
Oct 12 22:08:34 macbook Mail[268]: [LogIMAPMailboxSyncEngineActivity] <mail.net, INBOX>: End sync
lines with
Oct 12 22:09:18 macbook Mail[268]: [LogSocketStreamEvents] Waiting on run loop for input stream to be readable -- socket: 0x6080006d42e0 -- thread: 0x600001e76b00
blocks with
Oct 12 22:09:19 macbook Mail[268]: [LogSocketStreamEvents] Scheduling input stream for bytes available callback on main run loop -- socket: 0x6080002c3b10 -- thread: 0x608001a67b80
Oct 12 22:09:19 macbook Mail[268]: [LogSocketStreamEvents] Unscheduling input stream for bytes available callback on main run loop -- socket: 0x6080002c3b10 -- thread: 0x608001a67b80
Oct 12 22:09:19 macbook Mail[268]: [LogSocketStreamEvents] Waiting on run loop for input stream to be readable -- socket: 0x6080002c3b10 -- thread: 0x60800186d5c0
Oct 12 22:09:19 macbook Mail[268]: [LogSocketStreamEvents] NSStreamEventHasBytesAvailable -- socket: 0x6080006d42e0 -- thread: 0x608000a65f40
Oct 12 22:09:19 macbook Mail[268]: [LogSocketStreamEvents] Unscheduled input stream from run loop after waiting to be readable -- socket: 0x6080006d42e0 -- thread: 0x608000a65f40

From the Mail menu bar, select
          Window ▹ Connection Doctor
In the window that opens, uncheck the box marked
          Log Connection Activity

System.log filling with error messages

After SL update my system.log if filling with error messages.
Does any process delete the system.log periodically?
What's causing this error? Getting thousands of them.
9/30/09 12:08:13 PM [0x0-0x12012].com.nowsoftware.nowxagent[181] at now.swing.NProgressBar.fixAppleAnimationBug(null:-1)

JHF45 wrote:
After SL update my system.log if filling with error messages.
Does any process delete the system.log periodically?
Yes. There are three automatic jobs that run daily, weekly, and monthly doing this sort of thing. They run in the early hours of the morning if your Mac is awake, or shortly after it wakes up if it was sleeping. In Leopard, if it was powered-off, they won't run; I don't know if it's the same in Snow.

Kernel logs flooded with ACPI messages

I just noticed that my kernel logs are full of messages like the following:
ACPI: EC: non-query interrupt received: switching to interrupt mode
These messages appear harmless enough, but I'd like to get rid of them... I've been Googling and so far haven't been able to find a workaround. Is there one? Would for instance booting with noapic get rid of this?
(I have no need for APIC FWIW, I use a single-core CPU.)

Gullible Jones,
If you are willing, you should try the latest RC kernel (it runs just fine here). The GPE storm detection code in drivers/acpi/ec.c was rewritten a few weeks ago, and there was a bug in it. The latest RC has a fix.
commit 7b4d469228a92a00e412675817cedd60133de38a
Author: Alexey Starikovskiy <[email protected]>
Date: Thu Nov 13 12:00:03 2008 +0300
ACPI: EC: count interrupts only if called from interrupt handler.
fix 2.6.28 EC interrupt storm regression
Signed-off-by: Alexey Starikovskiy <[email protected]>
Signed-off-by: Len Brown <[email protected]>

System.log flooded with kernel[0]: On Board Mode Message

The Kernel keeps sending this message, apparently at a rather brisk pace. It's been going on for over a month apparently*. It's ogooglebar, also. Any thoughts on what it is? I'm not observing anything wrong on the system, but it's annoying when I need to rummage through the logs for whatever reason.
Mar 31 11:29:50 McMacMac kernel[0]: *** kernel exceeded 500 log message per second limit - remaining messages this second discarded ***
Mar 31 11:29:51 McMacMac kernel[0]: On Board Mode
Mar 31 11:29:51 --- last message repeated 498 times ---
Mar 31 11:29:51 McMacMac kernel[0]: *** kernel exceeded 500 log message per second limit - remaining messages this second discarded ***
Mar 31 11:29:52 McMacMac kernel[0]: On Board Mode
Mar 31 11:30:13 --- last message repeated 1015 times ---
Mar 31 11:30:13 McMacMac kernel[0]: *** kernel exceeded 500 log message per second limit - remaining messages this second discarded ***
Mar 31 11:30:14 McMacMac kernel[0]: On Board Mode

Triple-click anywhere in the line below to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}'
Copy the selected text to the Clipboard (command-C).
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
Post any lines of output that appear below what you entered — the text, please, not a screenshot.

LOGGING IN AND STRANGER MESSAGE

Hi,
I have an major issue. I sign off from my laptop, however my contacts still can see me all day long and chat and call me. Pleae let me know what s wrong with my account.
Also I have received strange "Online.Notification@" suggesting me to log on [invalid URL]
Please let me know if there is any chance the stalker can log in my account from different laptop and server.
Thanks

maitruong44 wrote:Also I have received strange "Online.Notification@" suggesting me to log on [invalid URL]
Please let me know if there is any chance the stalker can log in my account from different laptop and server.
Thanks
those are scam callers. please visit the thread below for instructions and suggestions on how to deal with such unwanted and suspicious activities;
How to Handle Suspicious Calls, Messages and Contact Requests (Scam/Spam)
CONTACT SKYPE CUSTOMER SERVICE | HOW TO RECORD SKYPE VIDEO CALLS | HOW TO HANDLE SUPICIOUS CALLS AND MESSAGES | WINDOWS PROBLEMS TROUBLESHOOTING | SKYPE DOWNLOAD LINKS
MORE TIPS, TRICKS AND UPDATES AT
skypefordummies.blogspot.com

Console message and system.log

Hi,
in the console system.log always apear this message every 30 second:
+Feb 16 02:22:55 Macintosh SystemUIServer[346]: Error: ACInterfaceGetPower() called with invalid interface+
+Feb 16 02:23:25: --- last message repeated 5 times ---+
and every 5 second this other message:
16/02/08 02:40:55 SystemUIServer[346] Error: ACInterfaceGetPower() called with invalid interface
.. and the message look like an infinite loop message.
Is it a problem ?
And i can ear the Internal HD run always.
Thanks on advice for any help
Ale

I just went through a bunch of research on this on my own iMac G5. (BTW - do you have an iMac G5 or an iMac Intel Core Duo? It can't be both)
It comes down to the items that the SystemUIServer is trying to call. if you look at <homefolder>/Library/Preferences/com.apple.systemuiserver.plist and open it with TextEdit, you'll see that, among other things, it references 8 menuExtras -
Battery.menu
Displays.menu
TimeMachine.menu
Bluetooth.menu
AirPort.menu
Volume.menu
Clock.menu
User.menu
While logged in as an administrative user, I launched System Preferences, Activity Monitor, and the Console looking at *+All Messages+*. I got the same ACInterfaceGetPower() error every 5 seconds, too. So I went through the Preferences and deactivated each menu item above, but the messages continued to appear.
I had two items that might have been causing a problem. The first was the fact that I had the AirPort signal showing up in the menu bar, even though the Network location I have set up does not have AirPort as an available service. I added the Airport service back in, disabled the menu icon, removed the AirPort service again, and Applied the changes. I'm pretty sure the error message was still appearing at this point.
The big change came when I opened up Accounts. First, I went to the Login Items section for my current user. I noticed that the EyeTV Helper and an Adobe process were both there along with the iTunes Helper process. I removed the first two using the "-" at the bottom. That actually appeared to fix it, but I proceeded to the Login Options section and disabled *Fast User Switching*. That removes the users from the menu bar. By this time the only thing left in the menu bar was the Spotlight icon.
Switching over to Activity Monitor, I killed the SystemUIServer process. It restarted and the ACInterfaceGetPower() messages did not reappear. I then re-activated each item, one at a time, killing the SystemUiServer after each activation. Again, the messages did not appear. I did not re-activate Bluetooth or AirPort, since I do not need them.
I am no longer getting those messages and the system appears to be running fine right now.
I have an external monitor attached to the iMac G5 as well as 4 FireWire hard drives. I am connected to the outside world via FiOS and I have a 100 Mb CAT-5 connection to that router.

Push notification service fills the system log with errors

When I have the push notification service enabled, my system logs become filled with messages such as this:
Sep 8 22:54:54 xserve jabberd/c2s[2175]: [7] [::ffff:192.168.1.100, port=50064] connect
Sep 8 22:54:54 xserve jabberd/c2s[2175]: [7] [::ffff:192.168.1.100, port=50064] disconnect jid=unbound, packets: 0
They occur at a rate of about two every second. What does that message mean and how do I stop it?

When I took a look at push notification, I noticed that it was listening to a different port than what dovecot had been configured to use.(jabberd was set to listen to 5347, while Dovecot (email) was using the standard 5222 port for that open protocol. Not sure what the ichat server is set to use.
Eventually, I did manage to get it working by updating the push notification config to listen to 5222. But it made no real difference because thunderbird and mail.app prefer imap updatings instead of push notification. So I turned it off.
Not sure if this is of any help to you.
Message was edited by: JFMezei

System log query is flooded with the message.. WindowServer[]: WSSetTrackingAreaEnabled : Invalid tracking area

Hello apple community (: quick question
my system log query is flooded with the message..
"8/29/14 12:10:12.258 PM WindowServer[176]: WSSetTrackingAreaEnabled : Invalid tracking area 0x61000089f220"
it has shown me after i run Mavericks Cache Cleaner to clean my computer. in my Activity Log, WindowServer[176] is taking up anywhere from 5 - 20 cpu at a time. (maybe more haven't watched it for too long)
what do i do fix this? i recently updated to OS X and i haven't payed attention to the errors until now (i'm an idiot i know..) so i don't exactly know when it all started happening. sorry all just hoping someone will have an idea.
-Ali

What functional problem do you have, if any? Log messages are not a problem in themselves.

Strange message in system.log every 10 secods

I'm getting the following three lines in system.log whenever my computer is running:
Sep 14 19:54:55 dmm com.danga.memcached\[12466\]: bind(): Address already in use
Sep 14 19:54:55 dmm com.danga.memcached\[12466\]: failed to listen
Sep 14 19:54:55 dmm com.apple.launchd\[1\] (com.danga.memcached\[12466\]): Exited with exit code: 1
Sep 14 19:54:55 dmm com.apple.launchd\[1\] (com.danga.memcached): Throttling respawn: Will start in 10 seconds
What is this process and how do I either turn it off or make it work?

A little Goodling might help. Apparently, you installed Live Journal or something else that installed memcached from danga. It can't bind to an IP address to do its thing and is failing.

Flood on system.log kernel[0]: m71482545 0

Hi all, I've see this strange messages on my system.log it is a real flood:
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:58 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:58: --- last message repeated 2 times ---
Feb 27 00:50:58 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:50:59 Melchior-1 kernel[0]: m71482545 0
Feb 27 00:50:59: --- last message repeated 2 times ---
Feb 27 00:50:59 Melchior-1 kernel[0]: m407168d8
Feb 27 00:51:00 Melchior-1 kernel[0]: m71482545 0
anyone known which process is doing that ? After two months i have still this problem... Anyone have the same ? Please check your system.log with a grep Best regards

Having the same problem here, and it is slowing down the machine:
Aug 25 03:16:11 kroll kernel[0]: m407168d8
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m407168d8
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m407168d8
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
Aug 25 03:16:11 kroll kernel[0]: m71482545 0
The last time I tried, a reboot cured the problem, but only for so long.

SATA driver flooding System.log, filling up startup disk

My system.log seems to be filling up with SATA error messages, about 10 per second. The log is now so large that I can't even get the Console app to open it (only in Open Quick, which seems to show little snippets of the log only).
This seems to have started when I installed an Initio 1623 SATA controller as part of a GraniteDigital drive upgrade. The controller worked, the drives worked. I've since pulled the controller card, but it seems the driver continues to flood the log file!
The drivers for the controller are apparently built in to OSX (at least in 10.4.7...) so there is no way to update the driver separately.
Restarting the machine hasn't helped. For now, I have to keep moving files to other disks to keep this G5 functioning.
How can I A) delete the log file to gain some time?
B) make this error stop?
Thanks.

Well - maybe it isn't a SATA driver system.log. I can't read the system.log because it keeps refreshing so the data in on the screen for less than a second before it refreshes. AND there is so much disk thashing that the system is barely responsive.
The only visible log entries are:
Jul 19 04:28:10 Platinum kernel[0]: Inic1622: SATA - Int no command active (repeated about ten times)
Jul 19 04:28:10 Platinum kernel[0]: and active
and repeat....
The log file is showing a size of 4.5 GB

Wism occur strange message on management log

Hi there,
I got the strange messages on my wism(v4.1.158.0)
Jul 03 14:41:24.148 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:1a:70:a6:b9:fe
Jul 03 14:41:22.821 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:18:39:0b:93:04
Jul 03 14:41:22.820 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:18:39:0b:93:04
Jul 03 14:41:21.618 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:16:b6:92:d1:1e
Jul 03 14:41:21.601 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:16:b6:92:d1:1e
Previous message occurred 2 times.
Jul 03 14:41:21.600 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:16:b6:92:d1:1e
Jul 03 14:41:19.698 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:16:b6:92:d1:1e
Jul 03 14:41:19.688 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:16:b6:92:d1:1e
Previous message occurred 2 times.
Jul 03 14:41:19.687 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:16:b6:92:d1:1e
Jul 03 14:41:19.300 apf_foreignap.c:1246 APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on MSCB. MSCB still in init state. Address:00:1a:70:a6:b8:ff
And the clients have the MAC on the log couldn't forward any packet to the network.
I couldn't find any idea on the CCO.
Do you have any idea about this message?
regards,
Jongkwan

Found this.... Might help hopefully, but its just a brief description, but at the end, of course.... call TAC
Error Message %APF-1-REGISTER_IPADD_ON_MSCB_FAILED: Could not Register IP Add on
MSCB. [chars]. Address:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]
Explanation Could not Register IP Add on MSCB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Search for REGISTER_IPADD_ON_MSCB_FAILED
http://www.cisco.com/en/US/docs/wireless/controller/message/guide/msgs2.html

I am getting a warning need more space on my disk. I have checked the Console and there have been 4000 thousand messages in my system log in the last 2 days. I have emptied as many files as possible.

Hi
I am getting a warning on opening my mac saying I need more space as my setup disk is full. I have emptied many files as well as my Trash. I am planning to get an external drive for my photos, but it has been suggested that I check Console and under the system log the following message (of which they say 4000 messages have been logged in 2 days) '06/06/2014 16:08:23.341 com.apple.dynamic_pager: dynamic_pager: Need more space on the disk to enable swapping'. This is a copy of one of the items. It is from the system log. I really do not think I have enough files to warrant this warning, with the exception of photos. My storage shows 143 MB free out of 120.47. Thanks for any help.

First off, no MacBook Air can run 10.3 or earlier.
Secondly, are you sure you only have 143MB of storage free? That's seriously low. With MacBook Airs of 120 GB hard drives, or even 140 GB which is often the case when it says out of 120, you shouldn't allow your free space to go down below 20 GB. MB is 1024 fold less than a GB. So if you really have 143MB free on a MacBook Air, you are long past the minimum space you should be keeping it at, and need to start clearing a lot of space now*:
http://www.macmaps.com/diskfull.html
I'm asking this thread be moved to the MacBook Air forum,a as we can't say for certain what you have when you post in the 10.3 or earlier forum.

System.log flood by strange messages

Similar Messages

Maybe you are looking for