Desktop MacPro Not Shutting down

Question

Level 1

16 points

Desktop MacPro Not Shutting down

Desktop MacPro w/OS 10.11.3.

My desktop will not fully shut down either manually via the dropdown menu or on scheduled shutdown. I gets to the black screen with an arrow I must manually force shutdown using the front button. I can't tell from the crash reporter what the problem is. I guess I don't know how to read it anyway so need help.

I have asked this question a time back but the responses did not solve the issue. I have removed some software, tested, and reinstalled same but with no positive results. It just seems to point to a software (Apple or 3d party) selection state I made in error, to many hard drives used for backups, or equipment failure. I wish I knew.

Suggestions are welcome.

MacBook Pro with Retina display, OS X El Capitan (10.11.3), Other Mac's linked to Airport

Posted on Feb 2, 2016 11:42 AM

Reply

Answer 1

lllaass

Level 10

210,411 points

Feb 2, 2016 12:21 PM in response to budspwr

When you force shutdown the crash report will not really help.

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

Look for entries before the one that starts with BOOT_TIME since that indicates the start of bootup

Reply

Answer 2

budspwr Author

Level 1

16 points

Feb 3, 2016 7:59 AM in response to lllaass

I could not find BOOT_TIME. I'll do a flag at shutdown and try again. The way reports are made, it's hard to get ahead of the process.

Reply

Answer 3

Feb 3, 2016 9:15 AM in response to budspwr

be sure to launch Activity Monitor and/or activate the force Quit window with Command-Option-Escape.

When your Mac will not shut down, sometimes the offending task will show up in their windows.

Reply

Answer 4

budspwr Author

Level 1

16 points

Feb 3, 2016 12:23 PM in response to budspwr

This what I have so far. Far to much data after shutdown attempt. I have been looking at TechToolProDaemon, NetUpdateAgent, & WiFiAgent. TechToolPro is more prevalent and a considerable more entries before the first entry shown below.

Hope this helps.

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 0 CoreGraphics 0x00007fff96197b98 CGSReleaseConnection + 386

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 1 CoreGraphics 0x00007fff96400d96 shutdown_server_connections + 87

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 2 CoreGraphics 0x00007fff96103559 CGSSnarfAndDispatchDatagrams + 874

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 3 CoreGraphics 0x00007fff961030b2 CGSGetNextEventRecordInternal + 84

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 4 CoreGraphics 0x00007fff96103003 CGEventCreateNextEvent + 48

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 5 HIToolbox 0x00007fff8be959d9 _ZL38PullEventsFromWindowServerOnConnectionjhP17__CFMachPortBoost + 102

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 6 HIToolbox 0x00007fff8be9594e _ZL14MessageHandlerP12__CFMachPortPvlS1_ + 51

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 7 CoreFoundation 0x00007fff87a7721c __CFMachPortPerform + 252

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 8 CoreFoundation 0x00007fff87a77109 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 9 CoreFoundation 0x00007fff87a77079 __CFRunLoopDoSource1 + 473

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 10 CoreFoundation 0x00007fff87a6eaab __CFRunLoopRun + 2171

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 11 CoreFoundation 0x00007fff87a6dfc8 CFRunLoopRunSpecific + 296

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 12 HIToolbox 0x00007fff8be8bd55 RunCurrentEventLoopInMode + 235

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 13 HIToolbox 0x00007fff8be8ba97 ReceiveNextEventCommon + 184

2/3/16 2:48:21.059 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 14 HIToolbox 0x00007fff8be8b9cf _BlockUntilNextEventMatchingListInModeWithFilter + 71

2/3/16 2:48:21.060 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 15 AppKit 0x00007fff884b1d96 _DPSNextEvent + 1067

2/3/16 2:48:21.060 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 16 AppKit 0x00007fff884b11c5 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

2/3/16 2:48:21.060 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 17 AppKit 0x00007fff884a5d28 -[NSApplication run] + 682

2/3/16 2:48:21.060 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 18 AppKit 0x00007fff8846efbe NSApplicationMain + 1176

2/3/16 2:48:21.060 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 19 TechToolProDaemon 0x0000000108d2d2e2 main + 34

2/3/16 2:48:21.060 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 20 libdyld.dylib 0x00007fff9013e5ad start + 1

2/3/16 2:48:21.060 PM TechToolProDaemon[6749]: CGSConnection: destruction backtrace:: 21 ??? 0x0000000000000001 0x0 + 1

2/3/16 2:48:21.472 PM mds[64]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:21.472 PM ARDAgent[6782]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:21.472 PM TechToolProDaemon[6749]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:21.472 PM loginwindow[6768]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:21.472 PM com.apple.xpc.launchd[1]: (com.apple.lsd[6788]) Service exited due to signal: Segmentation fault: 11

2/3/16 2:48:21.472 PM NetUpdateAgent[6783]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:21.472 PM diagnosticd[140]: error evaluating process info - pid: 6788, puniqueid: 6788

2/3/16 2:48:21.472 PM WiFiAgent[6781]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:21.594 PM ReportCrash[6731]: Saved crash report for lsd[6788] version 728.4 to /Library/Logs/DiagnosticReports/lsd_2016-02-03-144821_BBBMacProDescktop.crash

2/3/16 2:48:24.511 PM loginwindow[6768]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:24.511 PM com.apple.xpc.launchd[1]: (com.apple.lsd[6789]) Service exited due to signal: Segmentation fault: 11

