Stray process killed by launchd

Hi there,
I am trying to make launchd restart a Java daemon in my Mac. I finally made my plist file work. I use a shell script that kills old java process and starts it from scratch. It works but right after the shell script finishes executing launchd kills the java process with the following error:
Mar 26 21:28:42 Micaias com.apple.launchd[1] (com.skios.smtpserver[8377]): Stray process with PGID equal to this dead job: PID 8383 PPID 1 bash
Can I make launchd not to worry about that process? That is the pourpose of the plist file... here it is by the way:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Disabled</key>
<true/>
<key>Label</key>
<string>com.skios.smtpserver</string>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Applications/ServEngineSMTPd/startSMTPserver.sh</string>
</array>
<key>StartInterval</key>
<integer>5</integer>
</dict>
</plist>
Thanks for any help/directions
Ignacio

try adding the following to your plist
<key>AbandonProcessGroup</key>
<true/>
then your launch daemon should look like this
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Disabled</key>
<true/>
<key>Label</key>
<string>com.skios.smtpserver</string>
<key>ProgramArguments</key>
<array>
<string>/bin/sh</string>
<string>/Applications/ServEngineSMTPd/startSMTPserver.sh</string>
</array>
<key>StartInterval</key>
<integer>5</integer>
<key>AbandonProcessGroup</key>
<true/>
</dict>
</plist>

