Console Message Every 10 Seconds

Can anyone help me understand why this message is being repeated in Console every 10 seconds throughout the day:
9/3/09 6:20:54 PM WDDriveManagerStatusMenu[223] * attempt to pop an unknown autorelease pool (0x838800)

I also emailed WD, here is my response dated 11/9/2009:
Thank you for contacting Western Digital Customer Service and Support. My name is Aristides
That software is still under beta phase related to that O/S. Besides that it is should work without any issues.
I hope that we have met your expectations today and that you are satisfied with our service. If you have any further questions, please reply to this email and we will be happy to assist you further.
Sincerely,
Aristides
Western Digital Service and Support
http://support.wdc.com
Probably need to keep checking WD support site for updated WD Drive Manager. I like being able to turn-off my Studio II using the power button. Can't do it without WD Drive Manager.
I also noticed that the error message occur much less frequent when the drive is ejected.

Similar Messages

  • Console messages every second

    I am getting "INFO NativeIoPipeManager:50 - Found candidates: 0" every second in the console. I have no clue when it started or what the cause can be. Any pointers appreciated.

    I am getting "INFO NativeIoPipeManager:50 - Found
    candidates: 0" every second in the console. I have
    no clue when it started or what the cause can be.
    Any pointers appreciated.
    Do you run camino browser?
    http://www.google.com/search?hl=en&lr=&q=NativeIoPipeManager&btnG=Search

  • Console Messages - Every 10 seconds

    I recently checked the Console Messages for my system and notice the following messages being posted every 10 seconds:
    com.apple.launchd[1] 1 Warning (org.xinetd.xinetd439) Exited with exit code: 1
    com.apple.launchd[1] 1 Warning (org.xinetd.xinetd) Throttling respawn: Will start in 10 seconds
    com.apple.launchd[1] 1 Error (org.xinetd.xinetd440) posix_spawnp("xinetd", ...): No such file or directory
    Is this normal?
    If not how should I go about troubleshooting the cause of these messages.
    I am a recent convert to Apple and OS X and not familiar with the terminology.
    Can anyone help?

    launchd is the system process responsible for launching (and relaunching) other system or background processes that your system needs to function correctly. It knows to do this based on lots of configuration files, each of which describes a unique process for launchd to monitor. Most of these configuration files are kept in /System/Library/LaunchDaemons/. You can take a look at some of them if you're curious -- they're just XML and usually pretty short.
    xinetd is another program/process/daemon (all these words are basically synonymous) that behaves very much like launchd. xinetd, however, is not created by Apple, but is an open source piece of software. OS X, pre 10.4, used to use xinetd to perform the actions now being done by launchd. As of 10.4, launchd replaced xinetd.
    For whatever reason on your system, launchd is trying to start xinetd. Odd. Have you recently installed something, perhaps via Mac Ports or Fink or something like that?
    Making this message stop is not overly difficult, since all you need to do is tell launchd to disable it as a service it monitors. This is easy to do from the command line, but since you're a new Mac user maybe that's not so simple An easier (i.e. graphical) way to accomplish the same thing is to download and install Lingon:
    http://lingon.sourceforge.net/
    This will allow you to browse these launchd configuration files and make changes to them. Via this program, you can disable xinetd and you should see those console messages stop.

  • PRUNING-6-TRIGJOIN message every second

    We have just upgraded two Cat6509 switches to the enhanced chassis and from Sup2 to Sup720-3B.
    We are using hybrid mode. CatOS version is 8-5-1 and IOS is 12.2(18)SXF.
    The switch has multiple Vlans, most of which have corresponding layer 3 interfaces on the MSFC. The 6509 is running alongside another one, with HSRP between the two on the layer 3 interfaces.
    Routing and switching appears to be working correctly in all cases. However, one of these 6509 switches is producing the message "PRUNING-6-TRIGJOIN:trunk 15/1- send trig join" every second, so I have to disable logging in order to do any work on the switch.
    I am concerned that this message being repeated over and over means something is not right, but I can't find any information which indicates what the problem might be.
    I am also concerned that if I enter "show trunk 15/1" only one Vlan (the management Vlan for the switch) is shown as forwarding on the trunk.

    This message indicates a VTP pruning message is triggered on the trunk due to a VLAN status change; [chars] is the module number/port number.
    It's merely an informative message, but since you receive it every second, you probably have a flapping VLAN/userport somewhere on the other end of that trunk.
    In any case:
    -Check with the switch which is behind the trunk
    -Check VTP settings on both end
    -shut/no shut your trunk port on both ends

  • +3,000 Mail.app Notes Sync Console Messages

    Hi!
    Thanks for looking at my question! 
    I seem to be generating +3000 console messages every few days that almost all relate to syncing, particularly notes sync, errors from Mail.app.  I do not know how to decipher these messages to find the root of the problem.  I have notes sync de-selected on each Mail account as well as de-selected on MobileMe prefs. 
    How do I avoid Mail continuing to generate these errors?

    Well, nothing helped, even with the latest 2 updates where Apple states they fixed bugs in Mail app. Thus I just bought "AirMail" it's very cheap and works awsome with full gmail support.
    NB. I've used MS outlook for a while but it was awful, now totally satisfied with "Airmail" it supports notification, very light weight, etc.
    cons: I found that it cached all the attachments I have on my gmail.

  • Brand new iMac and a ton of Console Messages already

    Hello all, I am new to OSX and Mac as I just purchased a 27" iMac 3.06 ghz model. I think I am having some issues with my Mac. I use a screen calibrator called Spyder3Pro and for some reason it generates a console message every couple minutes. The only thing I can think of is that it takes an ambient light measurement so, this could possible be why I am getting the messages. I am just not sure. Here are some of the messages:
    6/8/10 4:44:57 PM Spyder3Utility[118] * attempt to pop an unknown autorelease pool (0x8ac600)
    6/8/10 4:48:07 PM Spyder3Utility[118] * attempt to pop an unknown autorelease pool (0x8ad600)
    6/8/10 6:42:47 PM Spyder3Utility[118] * attempt to pop an unknown autorelease pool (0x8ac600)
    6/8/10 6:42:57 PM Spyder3Utility[118] * attempt to pop an unknown autorelease pool (0x1819600)
    6/8/10 6:49:07 PM Spyder3Utility[118] * attempt to pop an unknown autorelease pool (0x8ac600)
    6/8/10 6:50:07 PM Spyder3Utility[118] * attempt to pop an unknown autorelease pool (0x1819600)
    6/8/10 6:56:17 PM Spyder3Utility[118] * attempt to pop an unknown autorelease pool (0x8ad600)
    and then with Google Chrome I get these following Console messages:
    6/8/10 6:56:48 PM [0x0-0x19a19a].com.google.Chrome[2046] [0608/185648:WARNING:/b/slave/chrome-official-mac/build/src/chrome/app/breakpad _mac.mm(62)] Breakpad disabled
    6/8/10 6:56:58 PM [0x0-0x19a19a].com.google.Chrome[2046] [0608/185658:WARNING:/b/slave/chrome-official-mac/build/src/chrome/app/breakpad _mac.mm(62)] Breakpad disabled
    6/8/10 6:57:02 PM [0x0-0x19a19a].com.google.Chrome[2046] [0608/185702:WARNING:/b/slave/chrome-official-mac/build/src/chrome/app/breakpad _mac.mm(62)] Breakpad disabled
    6/8/10 6:57:02 PM [0x0-0x19a19a].com.google.Chrome[2046] Debugger() was called!
    6/8/10 6:58:55 PM [0x0-0x19a19a].com.google.Chrome[2046] [0608/185855:WARNING:/b/slave/chrome-official-mac/build/src/chrome/app/breakpad _mac.mm(62)] Breakpad disabled
    6/8/10 6:59:24 PM [0x0-0x19a19a].com.google.Chrome[2046] 2010-06-08 18:59:24.671 Google Chrome Helper[2356:207] __CFServiceControllerBeginPBSLoadForLocalizations received error 1100 from bootstraplookup2
    6/8/10 7:02:28 PM [0x0-0x19a19a].com.google.Chrome[2046] [0608/190228:WARNING:/b/slave/chrome-official-mac/build/src/chrome/app/breakpad _mac.mm(62)] Breakpad disabled
    6/8/10 7:02:28 PM [0x0-0x19a19a].com.google.Chrome[2046] Debugger() was called!
    6/8/10 7:02:58 PM [0x0-0x19a19a].com.google.Chrome[2046] [0608/190258:WARNING:/b/slave/chrome-official-mac/build/src/chrome/app/breakpad _mac.mm(62)] Breakpad disabled
    Is there a hardware problem or is there a conflict somewhere? Please help as this is my first Mac. The console thing says I have 4000 messages from 6/4/10. That does not seem right.

    Barney's right, philip . . .
    The console keeps track of every step . . .
    So of course there are going to be a lot of notations.
    It's the repeating over and over that means you have to pay attention.
    Most of the notations that you see are normal, usually.

  • Amavis is logging error messages every 10 seconds

    Hello,
    I noticed today that amavisd started to report error messages to the console log every 10 seconds as follows:
    4/13/10 9:25:26 AM org.amavis.amavisd[617] Can't send SIG 0 to process [62]: Operation not permitted at /usr/bin/amavisd line 11203.
    4/13/10 9:25:26 AM com.apple.launchd[1] (org.amavis.amavisd[617]) Exited with exit code: 1
    4/13/10 9:25:26 AM com.apple.launchd[1] (org.amavis.amavisd[617]) Exited with exit code: 1
    4/13/10 9:25:26 AM com.apple.launchd[1] (org.amavis.amavisd) Throttling respawn: Will start in 10 seconds
    This block of messages repeats itself every 10 seconds.
    This began after I restarted the server after it apparantly crashed last night. Otherwise, there were no changes to the system.
    Running Leopard Server 10.5.8 on an intel mac mini.
    I am wondering how to stop this?

    Found the following blog post at Geek Foibles which solved the problem:
    +AMAVISD NOT STARTING AFTER RESTARTING MAC OS X SERVER+
    +February 6, 2009, 4:31 am+
    +Filed under: Uncategorized | Tags: amavisd, bug, mac os x server, mail, spam filtering+
    +I had a recent spot of trouble with Mac OS X Server for a client who has mail services running. Due to a hardware issue I had to force off the server, but when I started it back up I noticed that while Postfix would accept mail from senders, it wouldn’t actually deliver it to the destination mailbox. Instead, I’d get this message in mail.log:+
    +postfix/error[7063]: 56118A83885: to=<[email protected]>, relay=none, delay=4776, delays=4776/0/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)+
    +The complaint that it wasn’t delivering mail due to an inability to connect to the local host suggested some sort of mail filter not running, of which there are two on Mac OS X Server: clamav (used for virus scanning) and amavisd (used for spam filtering). In my case it was easy to narrow it down, since clamav wasn’t enabled. I checked amavis.log and found that it hadn’t been updated since I’d restarted, so it seemed clear it wasn’t launching. By looking in system.log I could see launchd was trying to start it repeatedly since it was enabled in Server Admin, but it kept failing:+
    +Feb 5 23:59:36 hq org.amavis.amavisd[5404]: Can't send SIG 0 to process [68]: Operation not permitted at /usr/bin/amavisd line 11203.+
    +Feb 5 23:59:36 hq com.apple.launchd[1] (org.amavis.amavisd[5404]): Exited with exit code: 1+
    +Feb 5 23:59:36 hq com.apple.launchd[1] (org.amavis.amavisd): Throttling respawn: Will start in 10 seconds+
    +It was trying to kill process 68, which in my case was kadmind. This didn’t make sense since kadmind deals with Kerberos, something spam filtering has nothing to do with. Fortunately amavisd is a Perl script and it was giving me the line number, so I was able to open it and hunt down the offending code. I found that when amavisd starts, it looks to see if there’s already a PID file (located at /var/amavis/amavisd.pid), gets the PID out of that file and then tries to kill said PID. So, if another copy of amavisd is already running when you start it, it kills the old one so that they don’t conflict. Problem is, in my case the PID file was stale: it hadn’t been cleaned up after amavisd’s last run since I’d had to force off the system, and now the PID was in use by another, unrelated process that it doesn’t have permission to kill.+
    +amavisd does check to see if the PID file was created before the last system startup, which would allow it to ignore stale PID files, but it only does this after trying to kill the old process. This bug was fixed in December in version 2.6.2 of amavis, but unfortunately for Mac OS X Server users, Apple uses version 2.5.1 from May of 2007.+
    +Removing the stale PID file resolved the issue. Its removal allowed launchd’s next automatic attempt to start amavisd to succeed, then a few minutes later Postfix’s mail queue manager started being able to deliver all the mail queued during the downtime to the appropriate mailboxes.+

  • I was today invited to upgrade my iTunes when I logged on.  Update failed. Every time I now try to open iTunes I get error messages.  Second message reads "iTunes was not installed correctly. Please re-install iTunes. Error 7. Windows error 126"

    I was today invited to upgrade my iTunes when I logged on.  Update failed. Every time I now try to open iTunes I get error messages.  Second message reads "iTunes was not installed correctly. Please re-install iTunes. Error 7. Windows error 126". I now can't sync my iPhoneand I am worried that if I re-install I will lose all my contacts,calendar, notes, etc.

    I too had this problems (Windows 8.1).  A few weeks ago after the previous update before this version of itunes, I'd had a problem with the itunes store crashing and at that time I followed instructions to copy QTMovieWin.dll to the itunes folder, which fixed the store crashing.
    Today I fixed the problem by:
    Delete QTMovieWin.dll from C:\Program Files (x86)\iTunes.
    Uninstall ALL Apple Software using Control Panel / Programs and Features.  I uninstalled:
    iTunes
    QuickTime
    Apple Mobile Device Support
    Apple Application Support
    Apple Software Update
    Bonjour
    Delete the folders:
    C:\Program Files (x86)\iTunes
    C:\Program Files (x86)\Common Files\Apple
    Restart the computer
    Reinstall QuickTime
    Reinstall iTunes
    Everything works GREAT now, including the iTunes store.  You will not lose your media files, I got everything back, all my settings, playlists, etc.

  • Latest iTunes update problems with repeated error messages every 65 seconds??

    After this mornings' update of iTunes.  Problems with Applemobiledeviceservices.exe.  Error message every 65 seconds - software exception (oxc06d007e) occurred in the application at location 0x7c812fd3.
    How do I stop this?

    'The installer has insufficient privileges to modify this file C:\Program Files (x86)\Common Files\Apple\Apple Application Support\Web kit.resources\inspector\Images\Spinner Inactive Selected.gif.'
    That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
    XP instructions in the following document: How to perform disk error checking in Windows XP
    Vista instructions in the following document: Check your hard disk for errors
    Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
    Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
    Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

  • Repeating Console Message 10.6.5 on MacBook Air (Late 2010)

    I just finished setting up the system on a new MacBook Air (13" 1.83ghz). I'm getting the following console message that repeats every 10 seconds. How can I stop it? Thanks.
    12/22/10 6:01:29 PM com.apple.launchd[1] (com.apple.batteryd[487]) Exited with exit code: 1
    12/22/10 6:01:29 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
    12/22/10 6:01:39 PM com.apple.launchd[1] (com.apple.batteryd[488]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory
    12/22/10 6:01:39 PM com.apple.launchd[1] (com.apple.batteryd[488]) Exited with exit code: 1
    12/22/10 6:01:39 PM com.apple.launchd[1] (com.apple.batteryd) Throttling respawn: Will start in 10 seconds
    12/22/10 6:01:49 PM com.apple.launchd[1] (com.apple.batteryd[490]) posix_spawn("/usr/local/libexec/batteryd", ...): No such file or directory

    My parents new 13'' MacBook Air (late 2010) would not fall asleep. After resetting the SMC to no avail I checked the console and saw the exact same message. After deleting the plist and rebooting the machine it is falling asleep now.
    I never installed any third-party program relating to the battery and there is a folder called /usr/local however there is no sub-folder libexec nor did a "locate" in Terminal find the daemon batteryd.
    Came across a similar thread on the Japanese Apple discussion forum (clicky). Since I cannot read Japanese I can only guess at what the various posts say. There seems to be talk about it being an Apple software related issue specifically regarding the HAL.
    I checked on my MacBook Pro (mid 2010) and there is no such plist. Will check another 13'' MacBook Air when I get the chance.
    If you delete the file com.apple.batteryd.plist in the folder /System/Library/LaunchDaemons and reboot the machine the message in the console will go away.

  • Need help with really odd console messages

    Aloha all, I'm attempting to track down some problems I've been experiencing. When I check my Console log it is constantly giving me these readings about applications I no longer have on my machine. How can I get rid of these, if I don't even have the applications? These readings are constant every couple of minutes. Any assistance will be very greatly appreciated!
    Example:
    03 18, 08 March 18, 2008 10:00:35 AM com.apple.launchd[1] (com.bombich.ccc.scheduledtask.C7782179-80A3-4D75-AAEC-158A4335CA95) Throttling respawn: Will start in 10 seconds
    03 18, 08 March 18, 2008 10:00:35 AM com.apple.launchd[1] (com.app4mac.CheckUpAgent[1409]) posix_spawn("/Applications/CheckUp.app/Contents/MacOS/CheckUpAgent", ...): No such file or directory
    03 18, 08 March 18, 2008 10:00:35 AM com.apple.launchd[1] (com.app4mac.CheckUpAgent[1409]) Exited with exit code: 1
    03 18, 08 March 18, 2008 10:00:35 AM com.apple.launchd[1] (com.app4mac.CheckUpAgent) Throttling respawn: Will start in 10 seconds
    03 18, 08 March 18, 2008 10:00:45 AM com.apple.launchd[1] (com.bombich.ccc.scheduledtask.C7782179-80A3-4D75-AAEC-158A4335CA95[1410]) posix_spawnp("/Applications/Carbon Copy Cloner.app/Contents/Resources/ccchelper.app/Contents/MacOS/ccchelper", ...): No such file or directory
    03 18, 08 March 18, 2008 10:00:45 AM com.apple.launchd[1] (com.bombich.ccc.scheduledtask.C7782179-80A3-4D75-AAEC-158A4335CA95[1410]) Exited with exit code: 1
    03 18, 08 March 18, 2008 10:00:45 AM com.apple.launchd[1] (com.bombich.ccc.scheduledtask.C7782179-80A3-4D75-AAEC-158A4335CA95) Throttling respawn: Will start in 10 seconds

    jettyboy wrote:
    Mahalo for the quick reply. I'm a bit timid about using the Terminal, when I typed it a warning message appeared telling me I could do some real damage and asked for my password is this normal?
    that's normal. Also, you won't see your password when you type it in.
    Those console messages indicate that you have some software from app4mac installed.
    This Checkupagent, perhaps? You might want to try uninstalling it.
    The launch agent com.app4mac.CheckUpAgent.plist was installed by this program. Also check to see if there is anything related in your login items in accounts preferences.

  • TimeMachine Console messages lie!?

    Mac OS 10.6.8 on a MacBook Pro 13"
    I have just spent an incredibly frustrating week trying to solve what I now believe to be a non-problem on my machine, caused by the messages TimeMachine writes (or, perhaps, doesn't write) to the Console log.  I would like to understand what was actually going on, and am hoping someone out there can help fill in the blanks.
    A friend with a 15" MBP, also running 10.6.8, was having severe TimeMachine problems -- backups taking 2 hours to complete after minimal changes to the disk.  We discovered how to filter Console messages so that we were only seeing TM messages (File->New Database Search then "Sender Contains backupd" in the Database Search window).  Initially we found that TM was copying 165,000+ files for a total backup size in the KB or at biggest, a few MB.  I started using my MBP as a temporary staging disk in extracting backups in trying to solve the problem on his machine.
    In the end we reformatted his disk and reinstalled the system off his DVD.  After the initial, expected long backup we did another one, just to see what was transferred that time.  No more huge numbers of files...sighs of relief.  One further backup, just to make sure, and...uh-oh: the numbers of files being transferred in both manual backups were identical.  For a machine which contains upwards of 700,000 files, this did not seem reasonable, so we considered that the problem had only been reduced in severity.
    Then I decided to run a quick pair of backups on my machine, just to check that this behaviour was not somehow being transferred to mine during the extraction of backups mentioned above.  Whereas the Console messages for previous backup runs (from other days) reported different numbers of files, suddenly my machine was also exhibiting this strange behaviour of transferring the same numbers of files on every backup.  The numbers of files differed depending on the machine, but the pattern was constant for a given machine.  The usual pattern was that x number of files was transferred in the first backup pass (it appears that TM nearly always performs two passes, even though its window in System Prefs does not always show this) and then y number of files was transferred in the second pass.  An immediate subsequent backup would again show x files in the first pass and y files in the second.  And so on.  Sometimes the quantity of bytes transferred also followed this pattern, but not always.
    The reason that I say "usual", "sometimes" and "always" above is that at that point we discovered that one can restore a system "wholesale" from a TM
    backup, via the item in the Utilities menu when the machine is started up from the system DVD.  We had known clean backups to go back to, and our days then devolved into a pattern of (1) reformatting the HD, then (2) doing a wholesale restore from a clean backup, and then (3) trying to migrate files changed since that backup without triggering the strange behaviour (and failing, thus starting all over again).
    After several days of this, and a migration attempt performed with pairs of backups after each change migration, and migrating the changes as "manually" as possible (i.e. not copying or moving files in the Finder, but instead opening the newer version, copying the contents, opening the older version, replacing the contents, then saving) and finding that even that did not prevent the strange behaviour, we started looking for utilities which operate on TM backups.  We found TimeTracker and BackupLoupe, and finally were able to see what was actually in the backups.
    Imagine our surprise to find that for a backup which produced the following Console messages:
    17/08/12 11:12:22 am          com.apple.backupd[1751]          Starting standard backup
    17/08/12 11:12:22 am          com.apple.backupd[1751]          Backing up to: /Volumes/Rugged/Backups.backupdb
    17/08/12 11:12:23 am          com.apple.backupd[1751]          No pre-backup thinning needed: 5.06 GB requested (including padding), 495.96 GB available
    17/08/12 11:12:29 am          com.apple.backupd[1751]          Copied 1160 files (3 KB) from volume Nickee's MacBook.
    17/08/12 11:12:30 am          com.apple.backupd[1751]          No pre-backup thinning needed: 5.06 GB requested (including padding), 495.96 GB available
    17/08/12 11:12:36 am          com.apple.backupd[1751]          Copied 1160 files (164 bytes) from volume Nickee's MacBook.
    17/08/12 11:12:39 am          com.apple.backupd[1751]          Starting post-backup thinning
    17/08/12 11:12:40 am          com.apple.backupd[1751]          Deleted backup /Volumes/Rugged/Backups.backupdb/Nickee’s MacBook Pro/2012-08-16-151757: 495.96 GB now available
    17/08/12 11:12:40 am          com.apple.backupd[1751]          Post-back up thinning complete: 1 expired backups removed
    17/08/12 11:12:40 am          com.apple.backupd[1751]          Backup completed successfully.
    that the actual contents appear to be this: (both programs report the same contents, so either they are both wrong or they are both right)
    If we assume that both programs are right, then one must inescapably conclude one of the following two things about the TM messages in the Console:
    (1) they are lies
    (2) they are not the whole truth: that TM is indeed transferring those numbers of files, and then for some reason deleting most of them (and not reporting this)!
    This begs the questions:
    (a) If the files really are being transferred, then why is it the same number of files every time, the same pattern to each backup, when the backups are being initiated one after the other, i.e. surely there isn't the time for such numbers of files to be changed, and surely it isn't possible that it's exactly the same numbers of files every time?
    (b) If the vast majority of files transferred are being deleted, why?  And why are they being transferred in the first place?
    (c) If this is happening, why is the Console not advising of this?  TM appears to fulsomely report its behaviour -- why would it not report this?
    (d) What on earth are these files in any case?
    Any help in getting closer to an understanding of this phenomenon would be gratefully received.  Having just lost literally a week of our lives to it, it would be satisfying to at least know what it was!

    The number of files is always somewhat high.  We suspect it's counting metadata (such as permissions, extended attributes, etc.) separately.  Ordinarily that doesn't indicate a problem. 
    And yes, Time Machine often makes a second "pass," if changes were made during the first one.  Often it's so quick you won't see the messages on the preferences window, or if the sizes are about the same, you may not realize that they changed.
    However, if you frequently get file counts in the area of many thousands, with only a few KB or MB, that take extremely long, you may have a problem that seems unique to some users running 10.6.8.  A few of them were able to solve it by re-installing Snow Leopard, but only going back to 10.6.7, not 10.6.8, via the "combo" update.  See Installing the ''combo'' update and/or Reinstalling OSX.
    If you do go back to 10.6.7, be aware of the 3rd item in #D5 of Time Machine - Troubleshooting.

  • Slow time machine, console messages: mdworker: unable to talk to lsboxd, and mdworker 32:kCGErrorFailure:set a breakpoint@CGErrorBreakpoint()

    iMac: model indentifier: iMac11,3
    processor: 3.2GHz intel core i3
    Software: OSX lion 10.7.5
    Current problem: Time machine running extremely slowly as is computer. When time machine is "preparing to update" if I attempt to open any drive, that function freezes the computer. 
    I followed web advice to check for console message:  mdworker: unable to talk to lsboxd.  Found that to be present.  As recommended, I turned off computer, restarted in safe mode, logged in and restarted computer.  checked console, I see this same message and another message that may be problematic: mdworker: 32: kCGErrorFailure: set a breakpoint@CGErrorBreakpoint() to catch srrors as they are logged.
    Both these messages being recorded every few minutes in the console log.
    Any support would be greatly appreciated.
    thank you,

    Hello Mr Davis,
    Thanks for your willingness to help I really appreciate your assistance.
    I decided to watch what was happening a bit more to see if I could discern a pattern to the problem so that I could pose a more refined question.
    This am, after the computer was left on all night, I noticed time machine (TM) was running.  I opened the console window, and noted after entering "starting" in the search field corresponding to "all messages"  that hourly, there is a notation:
    date, time, then "starting standard backu" followed by date, time and starting post backup thinning". 
    However, then there is the entry below at 12:25:46am referring to "starting standard backup" and there is no subsequent entry in the log referring to thinning having occured.  I wonder if this corresponds to TM running now and I am guessing, ever since 12:25:46 am?
    Once again, it seems that the problem is that when TM is running in this fashion, the computer slows down tremendously and operating particular programs such as photo processing lightroom that require more power, become very slow in particular.
    I copied and pasted a section of the log as it seems to repeat the same sequence of information over and over all night long.  I did not copy and paste the entire log since 12:25:46 am, as I wanted to not paste an excessive amount of lines here, but can do that if you like.
    I hope I followed your directions correctly. thanks again, Jeff
    Console log:
    8/2/13 12:25:46.540 AM com.apple.backupd: Starting standard backup
    8/2/13 12:25:46.823 AM com.apple.backupd: Backing up to: /Volumes/LaCie 2 TB Backup for Mac/Backups.backupdb
    8/2/13 12:25:47.938 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11610]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:25:47.938 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11610]) Exited with code: 1
    8/2/13 12:25:47.938 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:27:27.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 1 -> 4) timed out after 100721 ms
    8/2/13 12:27:28.015 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11620]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:27:28.016 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11620]) Exited with code: 1
    8/2/13 12:27:28.016 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:29:08.092 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11630]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:29:08.093 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11630]) Exited with code: 1
    8/2/13 12:29:08.093 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:29:08.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 4 -> 3) timed out after 100746 ms
    8/2/13 12:29:19.346 AM applepushserviced: <APSCourier: 0x7fe44b908430>: Stream error occurred for <APSTCPStream: 0x7fe44b810ab0>: The operation couldn’t be completed. Connection reset by peer
    8/2/13 12:30:30.000 AM kernel: add_fsevent: unable to get path for vp 0xffffff8017720930 (system.log; ret 22; type 4)
    8/2/13 12:30:30.000 AM kernel: add_fsevent: unabled to get a path for vp 0xffffff8017720930.  dropping the event.
    8/2/13 12:30:48.171 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11642]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:30:48.171 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11642]) Exited with code: 1
    8/2/13 12:30:48.172 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:31:10.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 3 -> 2) timed out after 100738 ms
    8/2/13 12:32:28.263 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11652]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:32:28.263 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11652]) Exited with code: 1
    8/2/13 12:32:28.264 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:33:11.000 AM kernel: IOSCSIPeripheralDeviceType00::setPowerState(0xffffff800b0c8200, 2 -> 1) timed out after 100738 ms
    8/2/13 12:34:08.343 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11662]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:34:08.344 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11662]) Exited with code: 1
    8/2/13 12:34:08.344 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:35:48.420 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11672]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:35:48.420 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11672]) Exited with code: 1
    8/2/13 12:35:48.421 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:37:28.498 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11682]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:37:28.498 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11682]) Exited with code: 1
    8/2/13 12:37:28.498 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:39:08.577 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11692]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:39:08.577 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11692]) Exited with code: 1
    8/2/13 12:39:08.577 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:39:19.976 AM applepushserviced: <APSCourier: 0x7fe44b908430>: Stream error occurred for <APSTCPStream: 0x7fe44a444230>: The operation couldn’t be completed. Connection reset by peer
    8/2/13 12:40:48.654 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11702]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:40:48.655 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11702]) Exited with code: 1
    8/2/13 12:40:48.655 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:42:28.731 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11712]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory
    8/2/13 12:42:28.731 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11712]) Exited with code: 1
    8/2/13 12:42:28.731 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper) Throttling respawn: Will start in 10 seconds
    8/2/13 12:42:54.000 AM kernel: CODE SIGNING: cs_invalid_page(0x1000): p=11715[GoogleSoftwareUp] clearing CS_VALID
    8/2/13 12:44:08.810 AM com.apple.launchd.peruser.501: (com.zeobit.MacKeeper.Helper[11723]) posix_spawn("/Applications/MacKeeper.app/Contents/Resources/MacKeeper Helper.app/Contents/MacOS/MacKeeper Helper", ...): No such file or directory

  • 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.

  • Console Message - YP server not responding, still trying

    I am getting the following message in the CONSOLE MESSAGES app. It repeats every 10 seconds. The IP that is not responding is my old Windows PC that was connected to my router before I bought my iMac.
    How can I stop the computer from trying to connect to this IP address?
    20/11/08 10:54:10 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:54:20 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:54:30 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:54:40 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:54:50 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:55:00 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:55:10 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:55:20 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:55:30 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:55:40 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:55:50 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:56:00 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:56:10 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying
    20/11/08 10:56:20 AM com.apple.DirectoryServices[11] YP server for domain 192.168.0.100 not responding, still trying

    I found this response to the same situation on OSX
    10.5 and I am wondering if this is safe to carry out.
    Am I going to run into any problems if I do this?
    {quote}A fix for the ypbind errors in system log
    OS X 10.5 Leopard is showing these errors every ten seconds:
    ] com.apple.nis.ypbind[]: Domainname not set. Aborting.
    ] com.apple.launchd[1] (com.apple.nis.ypbind[]): Exited with exit code: 1
    ] rasalas-pro com.apple.launchd[] (com.apple.nis.ypbind): Throttling respawn: Will start in 10 seconds
    I fixed it as follows:
    Since ypbind is not used by OS X in 99.9% of installations, just turn it off.
    Edit the ypbind start-up definition
    sudo vi /System/Library/LaunchDaemons/com.apple.nis.ypbind.plist
    and change
    <true/>
    to
    <false/>
    Then shutdown the service
    sudo service com.apple.nis.ypbind stop
    I'm expecting that the "false" will keep it from restarting on reboot, but not quite sure about that.
    Also, for future reference
    sudo service --list
    will show all the 'services'...
    {quote}

Maybe you are looking for