2/3/16 2:48:24.511 PM TechToolProDaemon[6749]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:24.511 PM WiFiAgent[6781]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:24.511 PM NetUpdateAgent[6783]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:24.511 PM diagnosticd[140]: error evaluating process info - pid: 6789, puniqueid: 6789

2/3/16 2:48:24.511 PM loginwindow[6768]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:24.511 PM WiFiAgent[6781]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:24.511 PM NetUpdateAgent[6783]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:24.511 PM mds[64]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:24.511 PM symptomsd[318]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:24.633 PM ReportCrash[6731]: Saved crash report for lsd[6789] version 728.4 to /Library/Logs/DiagnosticReports/lsd_2016-02-03-144824_BBBMacProDescktop.crash

2/3/16 2:48:27.122 PM WiFiAgent[6781]: securityd_message_with_reply_sync Failed to talk to secd after 4 attempts.

2/3/16 2:48:27.228 PM loginwindow[6768]: USER_PROCESS: 6768 console

2/3/16 2:48:27.230 PM loginwindow[6768]: Login Window Launched /System/Library/CoreServices/Software Update.app/Contents/Resources/SoftwareUpdateLauncher.app

2/3/16 2:48:27.671 PM loginwindow[6768]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:27.671 PM loginwindow[6768]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:27.671 PM diagnosticd[140]: error evaluating process info - pid: 6790, puniqueid: 6790

2/3/16 2:48:27.672 PM NetUpdateAgent[6783]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:27.672 PM loginwindow[6768]: ERROR | -[Login1 launchRootSetupAssistantSpringboard] | Failed to launch /System/Library/CoreServices/Software Update.app/Contents/Resources/SoftwareUpdateLauncher.app (error -10827)

2/3/16 2:48:27.672 PM com.apple.xpc.launchd[1]: (com.apple.lsd[6790]) Service exited due to signal: Segmentation fault: 11

2/3/16 2:48:27.672 PM mds[64]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

2/3/16 2:48:27.672 PM WiFiAgent[6781]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:27.672 PM symptomsd[318]: LaunchServices: disconnect event received for service com.apple.lsd.mapdb

2/3/16 2:48:27.815 PM ReportCrash[6731]: Saved crash report for lsd[6790] version 728.4 to /Library/Logs/DiagnosticReports/lsd_2016-02-03-144827_BBBMacProDescktop.crash

2/3/16 2:48:57.000 PM bootlog[0]: BOOT_TIME 1454528937 0

Reply

Answer 5

budspwr Author

Level 1

16 points

Feb 3, 2016 11:43 PM in response to Grant Bennet-Alder

Periodically, my laptop will not shut down completely so looked into Console and found this just before BOOT-TIME:

2/3/16 10:07:20.291 PM com.apple.xpc.launchd[1]: (com.google.keystone.daemon[4296]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.google.Keystone.Daemon.UpdateEngine

My thinking is Google is screwing up the shutdown process, at least on my laptop but will check the desktop as well.

Reply

Answer 6

Feb 4, 2016 7:39 AM in response to budspwr

That message just tells you they are not using the latest API available. It does not indicate anything deadly.

Reply

Answer 7

budspwr Author

Level 1

16 points

Feb 4, 2016 10:01 AM in response to Grant Bennet-Alder

OK, what can I do now to help me get over this problem?

Reply

Answer 8

lllaass

Level 10

210,411 points

Feb 4, 2016 10:25 AM in response to budspwr

Run Apple hardware test:

Using Apple Hardware Test - Apple Support

Intel-based Macs: Resetting the System Management Controller (SMC)

About NVRAM and PRAM

- Try starting in Safe Mode

OS X: What is Safe Boot, Safe Mode?

- Boot to Recovery and repair the startup disk

OS X: About OS X Recovery - Apple Support

- If it is repairable reinstall the OSX

How to reinstall OS X on your Mac - Apple Support

- If you do not have a backup use disk utility to restore the internal disk to an external disk so you can try to recover data.

Then format the startup disk and do a fresh install of OSX

Then reinstall SOME apps and see what apps. Install more apps if no problem

Reply

Answer 9

budspwr Author

Level 1

16 points

Feb 4, 2016 3:01 PM in response to lllaass

I have done that as you suggest, however, it does not seem practicable/feasible when a large number of applications are stored for transfer. What would be better is to find a way to delete old apps w/o a mass uninstall program for apps no longer in use much like windows. Some programs like drawing apps are sometime used in spurts so what ones go and which one give trouble

What would seem to me is a nice way to find what apps are dormant and which seem to be aways needing the computer much like Adobe for frequent updates. Many apps just do it through the back door quietly.

Reply

Answer 10

lllaass

Level 10

210,411 points

Feb 4, 2016 3:09 PM in response to budspwr

Yes, y can uninstall unused apps. How you do it depends upon the specific app. Most apps can simply be removed by dragging the app from the Applications folder to the Trash. However, some require using the uninstaller that came with the app since those apps, like Windows apps, place stuff in a lot of places.

http://www.thexlab.com/faqs/uninstallingapps.html

Reply

Answer 11

budspwr Author

Level 1

16 points

Feb 4, 2016 3:29 PM in response to lllaass

Thanks. That's what I thought I might need to do. So, wish me luck since I'm really convinced I'm making any progress but I'm tying to keep a smile or two.

Reply