Similar Messages

  • Repeated postfix "Stray process" chatter in log after update to 10.5.8

    After updating to 10.5.8 (via combo updater), I've been getting a bunch of odd console messages, about every minute, along the lines of the following:
    com.apple.launchd[1] (org.postfix.master[6214]): Stray process with PGID equal to this dead job: PID 6216 PPID 1 qmgr
    The dead job alternates seemingly at random between qmgr and pickup (both of which I can see running via Activity Monitor (owned by _postfix), and the PID increases steadily. A Google search turned up a few things along the lines of this older thread:
    http://discussions.apple.com/thread.jspa?messageID=8141721
    ...but they largely seemed to be from people who actually were doing something with postfix, which I'm not. This is a 2009 mini with a pretty much stock OS install; I certainly haven't done anything at that low of a level, and I'm in fact not even using Mail on that system (it's a media center/file server).
    The only persistent process that's running that I can imagine would have anything to do with this is Growl, which I do happen to be using to send myself notifications of failed backups. Disabling Growl didn't seem to make any difference, though.
    Anybody else seen this with 10.5.8, or have any suggestions about why it might be happening? It seems to be functioning fine, but I kinda don't like bloated log files, and I like randomly spawned/killed processes without understanding them even less.

    Addendum:
    I just saw this in my system log, no idea what exactly it's about:
    Aug 21 11:37:26 FrontRow blued[51]: Potentially fatal Bluetooth firmware error condition detected:
    Aug 21 11:37:26 FrontRow blued[51]: PSKeyUser0: len = 4, error = 0x0, psKey=650, Data: 0000B22300001800
    Aug 21 11:37:26 FrontRow blued[51]: PSKeyUser1: len = 4, error = 0x0, psKey=650, Data: 0000B22300001800
    Aug 21 11:37:26 FrontRow blued[51]: Attempting repair...
    Aug 21 11:37:27 FrontRow blued[51]: Repair complete: error = 0x0
    The condition persists, and the usual ad nauseum errors resumed. Wish I didn't have to sign up to ADC to submit a conventional bug that I could update with new content like this.

  • Stray process for Postfix on a server not hosting Mail

    I have three servers and each does different stuff. Well my web server has been showing an error constantly over and over again and it won't stop. It says it has to do with postfix and I'm not even running mail services on that server. So I'm not sure why it keeps showing it over and over again. Here is the error below.
    Thanks.
    Jul 14 09:18:35 xpmedia3 com.apple.launchd[1] (org.postfix.master[60298]): Stray process with PGID equal to this dead job: PID 60303 PPID 1 smtp

    Even with mail services disabled, SMTP is set to be used on demand (think cron job, web form, etc.).
    To completely disable it, issue:
    sudo /bin/launchctl unload -w /System/Library/LaunchDaemons/org.postfix.master.plist
    To re-enable:
    sudo /bin/launchctl load -w /System/Library/LaunchDaemons/org.postfix.master.plist

  • "Stray process with PGID equal to this dead job..." in Console

    I keep getting these errors in Console:
    24/06/08 11:36:18 AM com.apple.launchd[1] (org.postfix.master[2376]) Stray process with PGID equal to this dead job: PID 2378 PPID 1 qmgr
    24/06/08 11:36:18 AM com.apple.launchd[1] (org.postfix.master[2376]) Stray process with PGID equal to this dead job: PID 2377 PPID 1 pickup
    Any ideas what causes this?
    Thanks,
    James.

    Did you ever find out why these messages were happening and how to stop them?
    I have the same problem - once a minute, a new set of postfix log entries appear...
    Aug 20 10:45:16 devel com.apple.launchd[1] (org.postfix.master[619]): Stray process with PGID equal to this dead job: PID 620 PPID 1 pickup
    Aug 20 10:45:16 devel com.apple.launchd[1] (org.postfix.master[619]): Stray process with PGID equal to this dead job: PID 621 PPID 1 qmgr
    Aug 20 10:46:16 devel com.apple.launchd[1] (org.postfix.master[622]): Stray process with PGID equal to this dead job: PID 623 PPID 1 pickup
    Aug 20 10:46:16 devel com.apple.launchd[1] (org.postfix.master[622]): Stray process with PGID equal to this dead job: PID 624 PPID 1 qmgr
    Aug 20 10:47:16 devel com.apple.launchd[1] (org.postfix.master[625]): Stray process with PGID equal to this dead job: PID 627 PPID 1 qmgr
    Aug 20 10:48:16 devel com.apple.launchd[1] (org.postfix.master[628]): Stray process with PGID equal to this dead job: PID 630 PPID 1 qmgr
    Aug 20 10:49:16 devel com.apple.launchd[1] (org.postfix.master[631]): Stray process with PGID equal to this dead job: PID 633 PPID 1 qmgr
    Aug 20 10:50:16 devel com.apple.launchd[1] (org.postfix.master[634]): Stray process with PGID equal to this dead job: PID 635 PPID 1 pickup
    Aug 20 10:51:16 devel com.apple.launchd[1] (org.postfix.master[637]): Stray process with PGID equal to this dead job: PID 639 PPID 1 qmgr
    Aug 20 10:52:16 devel com.apple.launchd[1] (org.postfix.master[640]): Stray process with PGID equal to this dead job: PID 642 PPID 1 qmgr

  • Problem description: My iMac (early 2008) with OS 10.10.2 runs slow.  I have run EtreCheck several times, and I am unable to move beyond Problem System Launch Agents (11 processes killed due to memory pressure) and Launch Daemons (12 processes killed

    Problem description:
    My iMac (early 2008) with OS 10.10.2 runs slow.  I have run EtreCheck several times, and I am unable to move beyond Problem System Launch Agents (11 processes killed due to memory pressure) and Launch Daemons (12 processes killed).
    EtreCheck version: 2.1.8 (121)
    Report generated April 14, 2015 at 9:50:48 AM EDT
    Download EtreCheck from http://etresoft.com/etrecheck
    Click the [Click for support] links for help with non-Apple products.
    Click the [Click for details] links for more information about that line.
    Hardware Information: ℹ️
        iMac (24-inch, Early 2008) (Verified)
        iMac - model: iMac8,1
        1 3.06 GHz Intel Core 2 Duo CPU: 2-core
        4 GB RAM Upgradeable
            BANK 0/DIMM0
                2 GB DDR2 SDRAM 800 MHz ok
            BANK 1/DIMM1
                2 GB DDR2 SDRAM 800 MHz ok
        Bluetooth: Old - Handoff/Airdrop2 not supported
        Wireless:  en1: 802.11 a/b/g/n
    Video Information: ℹ️
        NVIDIA GeForce 8800 GS - VRAM: 512 MB
            iMac 1920 x 1200
    System Software: ℹ️
        OS X 10.10.2 (14C1510) - Time since boot: 4 days 20:29:22
    Disk Information: ℹ️
        Hitachi HDS721010KLA330 disk0 : (1 TB)
            EFI (disk0s1) <not mounted> : 210 MB
            Mac iBook HD (disk0s2) / : 999.35 GB (521.60 GB free)
            Recovery HD (disk0s3) <not mounted>  [Recovery]: 650 MB
    USB Information: ℹ️
        Apple Inc. Built-in iSight
        Apple, Inc. Keyboard Hub
            Apple, Inc Apple Keyboard
        Apple Computer, Inc. IR Receiver
        Apple Inc. BRCM2046 Hub
            Apple Inc. Bluetooth USB Host Controller
    Configuration files: ℹ️
        /etc/sysctl.conf - Exists
    Gatekeeper: ℹ️
        Mac App Store and identified developers
    Problem System Launch Agents: ℹ️
        [killed]    com.apple.CallHistoryPluginHelper.plist
        [killed]    com.apple.CallHistorySyncHelper.plist
        [killed]    com.apple.coreservices.appleid.authentication.plist
        [killed]    com.apple.icloud.fmfd.plist
        [killed]    com.apple.Maps.pushdaemon.plist
        [killed]    com.apple.printtool.agent.plist
        [killed]    com.apple.SafariNotificationAgent.plist
        [killed]    com.apple.sbd.plist
        [killed]    com.apple.scopedbookmarkagent.xpc.plist
        [killed]    com.apple.telephonyutilities.callservicesd.plist
        [killed]    com.apple.warmd_agent.plist
        11 processes killed due to memory pressure
    Problem System Launch Daemons: ℹ️
        [killed]    com.apple.AssetCacheLocatorService.plist
        [killed]    com.apple.ctkd.plist
        [killed]    com.apple.emond.aslmanager.plist
        [killed]    com.apple.icloud.findmydeviced.plist
        [killed]    com.apple.ifdreader.plist
        [killed]    com.apple.nehelper.plist
        [killed]    com.apple.nesessionmanager.plist
        [killed]    com.apple.periodic-daily.plist
        [killed]    com.apple.periodic-weekly.plist
        [killed]    com.apple.softwareupdate_download_service.plist
        [killed]    com.apple.wdhelper.plist
        [killed]    org.cups.cupsd.plist
        12 processes killed due to memory pressure
    Launch Agents: ℹ️
        [not loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
        [running]    com.adobe.AdobeCreativeCloud.plist [Click for support]
    Launch Daemons: ℹ️
        [loaded]    com.adobe.fpsaud.plist [Click for support]
        [loaded]    com.adobe.SwitchBoard.plist [Click for support]
        [running]    com.arubanetworks.via.NetworkMonitorLaunchd.plist [Click for support]
        [loaded]    com.microsoft.office.licensing.helper.plist [Click for support]
    User Launch Agents: ℹ️
        [loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
        [loaded]    com.adobe.ARM.[...].plist [Click for support]
        [loaded]    com.adobe.ARM.[...].plist [Click for support]
        [loaded]    com.google.keystone.agent.plist [Click for support]
        [running]    com.spotify.webhelper.plist [Click for support]
    User Login Items: ℹ️
        ChronoSyncBackgrounder    Application  (/Library/Application Support/ChronoSync/ChronoSyncBackgrounder.app)
        Dropbox    Application  (/Applications/Dropbox.app)
        Canon IJ Network Scanner Selector2    Application Hidden (/Library/Printers/Canon/IJScanner/Utilities/Canon IJ Network Scanner Selector2.app)
        Google Drive    Application  (/Applications/Google Drive.app)
    Internet Plug-ins: ℹ️
        Google Earth Web Plug-in: Version: 6.1 [Click for support]
        Default Browser: Version: 600 - SDK 10.10
        AdobeExManDetect: Version: AdobeExManDetect 1.1.0.0 - SDK 10.7 [Click for support]
        Flip4Mac WMV Plugin: Version: 3.1.0.24   - SDK 10.8 [Click for support]
        OVSHelper: Version: 1.1 [Click for support]
        AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 [Click for support]
        AdobePDFViewerNPAPI: Version: 11.0.10 - SDK 10.6 [Click for support]
        DivX Web Player: Version: 3.2.4.1250 - SDK 10.6 [Click for support]
        FlashPlayer-10.6: Version: 17.0.0.134 - SDK 10.6 [Click for support]
        Flash Player: Version: 17.0.0.134 - SDK 10.6 Outdated! Update
        iPhotoPhotocast: Version: 7.0
        QuickTime Plugin: Version: 7.7.3
        SharePointBrowserPlugin: Version: 14.4.8 - SDK 10.6 [Click for support]
        AdobePDFViewer: Version: 11.0.10 - SDK 10.6 [Click for support]
        Silverlight: Version: 5.1.20913.0 - SDK 10.6 [Click for support]
        JavaAppletPlugin: Version: 15.0.0 - SDK 10.10 Check version
    User internet Plug-ins: ℹ️
        WebEx: Version: 1.0 [Click for support]
        Google Earth Web Plug-in: Version: 7.1 [Click for support]
    3rd Party Preference Panes: ℹ️
        Adobe Version Cue CS2  [Click for support]
        Flash Player  [Click for support]
        Flip4Mac WMV  [Click for support]
        VIA PrefPane  [Click for support]
    Time Machine: ℹ️
        Time Machine not configured!
    Top Processes by CPU: ℹ️
             3%    WindowServer
             3%    Mail
             2%    com.apple.iCloudHelper
             1%    Creative Cloud
             1%    Google Chrome
    Top Processes by Memory: ℹ️
        223 MB    Google Chrome
        150 MB    Finder
        129 MB    Google Chrome Helper
        112 MB    Mail
        69 MB    Google Drive
    Virtual Memory Information: ℹ️
        35 MB    Free RAM
        1.45 GB    Active RAM
        1.45 GB    Inactive RAM
        888 MB    Wired RAM
        27.01 GB    Page-ins
        851 MB    Page-outs

    When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console 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 and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Process killed by SIGALRM randomly

    Hi,
    We have been observing a strange thing happening to our server processes (multithreaded) on Solaris 5.7. After running the servers for a while, they will be killed by "Alarm Clock". We are never explicitly using alarm in our code. So, the only thing that we can think of is the implementation of sleep because we do use sleep indirectly.
    According to the POSIX standard, sleep can be implemented using alarm. The default action to SIGALRM is terminating the process. It seems to be the case now. So if sleep is implemented using alarm, is it possible that the signal handler that sleep registers somehow got lost and the default action is used? Could it be related to multithreaded applications with signals?
    I appreciate any relevant information.
    Thanks in advance,
    Miranda

    Hi,
    We are using version 7 Solaris. And I believe we are having the latest thread patch and kernel. Please correct me if I am wrong. Our kernel ID is Generic_106541-14. The patch we have for libthread is 106980-15.
    We are not using usleep and we are using nanosleep. That's why we are suspecting that it's the implementation of some OS functions using alarm that causes this problem. Since the POSIX standard indicates that sleep can be implemented using alarm. Besides, I found another piece of information from the alarm(2) man page:
    Calling alarm() in a multithreaded process linked with
    -lthread (Solaris threads) and not with -lpthread (POSIX
    threads) currently behaves in the following fashion:
    o if the calling thread is a bound thread, the resulting
    SIGALRM is delivered to the bound thread's LWP, i.e.
    to the calling thread. There is a bug currently that
    this signal is not maskable via thr_sigsetmask(3T) on
    this bound thread.
    o if the calling thread is an unbound thread, the
    resulting SIGALRM is sent to the LWP on which the
    thread was running when it issued the call to alarm().
    This is neither a per-process semantic, nor a per-
    thread semantic, since the LWP could change threads
    after the call to alarm() but before the SIGALRM
    delivery, causing some other thread to get it possi-
    bly. Hence this is basically a bug.
    Our programs currently do not link with -lpthread, they only have -mt. And I believe we are using unbound threads. So according to the man page, there is a bug if sleep is implemented using alarm and SIGALRM is being sent to the wrong thread!? Does linking with -lpthread help? Should I get rid of the -mt?
    FYI, the output of the program when it is being killed is:
    <My program's output>
    Alarm Clock
    You can get the output above very easily by sending SIGALRM to any process which does not catch SIGALRM.
    Thanks,
    Miranda

  • Native process killed/terminated automatically

    Hi there,
    We have developed Mpeg-2 format streams Scheduling Aplication using JAVA
    that invokes a native WIN32(dll) library through JNI.
    This Win32(dll) Library further instantiate a COM Executable Server
    (CVPROS~1.EXE). The transmission starts sucessfully. But the EXE server
    is killed/terminated automaically without raising some exception at some
    unpredictable interval of time. It looks the COM EXE server is sub
    process of native WIN32Dll and JVM and JNI has not its direct reference.
    1- Possibly it look that Java's Garbadge collector kills this process
    assuming that its not being refered any where in project .
    2- Its being terminated due to some architectural problem .
    NOTE: if this Win32Dll is invoked through Win32 Client it works fine and
    COM exe Server is never termiated automatically.
    help required ???
    Thanks in advance.

    And why do you think it is being killed rather than it is terminating itself?
    If exit() is called in the C code, or some variation thereof, then the application will exit.
    If System.exit() is called in java then a java app will exit.

  • Can't stop the process com.apple.launchd.peruser.502

    Hi, I hope someone can help me!!
    This message is coming up everyday all day in the console and no matter what I do I can't stop it, I installed Tvmobili about 8 months ago and deleted it soon after. I have been wondering why my CPU is constantly active so looked in the console and found this:
    Oct 23 17:37:10 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15403]): posix_spawn("/Applications/TVMOBiLi.app/Contents/MacOS/tvmobiliqlhandler", ...): No such file or directory
    Oct 23 17:37:10 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15403]): Exited with exit code: 1
    Oct 23 17:37:10 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork): Throttling respawn: Will start in 10 seconds
    Oct 23 17:37:20 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15404]): posix_spawn("/Applications/TVMOBiLi.app/Contents/MacOS/tvmobiliqlhandler", ...): No such file or directory
    Oct 23 17:37:20 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15404]): Exited with exit code: 1
    Oct 23 17:37:20 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork): Throttling respawn: Will start in 10 seconds
    Oct 23 17:37:30 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15405]): posix_spawn("/Applications/TVMOBiLi.app/Contents/MacOS/tvmobiliqlhandler", ...): No such file or directory
    Oct 23 17:37:30 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15405]): Exited with exit code: 1
    Oct 23 17:37:30 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork): Throttling respawn: Will start in 10 seconds
    Oct 23 17:37:40 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15409]): posix_spawn("/Applications/TVMOBiLi.app/Contents/MacOS/tvmobiliqlhandler", ...): No such file or directory
    Oct 23 17:37:40 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork[15409]): Exited with exit code: 1
    Oct 23 17:37:40 doms-imac com.apple.launchd.peruser.502[189] (com.tvmobili.artwork): Throttling respawn: Will start in 10 seconds
    I've done everything I know, I've searched for it in Finder nothing has come back, I've reinstalled the application and deleted everything again but it still performs this every 10 seconds!
    Any advice is appreciated.
    Many thanks

    Check out > Configuring a DLNA Media Server
    Nice try, see how there blaming Apple for not having an uninstaller.

  • How do I stop Launchd from opening so many other processes?

    My computer has been running slow for some time even with without any applications open. On a whim, I created a new login account and it runs lickety split. I compared the Activity Monitor of both accounts and the old account is running 40 other processes associated with Launchd. One that has me baffled is called MAFL which is running PowerPC. It says the parent process is Launchd. When I try to quit MAFL it just won't quit. I searched on my computer and there is nothing called MAFL. I googled MALF and it says that it's associated with a MIDI device i had years ago on an old laptop, never this computer. How do i get rid of this thing?
    Here's what the process is listed as:
    91
    MAFL
    root
    0.0
    2
    156.00 KB
    642.15 MB
    PowerPC

    Mostly those are stored in plista in various folders...
    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for action in Safe Mode...
    Reboot, test again.
    If it only does it in Regular Boot, then it could be some 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed. Also look in System Preferences' Other row.
    Also look in these if they exist, some are invisible...
    /private/var/run/StartupItems
    /Library/StartupItems
    /System/Library/StartupItems
    /System/Library/LaunchDaemons
    /Library/LaunchDaemons

  • Firefox 4.0.1 hangs HARD on XP (cannot kill process)

    Multiple times is recent weeks (since the Firefox 4.0.1 update), Firefox has hung on my XP laptop after time (no other obvious influence) and CANNOT be killed! I have had to reboot every time, since no XP process-kill approach works. Presumably, there is no dump from Firefox either, since it just utterly locks up, quietly, and no longer responds to anything.

    In Tools->Options Advanced tab->Settings Firefox apparently defaults to
    Use system proxy settings
    and this causes all kinds of issues, including non-killable hangs, in a VPN/multi-network environment. Since I changed to
    Auto-detect proxy settings for the network
    several days ago, I have seen no problems. This is a welcome fix, since
    I otherwise really like Firefox, and was moving more and more to IE, which
    did not have the dead-connection and hang issues described above.

  • Firefox stops playing sound, closing Firefox leaves straggling processes running, kill those and sound returns, how to fix?

    Firefox 3.6.8 just now on Ubuntu 9.10, but happens on 8.04-10.04 Ubuntu with related older Firefox versions.
    Problem is probably related to Youtube/Flash problems, but something gets stuck in Firefox. I can close the main instance of Firefox, but looking in 'top' I can still find processes running for Firefox (sometimes if I try to restart Firefox I will get a note that Firefox is already running). If I kill those 'runaway processes' then restart Firefox I have Youtube/etc sound back.
    When this happens all programs on the computer cannot produce sound. When processes killed then sound works all around.

    I was able to fix this problem on my computer in Windows 7. Try going to start/control panel/programs and then uninstall the flash plugin -
    then start browser again go to a flash video and when prompted install plugin again.
    This worked well for me let me know how everyone else makes out.

  • Time machine kills Wifi network!!

    I had recently posted a thread on TC forum "Weird shut down of TC" that my TC just shuts down routinely.
    I have a 1TB TC that has been working very well. I bought the new unibody MBP and the Time machine has been backing up quite nicely for past one month.
    I now have a problem that the TM aborts with a message the the drive could not be accessed due to network problems.
    My Wifi would be down, status light amber, after a while the status light would go off completely but the disk in TC would be spinning as can feel the spin vibrations. This would happen about every 45 minutes and only way to go back up was to unplug and plug.
    I now find that the culprit is time machine. This is what I tried sequentially:
    A. Rolled back to 7.3.1 firmware. Same problem.
    B. Switched off the TM from prefrences. It worked well for a day.
    C. Switched on the TM. As soon as TM backup started, I had the TC wifi freeze.
    D. updated to firmware 7.3.2 with TM turned on. Same problem
    E. Turned off the airport card, plugged in ethernet cable so now was not using the wifi but wired connection to the TC. Started the TM and again. SAME PROBLEM.
    F. Turned off TM, all was well for the entire day.
    G. Turned it back on and on the first back up attempt, the WiFi was killed again.
    I think now the problem may be with the size of the back up that TM is attempting. It does the 'prepare for back up' pretty quickly but once the back up starts, it kills the WiFi and aborts with a message that there is no network.
    Anyone have any idea if I should troubleshoot differently or diagnose this differently?
    Has anyone had a problem with TM with large back ups?

    Hi Alexandre,
    Thanks for the input. Sorry my profile was not updated. I am using MBPro 10.5.5.
    Here is the output from console which I think is the portion till the network went down. Could not find a way to attach the file.
    Thanks for any help you can give:
    Dec 7 08:50:36 Mehers-MB-Pro-2 kernel[0]: AFPSleepWakeHandler: waking up
    Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: Computer did wake up from sleep. Reschedule our timers!
    Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
    Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
    Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
    Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
    Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
    Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
    Dec 7 08:50:40 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
    Dec 7 09:26:38 Mehers-MB-Pro-2 ntpd[27]: time reset -0.527369 s
    Dec 7 09:34:27 Mehers-MB-Pro-2 SyncServer[3340]: SyncServer: Truth vacuumed. Next vacuum date 2008-12-21 09:34:24 +0500
    Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
    Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
    Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
    Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
    Dec 7 09:51:20 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
    Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup requested by user
    Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Starting standard backup
    Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network mountpoint /Volumes/Data-1 not owned by backupd... remounting
    Dec 7 09:51:34 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3360
    Dec 7 09:51:34 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network volume mounted at: /Volumes/Data
    Dec 7 09:51:36 Mehers-MB-Pro-2 hdiejectd[3374]: running
    Dec 7 09:51:37 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75690496 to: 75768832 (joffset 0x1d0f000)
    Dec 7 09:51:38 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
    Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: event logs in /Volumes/Backup of Meher’s MB Pro/.fseventsd out of sync with volume. destroying old logs. (524 2 54320)
    Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
    Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
    Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: log dir: /Volumes/Backup of Meher’s MB Pro/.fseventsd getting new uuid: 2EF5457F-ED49-4E27-A818-A80F61BCCB86
    Dec 7 09:51:47 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (906 > 0)
    Dec 7 09:51:52: --- last message repeated 1 time ---
    Dec 7 09:52:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
    Dec 7 09:52:17: --- last message repeated 1 time ---
    Dec 7 09:52:37 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
    Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: No beacon for too long time
    Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
    Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
    Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
    Dec 7 09:52:51: --- last message repeated 1 time ---
    Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9d22100
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9d22100.
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9d22100
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:2a:6e
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
    Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9d22100.
    Dec 7 09:52:55 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
    Dec 7 09:53:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
    Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
    Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
    Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
    Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
    Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
    Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
    Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
    Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
    Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
    Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
    Dec 7 09:53:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Data
    Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
    Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
    Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: No Ack
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
    Dec 7 09:53:17 Mehers-MB-Pro-2 configd[14]: AppleTalk startup
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: MAC AUTH succeeded
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Up on en1
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x7c92a00.
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x7c92a00
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:74:89
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: got dev 0x4dd6604
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: wireless interface detected.
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: up
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: attached
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x7c92a00.
    Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is coming UP
    Dec 7 09:53:23 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
    Dec 7 09:53:28 Mehers-MB-Pro-2 diskimages-helper[3365]: terminating disk1 - image is no longer available
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: rder First]
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: ] [IOType Read] [PBlkNum 722696] [LBlkNum 29801] [FSLogMsgID 1403590549] [FSLogMsgOrder First]
    Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write error (6)
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: HFS resolvelink: can't find iNode463676
    Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write failed - expected:12017024, actual: 1048576
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:28: --- last message repeated 1 time ---
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: [FSLogMsgOrder First]
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: 741] [FSLogMsgOrder First]
    Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in recoverIndex:recover canceled (live.0.)
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:28 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:28: --- last message repeated 1 time ---
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
    Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
    Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexCI in ContentIndexUpdateContent:Caught mach exception. Fun Fun Fun.
    Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in bool siwriteBackAndIndex(_SI*, __ContentIndex*, const __CFDictionary*, const __CFDictionary*, db_obj**, const __CFString*, int, bool, bool, bool, __SIUserCtx*, const __CFString*, int32_t, bool):ContentIndexUpdateContent failed
    Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in void setAttributes(siset_attrctx*, Boolean, long unsigned int):Couldn't update index.
    Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
    Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:29: --- last message repeated 1 time ---
    Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:30: --- last message repeated 1 time ---
    Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
    Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:30: --- last message repeated 1 time ---
    Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:30: --- last message repeated 1 time ---
    Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup failed with error: 26
    Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
    Dec 7 09:53:30: --- last message repeated 1 time ---
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:31: --- last message repeated 1 time ---
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:31: --- last message repeated 1 time ---
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:31: --- last message repeated 1 time ---
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:31: --- last message repeated 1 time ---
    Dec 7 09:53:31 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:32: --- last message repeated 1 time ---
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:32: --- last message repeated 1 time ---
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:32: --- last message repeated 1 time ---
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:32: --- last message repeated 1 time ---
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: close: journal 0x4e8ae08, is invalid. aborting outstanding transactions
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:32: --- last message repeated 1 time ---
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
    Dec 7 09:53:32 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
    Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 09:53:32: --- last message repeated 1 time ---
    Dec 7 09:53:34 Mehers-MB-Pro-2 com.apple.launchd[1] (com.apple.netauth.sysagent[3360]): Stray process with PGID equal to this dead job: PID 3363 PPID 1 check_afp
    Dec 7 09:53:40 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data, flags 0, pid 3414
    Dec 7 09:54:36 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
    Dec 7 09:54:55: --- last message repeated 7 times ---
    Dec 7 09:55:08: --- last message repeated 8 times ---
    Dec 7 09:55:12 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
    Dec 7 09:55:17: --- last message repeated 7 times ---
    Dec 7 09:59:07 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2c00 Autoneg capable 1
    Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
    Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
    Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
    Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
    Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x4fd2300.
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x4fd2300
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e1:0f:ab
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
    Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x4fd2300.
    Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766270
    Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766270
    Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766370
    Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766370
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766520
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766520
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766622
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766622
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766770
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766770
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767020
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767020
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767273
    Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767273
    Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
    Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
    Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
    Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
    Dec 7 09:59:16 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
    Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backup requested by user
    Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Starting standard backup
    Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
    Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
    Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
    Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
    Dec 7 10:01:00 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: posting to KEA EINPROGRESS for /Volumes/Data-1
    Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
    Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
    Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 found 1 filesystem(s) with problem(s)
    Dec 7 10:01:00 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
    Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
    Dec 7 10:01:05 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3441
    Dec 7 10:01:05 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
    Dec 7 10:01:05 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
    Dec 7 10:01:05 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Network volume mounted at: /Volumes/Data
    Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
    Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
    Dec 7 10:01:20 Mehers-MB-Pro-2 hdiejectd[3459]: running
    Dec 7 10:01:21 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75768832 to: 76011520 (joffset 0x1d0f000)
    Dec 7 10:01:22 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
    Dec 7 10:01:22 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
    Dec 7 10:01:22 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
    Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
    Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
    Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
    Dec 7 10:01:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (906 > 0)
    Dec 7 10:01:35: --- last message repeated 1 time ---
    Dec 7 10:01:38 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 unmounting 1 filesystems
    Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data-1, flags 524288, pid 40
    Dec 7 10:01:39 Mehers-MB-Pro-2 loginwindow[39]: No servers unresponsive
    Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
    Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
    Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
    Dec 7 10:01:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
    Dec 7 10:02:00: --- last message repeated 1 time ---
    Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: Link Down
    Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: interface en is going DOWN
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9cd4800
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: filter detached
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: down
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: detached
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9cd4800.
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9cd4800
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f4:e9:4f
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
    Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9cd4800.
    Dec 7 10:02:14 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
    Dec 7 10:02:20 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
    Dec 7 10:02:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2cff Autoneg capable 1
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x62aeb00
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x62aeb00.
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x62aeb00
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f5:10:a0
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
    Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x62aeb00.
    Dec 7 10:02:48 Mehers-MB-Pro-2 mDNSResponder[16]: Note: Frequent transitions for interface en0 (192.168.1.130); network traffic reduction measures in effect
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <1d89> can not be reopened due to deny modes or byte range locks (file has exclusive access).
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <token> can not be reopened due to deny modes or byte range locks (file has exclusive access).
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 10:02:55: --- last message repeated 1 time ---
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 10:02:55: --- last message repeated 1 time ---
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
    Dec 7 10:02:55: --- last message repeated 1 time ---
    Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).

  • Launchd and periodic: mail does not get sent

    Hello together,
    I have the same problem as reported in this thread:
    http://discussions.apple.com/thread.jspa?messageID=6241179
    According to the thread the problem seemed to be fixed in Mac OS X 10.5.2 but I have it in 10.5.5
    In short:
    Whenever periodic scripts are started by launchd they run but no email is sent even if there is a file /etc/periodic.conf set up to send email.
    Instead an entry appears in /var/log/system .log:
    com.apple.launchd[1] (com.apple.periodic-daily[307]): Stray process with PGID equal to this dead job: PID 363 PPID 1 sendmail
    If the periodic jobs are started in terminal with "sudo periodic daily" the mail is sent by the local mail system.
    Does anyone know, how to fix this.
    Thanks in advance
    Martin

    Jerry Levan1 wrote:
    Any suggestions on how to fix the problem?
    Jerry
    The problem:
    launchd is killing the mail process before it can send the email because it considers it a stray child process.
    That is what this line is telling you:
    "Nov 21 03:16:47 mbp com.apple.launchd[1] (com.apple.periodic-daily1904): Stray process with PGID equal to this dead job: PID 1969 PPID 1 sendmail"
    The solution:
    I added the following to my com.apple.periodic-daily.plist and the daily run output started being mailed to me again...
    <key>AbandonProcessGroup</key>
    <true/>
    Like so:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.
    com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Label</key>
    <string>com.apple.periodic-daily</string>
    <key>ProgramArguments</key>
    <array>
    <string>/usr/sbin/periodic</string>
    <string>daily</string>
    </array>
    <key>LowPriorityIO</key>
    <true/>
    <key>Nice</key>
    <integer>1</integer>
    <key>StartCalendarInterval</key>
    <dict>
    <key>Hour</key>
    <integer>3</integer>
    <key>Minute</key>
    <integer>15</integer>
    </dict>
    <key>AbandonProcessGroup</key>
    <true/>
    </dict>
    </plist>
    Make sure you unload and load com.apple.periodic-daily.plist after you make the change so it is seen by launchd...
    sudo launchctl unload /System/Library/LaunchDaemons/com.apple.periodic-daily.plist
    sudo launchctl load /System/Library/LaunchDaemons/com.apple.periodic-daily.plist
    Further details at:
    http://developer.apple.com/technotes/tn2005/tn2083.html#SECCAREFULWITHTHATFORKEU GENE
    Cheers,
    Darrell

  • Mailman vs Launchd

    I've built and installed Mailman 2.12 from current source code and have it running just fine under OS X Server 10.5.7, with on exception…
    If I start Mailman from the CLI, using +/usr/share/mailman/bin/mailmanctl -s start+, all is well.
    If I allow launchd to start it using the following Launch Daemon…
    +<?xml version="1.0" encoding="UTF-8"?>+
    +<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">+
    +<plist version="1.0">+
    <dict>
    + <key>Label</key>+
    + <string>org.list.mailmanctl</string>+
    + <key>OnDemand</key>+
    + <false/>+
    + <key>Program</key>+
    + <string>/usr/share/mailman/bin/mailmanctl</string>+
    + <key>ProgramArguments</key>+
    + <array>+
    + <string>mailmanctl</string>+
    + <string>-s</string>+
    + <string>start</string>+
    + </array>+
    + <key>ServiceIPC</key>+
    + <false/>+
    </dict>
    </plist>
    …I get an endless succession of…
    +Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner.+
    +Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python+
    +Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds+
    …complete with dawn-of-the-dead respawning processes.
    I configured Mailman to replicate OSXS's default locations, and it runs fine. It doesn't even break Server Admin, aside from my use of virtual domains which ServerAdmin of course can't handle.
    The only difference between my org.list.mailmanctl.plist and Apple's is my verb start, as opposed to Apple's startf. I'm baffled by startf, which is not supported by mailman and does nothing, either in the CLI or in org.list.mailmanctl.plist.
    Obviously this isn't fatal and there are even other ways to insure an automatic startup, but I use launchd for such things, Apple more or less deprecates other approaches, and it drives me nuts not to understand what's going on.
    Speak, oh voices of wisdom!
    -Bryan

    +something in the newer version that you absolutely had to have, feature-wise+
    Let's just I have control issues. In general, I find Apple's builds to be lackluster and poorly documented (PHP without GED? What planet are they on? LOL). In this case, I was unable to implement mailman virtual domains with the installed binary.
    +That error sounds like you didn't unload the plist before editing it+
    Thanks for the suggestion, but the problem has survived more loads, unloads, and restarts than I can count.
    Apple's undocumented use of startf apparently works only with Apple's binary. It's not in mailman's usual lexicon, and has no effect on other builds.
    Regards,
    Bryan

  • Launchd won't send email via shell script

    I'm trying to send an email via shell script. e.g. my shell script is something like this:
    #!/bin/sh
    echo testing | mail -s 'this is a test' [email protected]
    My launchdaemon runs the script: /usr/local/scripts/testscript.sh
    I know the script is working, because I added some debugging (I added a line: echo is this working and sure enough, "is this working" is showing up in the console) but the email part kicks off an error message about 30 seconds later: Stray process with PGID equal to this dead job: PID ### PPID 1 sendmail
    The script works when I run it with a cron job. But why wouldn't it work as a launchd item? And why is it I'm only having problems with the email segment of my scripts? I've tried other scripts and they all seem to work fine.

    There are no errors reported. I'm looking in /var/log/mail.log.

Maybe you are looking for