Forrest

Q: Mac shuts down after 10.11.15

After upgrading to 10.11.15, my Mac Pro (cylinder) is shutting down on it's own during the night.  The system is not going in to sleep mode, but it is powering off.  I have to use the power button to bring the system back up, and this has become very annoying in lieu of the work I'm trying to do.

 

I haven't changed any settings, such as Energy Saver, etc.   I do have "Power Nap" enabled, but I have been keeping my system powered on for other reasons, therefore I'm not putting the system to sleep mode.

 

So my question is, is this a bug that's been introduced?  Is anyone else encountering this problem and if so, is there a work around?

 

 

Thanks.

Mac Pro, OS X El Capitan (10.11.2)

Posted on May 24, 2016 9:06 AM

Close

Q: Mac shuts down after 10.11.15

  • All replies
  • Helpful answers

  • by lllaass,

    lllaass lllaass May 24, 2016 9:11 AM in response to Forrest
    Level 10 (188,027 points)
    Desktops
    May 24, 2016 9:11 AM in response to Forrest

    My 2013 MP is not having that problem

     

    • Note the time of the next unintended shutdown. After rebooting open the Console app in Finder>Applications>Utilities and look for log entries at the time of the shutdown. Post suspicious ones here.

    Look before the log entry that starts with BOOT_TIME since that is the first line of a bootup

  • by Forrest,

    Forrest Forrest May 24, 2016 9:19 AM in response to lllaass
    Level 1 (13 points)
    Apple Music
    May 24, 2016 9:19 AM in response to lllaass

    I see some entries that indicate something is going on, but I can't make sense of it.  Looks like it happened around 6:00am EST.   After that, you see when I booted the system up.   I did a search for BOOT_TIME and only got today's.

     

     

    Thank you.

     

     

     

     

    5/24/16 6:00:57.880 AM com.apple.backupd[2162]: Post-backup thinning complete: 1 expired backups removed

    5/24/16 6:00:57.904 AM UserEventAgent[45]: Failed to send message because the port couldn't be created.

    5/24/16 6:00:58.067 AM UserEventAgent[45]: Failed to send message because the port couldn't be created.

    5/24/16 6:00:58.116 AM com.apple.backupd[2162]: Backup completed successfully.

    5/24/16 6:01:01.118 AM com.apple.backupd[2162]: Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb

    5/24/16 6:01:47.757 AM launchservicesd[81]: SecTaskLoadEntitlements failed error=22

    5/24/16 6:01:47.761 AM launchservicesd[81]: SecTaskLoadEntitlements failed error=22

    5/24/16 6:01:47.801 AM AOUDownloadCount[2194]: ERROR|AOUDownloadCount.m|368L|Error:AOUDownloadCount::sendDownloadCountInfo:get DownloadCountInfo failed.

    5/24/16 6:01:47.803 AM appleeventsd[53]: SecTaskLoadEntitlements failed error=22

    5/24/16 6:02:07.470 AM com.apple.backupd[2162]: Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb

    5/24/16 6:02:59.667 AM com.apple.xpc.launchd[1]: (com.adobe.ARMDCHelper.cc24aef4a1b90ed56a725c38014c95072f92651fb65e1bf9c8e43c37 a23d420d[2195]) Service exited with abnormal code: 111

    5/24/16 6:04:19.837 AM com.apple.backupd[2162]: Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb

    5/24/16 6:05:23.937 AM mdworker[2128]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:23.937 AM mdworker[2137]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:23.937 AM mdworker[2132]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:23.938 AM mdworker[2135]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:23.938 AM mdworker[2160]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:23.938 AM mdworker[2147]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:23.939 AM mdworker[2192]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:34.930 AM diskarbitrationd[70]: mds [64]:20483 not responding.

    5/24/16 6:05:36.000 AM kernel[0]: hfs: unmount initiated on Time Machine Backups on device disk2s2

    5/24/16 6:05:39.114 AM com.apple.backupd[2162]: Ejected Time Machine disk image: /Volumes/Data/Monster Pro.sparsebundle

    5/24/16 6:05:39.125 AM mdworker[2197]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:39.125 AM mdworker[2199]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    5/24/16 6:05:39.000 AM kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data, flags 0, pid 2201

    5/24/16 6:05:39.000 AM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x3c4c3ce18bbacf4f

    5/24/16 6:05:39.000 AM kernel[0]: ASP_TCP Detach: Reply queue not empty?

    5/24/16 6:05:39.738 AM com.apple.backupd[2162]: Ejected Time Machine network volume.

    5/24/16 6:05:42.340 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 371 seconds.  Ignoring.

    5/24/16 6:05:42.340 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 371 seconds.  Ignoring.

    5/24/16 6:06:16.458 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 337 seconds.  Ignoring.

    5/24/16 6:06:16.458 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 337 seconds.  Ignoring.

    5/24/16 6:06:46.457 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 307 seconds.  Ignoring.

    5/24/16 6:06:46.457 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 307 seconds.  Ignoring.

    5/24/16 6:07:16.456 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 277 seconds.  Ignoring.

    5/24/16 6:07:16.456 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 277 seconds.  Ignoring.

    5/24/16 6:07:48.251 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 245 seconds.  Ignoring.

    5/24/16 6:07:48.252 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 245 seconds.  Ignoring.

    5/24/16 6:08:18.404 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 215 seconds.  Ignoring.

    5/24/16 6:08:18.404 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 215 seconds.  Ignoring.

    5/24/16 6:08:48.444 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 185 seconds.  Ignoring.

    5/24/16 6:08:48.444 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 185 seconds.  Ignoring.

    5/24/16 6:09:18.443 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 155 seconds.  Ignoring.

    5/24/16 6:09:18.443 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 155 seconds.  Ignoring.

    5/24/16 6:09:48.444 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 125 seconds.  Ignoring.

    5/24/16 6:09:48.444 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 125 seconds.  Ignoring.

    5/24/16 6:10:22.451 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 91 seconds.  Ignoring.

    5/24/16 6:10:22.452 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 91 seconds.  Ignoring.

    5/24/16 6:10:31.000 AM syslogd[46]: ASL Sender Statistics

    5/24/16 6:10:56.405 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 57 seconds.  Ignoring.

    5/24/16 6:10:56.406 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 57 seconds.  Ignoring.

    5/24/16 6:11:26.704 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 27 seconds.  Ignoring.

    5/24/16 6:11:26.705 AM com.apple.cts[45]: com.apple.coreduetd.knowledge: scheduler_evaluate_activity told me to run this job; however, but the start time isn't for 27 seconds.  Ignoring.

    5/24/16 6:20:31.000 AM syslogd[46]: ASL Sender Statistics

    5/24/16 6:22:35.029 AM com.apple.usbmuxd[82]: _SendAttachNotification Device dc:2b:2a:5d:bf:3e@fe80::de2b:2aff:fe5d:bf3e._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.

    5/24/16 6:22:35.030 AM com.apple.usbmuxd[82]: _SendAttachNotification Device dc:2b:2a:5d:bf:3e@fe80::de2b:2aff:fe5d:bf3e._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.

    5/24/16 6:22:59.106 AM iTunes[327]: Entered:_AMMuxedDeviceDisconnected, mux-device:61

    5/24/16 6:22:59.106 AM iTunes[327]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:61

    5/24/16 6:22:59.106 AM iTunes[327]: tid:1868f - Mux ID not found in mapping dictionary

    5/24/16 6:22:59.106 AM iTunes[327]: tid:1868f - Can't handle disconnect with invalid ecid

    5/24/16 6:26:44.575 AM com.apple.usbmuxd[82]: _SendAttachNotification Device dc:2b:2a:5d:bf:3e@fe80::de2b:2aff:fe5d:bf3e._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.

    5/24/16 6:26:44.575 AM com.apple.usbmuxd[82]: _SendAttachNotification Device dc:2b:2a:5d:bf:3e@fe80::de2b:2aff:fe5d:bf3e._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.

    5/24/16 6:26:50.625 AM iTunes[327]: Entered:_AMMuxedDeviceDisconnected, mux-device:62

    5/24/16 6:26:50.625 AM iTunes[327]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:62

    5/24/16 6:26:50.625 AM iTunes[327]: tid:1868f - Mux ID not found in mapping dictionary

    5/24/16 6:26:50.625 AM iTunes[327]: tid:1868f - Can't handle disconnect with invalid ecid

    5/24/16 12:00:26.000 PM bootlog[0]: BOOT_TIME 1464105626 0

  • by lllaass,

    lllaass lllaass May 24, 2016 9:46 AM in response to Forrest
    Level 10 (188,027 points)
    Desktops
    May 24, 2016 9:46 AM in response to Forrest

    I really have no idea. My MP will not sleep but it started before 10.11.5

  • by Forrest,

    Forrest Forrest May 24, 2016 9:47 AM in response to lllaass
    Level 1 (13 points)
    Apple Music
    May 24, 2016 9:47 AM in response to lllaass

    Thank you for responding, either way

     

    This really sounds like a bug, so hopefully others will chime in.

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder May 24, 2016 9:53 AM in response to Forrest
    Level 9 (60,714 points)
    Desktops
    May 24, 2016 9:53 AM in response to Forrest

    RE: your log:

     

    It looks like your backup completed successfully about 6:00. Then backup started spotlight indexing the backup. Before it finished, the drive may have disconnected.

     

    It appear that this may be a local drive disk2, but it seems to be using sparse bundles -- a sign of using a Network drive. Does this drive have an unusual history?

     

    Then it looks like all héll broke loose in the scheduler with request to run a job, starting at a future time. then that subsided.

     

    then around 6:20, it starts to attach a device, (maybe a Network device or USB device? ) complaining it appears on two interfaces, and mentioning mux-device.

    then iTunes seems to get involved, complain, possibly about that same device) and ... that's all.

  • by Forrest,

    Forrest Forrest May 24, 2016 9:54 AM in response to Grant Bennet-Alder
    Level 1 (13 points)
    Apple Music
    May 24, 2016 9:54 AM in response to Grant Bennet-Alder

    I have a Time Capsule, directly-attached to my Mac Pro.  I'm not using any other devices on the network for this.   Maybe I need to reboot the time capsule - or is there a way to do a disk repair on that volume, in case  of some issue?

     

    I'm unfamiliar with the scheduler, but I don't understand how/why a job would run at a future time - - that's rather odd.

     

    Thank you

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder May 24, 2016 10:11 AM in response to Forrest
    Level 9 (60,714 points)
    Desktops
    May 24, 2016 10:11 AM in response to Forrest

    I have a Time Capsule, directly-attached to my Mac Pro.

     

    usually that is connected across an Ethernet or possibly a Wi-Fi link. Is that the way yours is set up? if it is, then it is considered a Network Drive for Backup purposes and sparse bundle (disk image inside a file) is the "normal" way to store backups.

     

    do you have both Ethernet and Wi-FI active at the same time?

     

    Do you have both IPv4 and IPv6 active at the same time? for most Users, IPv4 should be active, and IPv6 should be set to Link-local only or Off. Both active can cause hangs.

     

    The scheduler is the heart of MacOS, determining what task gets use of the processor(s) next, on a fairly microscopic level. But that issue seems to have subsided, and not caused the hang.

     

    Are you also storing iTunes stuff on that Time Capsule drive?

     

    Verify, repair, or erase an AirPort Time Capsule drive - Apple Support

     

    .

  • by Forrest,

    Forrest Forrest May 24, 2016 10:15 AM in response to Grant Bennet-Alder
    Level 1 (13 points)
    Apple Music
    May 24, 2016 10:15 AM in response to Grant Bennet-Alder

    I only run the Mac on direct network connection to the Time Capsule.   WIFI is enabled on the Time Capsule but not the Mac Pro.   I did see the IPv6 addresses, but I had previously configured it to local-link-only, that was just fixed.

     

    I'm storing iTunes stuff on my local drive, but it's being backed-up on Time Capsule.

     

    The Time Capsule drive has a sparse.bundle -- that's the way it was set up.

     

     

    Thank you.

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder May 24, 2016 10:48 AM in response to Forrest
    Level 9 (60,714 points)
    Desktops
    May 24, 2016 10:48 AM in response to Forrest

    I'm storing iTunes stuff on my local drive,

     

    is that a USB drive?

     

    is it possible that drive is disconnecting and reconnecting during the night? Is it Bus powered or has its own Power supply?

  • by Forrest,

    Forrest Forrest May 24, 2016 12:05 PM in response to Grant Bennet-Alder
    Level 1 (13 points)
    Apple Music
    May 24, 2016 12:05 PM in response to Grant Bennet-Alder

    I meant to say, the "drive" is inside the Time Capsule itself.

  • by Forrest,

    Forrest Forrest May 25, 2016 9:05 AM in response to Forrest
    Level 1 (13 points)
    Apple Music
    May 25, 2016 9:05 AM in response to Forrest

    So, the system seems to be crashing rather than shutting down -- as the system checks the disk when it boots.

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder May 25, 2016 9:49 AM in response to Forrest
    Level 9 (60,714 points)
    Desktops
    May 25, 2016 9:49 AM in response to Forrest

    If a kernel panic occurs, information is added to a log file in the folder /Library/Logs/DiagnosticReports (Mac OS X v10.6), or later.

    these files are named with a Date&Time,  username, and  ".panic"