Abnormal Shut Down
My MacBook has begun to intermittently demonstrate an abnormal shut down. It appears to shut down properly, the screen goes blank, the drive stops, but when I close the cover the sleep indicator light begins to glow.
However, when I open the cover (the light goes out) the computer does not come back to life. I discovered I need to hold down the power button for several seconds to actually shut it down.
Then, on the next start, I get a message that the computer was abnormally shut down.
I have checked the processes, and made certain that no software is left running. I'm stumped. Any ideas?
Thanks
I have exactly the same problem, except for the error message at boot, I don't have any message.
my 2 years macbook, probabily after 10.5.3 update, SOMETIMES, when I shut down, have the same problem: black screen but the fan keeps working, and my mouse keeps on (I can see the light under my mouse).
I've tried to reset SMC holdin down the power button for several seconds at boot and I also tried to repair permissons...nothing...sometimes it shut down properly and sometimes not...
now I'll try to reset the PRAM..
but what's the problem? I use my macbook everyday in the same way: safari, thunderbird, amsn, word 2008, excel 2008, itunes, vlc...
It's a leopard problem o it's a smc problem?
if it's a leopard problem I can solve with a new installation...but if it's a smc I have to call the support...pay...etc..
Similar Messages
-
Abnormal Shut-Down Sequence After Power Supply Replacement ???
Before the repair, there was a spinning wheel on the blue screen before the shut-down. But now the machine just cuts the power completely the moment the blue screen appears. Do you guys think that there is something to do with the new power supply ?
Thanks for helping me !Going through the exact same issue started about 1.5 weeks ago thinking about giving up and buying a Mac mini for access and snow leopard.
-
Weblogic shutting down abnormally
hi my weblogic server is shutting down abnormally.when i checked the weblogic.log
file i could trace the following error i dont know whether this error is related to the abnormal shutdown of weblogic i am
copying the error message for your reference
ERROR: Mon Apr 08 13:20:00 CEST 2002:<W> <SSLListenThread> Connection rejected: 'Login
timed out after: '25000' ms on socket: 'Socket[addr=eurcic1.emea.citicorp.com/16
9.194.168.43,port=63988,localport=7003}''
please help me out with a solution at the earliest
Regards
SurenderIs it actually shutting down (ie is it clean)? or is it dying or hanging?
-
I have been edited a project for weeks. Today, a few minutes after opening the project to work on it again, my computer shut down abnormally. The timeline disappeared. All the media is still in the project but my edited timeline is gone. Please help!
You have 10.6 on that machine, I suggest you stick with it for performance, third party hardware and software reasons as long as possible.
Consider 10.8 (not 10.7) when it's released, because 10.7 and 10.8 will require a new investment in software and newer third party hardware as it requires newer drivers the old machines won't have. (forced upgrade because of software, really nice of them)
http://roaringapps.com/apps:table
Far as your Safari problem do these things until it's resolved:
1: Software Update fully under the Apple menu.
2: Check the status of your plug-ins and update (works for all browsers) also install Firefox and see if your problems continue. You should always have at least two browsers on the machine just in case one fails.
https://www.mozilla.org/en-US/plugincheck/
Flash install instructions/problem resolution here if you need it.
How to install Flash, fix problems
3: Install Safari again from Apple's web site
https://www.apple.com/safari/
4: Run through this list of fixes, stopping with #16 and report back before doing #17
Step by Step to fix your Mac -
Hello,
I have two very old iPod's that still work great and a new iTouch. I still have an old PowerBook G4 that works great. The only problems that I have are the fans always running very loud and it's very hot.
Anyways, I bought one of the first iMac G5's and it worked great for the first year. After that I had nothing, but problems. Very loud fan noise and it would always shut down even while just using Firefox. I was glad that Apple gave out an extended warranty on the iMac G5's. Of course they replaced the power supply and logic board a few times. I had to get Apple corporate involved and that's when they gave me a new intel-iMac.
I just hit the 2 year mark with my new intel-iMac. The computer has ran great, but now it shuts down on me for no reason. I don't have loud fan noise, but the case gets very hot! I hope it's not a hardware problem again. Could it be a software problem?
Below is my log file of the last crash:
Jul 13 19:01:27 localhost kernel[0]: hi mem tramps at 0xffe00000
Jul 13 19:01:28 localhost kernel[0]: PAE enabled
Jul 13 19:01:28 localhost kernel[0]: 64 bit mode enabled
Jul 13 19:01:28 localhost kernel[0]: standard timeslicing quantum is 10000 us
Jul 13 19:01:28 localhost kernel[0]: vmpagebootstrap: 253712 free pages
Jul 13 19:01:28 localhost kernel[0]: migtable_maxdispl = 71
Jul 13 19:01:28 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 13 19:01:28 localhost kernel[0]: 89 prelinked modules
Jul 13 19:01:28 localhost kernel[0]: ACPI CA 20060421
Jul 13 19:01:28 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
Jul 13 19:01:28 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Jul 13 19:01:28 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Jul 13 19:01:28 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 13 19:01:28 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Jul 13 19:01:28 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Jul 13 19:01:28 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 13 19:01:28 localhost kernel[0]: Started CPU 01
Jul 13 19:01:28 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Jul 13 19:01:28 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Jul 13 19:01:28 localhost kernel[0]: Security auditing service present
Jul 13 19:01:28 localhost kernel[0]: BSM auditing present
Jul 13 19:01:28 localhost kernel[0]: disabled
Jul 13 19:01:28 localhost kernel[0]: rooting via boot-uuid from /chosen: E2A4D71C-2C5C-492B-81AA-FABDCA405647
Jul 13 19:01:28 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Jul 13 19:01:28 localhost kernel[0]: USB caused wake event (EHCI)
Jul 13 19:01:28 localhost kernel[0]: USB caused wake event (EHCI)
Jul 13 19:01:28 localhost kernel[0]: FireWire (OHCI) Lucent ID 5901 PCI now active, GUID 001b63fffe8de00a; max speed s800.
Jul 13 19:01:28 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0@0 /IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDrive r/WDC WD2500AAJS-40RYA0 Media/IOGUIDPartitionScheme/Customer@2
Jul 13 19:01:28 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Jul 13 19:01:28 localhost kernel[0]: jnl: replay_journal: from: 3255296 to: 21396480 (joffset 0x7d01000)
Jul 13 19:01:28 localhost kernel[0]: CSRHIDTransitionDriver::probe:
Jul 13 19:01:28 localhost kernel[0]: CSRHIDTransitionDriver::start before command
Jul 13 19:01:28 localhost kernel[0]: CSRHIDTransitionDriver::stop
Jul 13 19:01:28 localhost kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Jul 13 19:01:28 localhost kernel[0]: HFS: Removed 4 orphaned unlinked files
Jul 13 19:01:28 localhost kernel[0]: Jettisoning kernel linker.
Jul 13 19:01:28 localhost kernel[0]: Resetting IOCatalogue.
Jul 13 19:01:28 localhost kernel[0]: Matching service count = 0
Jul 13 19:01:28 localhost kernel[0]: Matching service count = 0
Jul 13 19:01:28 localhost kernel[0]: Matching service count = 0
Jul 13 19:01:28 localhost kernel[0]: Matching service count = 0
Jul 13 19:01:28 localhost kernel[0]: Matching service count = 0
Jul 13 19:01:28 localhost kernel[0]: Matching service count = 0
Jul 13 19:01:28 localhost kernel[0]: Previous Shutdown Cause: 0
Jul 13 19:01:28 localhost kernel[0]: BTCOEXIST on
Jul 13 19:01:28 localhost kernel[0]: wl0: Broadcom BCM4328 802.11 Wireless Controller
Jul 13 19:01:28 localhost kernel[0]: 4.170.46.9IPv6 packet filtering initialized, default to accept, logging disabled
Jul 13 19:01:27 localhost mDNSResponder-108.6 (Jul 19 2007 11: 41:28)[31]: starting
Jul 13 19:01:27 localhost lookupd[40]: lookupd (version 369.8) starting - Mon Jul 13 19:01:27 2009
Jul 13 19:01:27 localhost memberd[39]: memberd starting up
Jul 13 19:01:28 localhost DirectoryService[44]: Launched version 2.1 (v353.6)
Jul 13 19:01:29 localhost usbmuxd[34]: usbmuxd-167 built for iTunesEightTwo on May 11 2009 at 13:36:48, running 32 bit
Jul 13 19:01:29 localhost diskarbitrationd[38]: disk0s2 hfs 64955A85-1720-3C08-B2FF-FF77C91746BC Macintosh HD /
Jul 13 19:01:29 localhost kernel[0]: yukon: Ethernet address 00:1b:63:96:01:17
Jul 13 19:01:29 localhost kernel[0]: AirPort_Brcm43xx: Ethernet address 00:1c:b3:71:ae:a7
Jul 13 19:01:29 localhost lookupd[62]: lookupd (version 369.8) starting - Mon Jul 13 19:01:29 2009
Jul 13 19:01:29 localhost kernel[0]: Registering For 802.11 Events
Jul 13 19:01:29 localhost kernel[0]: [HCIController][setupHardware] AFH Is Supported
Jul 13 19:01:29 Shamu configd[36]: setting hostname to "Shamu.local"
Jul 13 19:01:30 Shamu kernel[0]: WLCE_COUNTRY_CODECHANGED
Jul 13 19:01:30 Shamu kernel[0]: en1: 802.11d country code set to 'US'.
Jul 13 19:01:30 Shamu kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 5 6 7 8 9 10 11 1 2 3 4 5 6 7 36 40 44 48 52 56 60 64 149 153 157 161 165 40 48 56 64 153 161 36 44 52 60 149 157
Jul 13 19:01:31 Shamu kernel[0]: WLCE_COUNTRY_CODECHANGED
Jul 13 19:01:31 Shamu kernel[0]: en1: 802.11d country code set to 'X0'.
Jul 13 19:01:31 Shamu kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 5 6 7 8 9 10 11 1 2 3 4 5 6 7 36 40 44 48 52 56 60 64 149 153 157 161 165 40 48 56 64 153 161 36 44 52 60 149 157
Jul 13 19:01:32 Shamu kernel[0]: Authentication Mismatch failure
Jul 13 19:01:32 Shamu mDNSResponder: Adding browse domain local.
Jul 13 19:01:33 Shamu kernel[0]: MAC AUTH succeeded
Jul 13 19:01:33 Shamu /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Jul 13 19:01:34 Shamu loginwindow[67]: Login Window Started Security Agent
Jul 13 19:01:35 Shamu configd[36]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jul 13 19:01:35 Shamu configd[36]: posting notification com.apple.system.config.network_change
Jul 13 19:01:35 Shamu lookupd[77]: lookupd (version 369.8) starting - Mon Jul 13 19:01:35 2009
Jul 13 19:01:36 Shamu VersionCueCS2Daemon[155]: warning: VersionCueCS2Daemon not started by mach_init process (parent pid: 1)
Jul 13 19:01:37 Shamu configd[36]: target=enable-network: disabled
Jul 13 19:01:45 Shamu /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Currently connected to network 435E1
Thanks for your help!
JasonOkay, started up my computer last night just for a few mins. It crashed again when just checking my e-mail.
Jul 18 23:17:39 Shamu kernel[0]: System Wake
Jul 18 23:17:39 Shamu kernel[0]: USB caused wake event (EHCI)
Jul 18 23:17:48 Shamu configd[36]: posting notification com.apple.system.config.network_change
Jul 18 23:17:48 Shamu launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[617]: exited abnormally: Hangup
Jul 18 23:17:50 Shamu kernel[0]: Authentication Mismatch failure
Jul 18 23:17:52 Shamu kernel[0]: MAC AUTH succeeded
Jul 18 23:17:53 Shamu mDNSResponder: Repeated transitions for interface en1 (FE80:0000:0000:0000:021C:B3FF:FE71:AEA7); delaying packets by 5 seconds
Jul 18 23:17:54 Shamu lookupd[1092]: lookupd (version 369.8) starting - Sat Jul 18 23:17:54 2009
Jul 18 23:18:03 Shamu configd[36]: posting notification com.apple.system.config.network_change
Jul 18 23:18:03 Shamu lookupd[1096]: lookupd (version 369.8) starting - Sat Jul 18 23:18:03 2009
Jul 18 23:18:05 Shamu mDNSResponder: Repeated transitions for interface en1 (192.168.1.7); delaying packets by 5 seconds
Jul 18 23:20:56 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:21:00 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:21:08 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:21:20 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:21:39 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:21:56 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:22:02 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:22:06 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:22:10 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:22:14 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:22:58 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:23:16 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:23:53 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:24:04 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:24:23 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:34:03 Shamu kernel[0]: AirPort: Roam (Beacons Lost)
Jul 18 23:35:53 localhost kernel[0]: hi mem tramps at 0xffe00000
Jul 18 23:35:54 localhost kernel[0]: PAE enabled
Jul 18 23:35:54 localhost kernel[0]: 64 bit mode enabled
Jul 18 23:35:54 localhost kernel[0]: standard timeslicing quantum is 10000 us
Jul 18 23:35:54 localhost kernel[0]: vmpagebootstrap: 253712 free pages
Jul 18 23:35:54 localhost kernel[0]: migtable_maxdispl = 71
Jul 18 23:35:54 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 18 23:35:54 localhost kernel[0]: 89 prelinked modules
Jul 18 23:35:54 localhost kernel[0]: ACPI CA 20060421
Jul 18 23:35:54 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
Jul 18 23:35:54 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Jul 18 23:35:54 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Jul 18 23:35:54 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 18 23:35:54 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Jul 18 23:35:54 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Jul 18 23:35:54 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 18 23:35:54 localhost kernel[0]: Started CPU 01
Jul 18 23:35:54 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Jul 18 23:35:54 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Jul 18 23:35:54 localhost kernel[0]: Security auditing service present
Jul 18 23:35:54 localhost kernel[0]: BSM auditing present
Jul 18 23:35:54 localhost kernel[0]: disabled
Jul 18 23:35:54 localhost kernel[0]: rooting via boot-uuid from /chosen: E2A4D71C-2C5C-492B-81AA-FABDCA405647
Jul 18 23:35:54 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Jul 18 23:35:54 localhost kernel[0]: USB caused wake event (EHCI)
Jul 18 23:35:54 localhost kernel[0]: USB caused wake event (EHCI)
Jul 18 23:35:54 localhost kernel[0]: FireWire (OHCI) Lucent ID 5901 PCI now active, GUID 001b63fffe8de00a; max speed s800.
Jul 18 23:35:54 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0@0 /IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDrive r/WDC WD2500AAJS-40RYA0 Media/IOGUIDPartitionScheme/Customer@2
Jul 18 23:35:54 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Jul 18 23:35:54 localhost kernel[0]: jnl: replay_journal: from: 8706048 to: 16946176 (joffset 0x7d01000)
Jul 18 23:35:54 localhost kernel[0]: HFS: Removed 7 orphaned unlinked files
Jul 18 23:35:54 localhost kernel[0]: CSRHIDTransitionDriver::probe:
Jul 18 23:35:54 localhost kernel[0]: CSRHIDTransitionDriver::start before command
Jul 18 23:35:54 localhost kernel[0]: Jettisoning kernel linker.
Jul 18 23:35:54 localhost kernel[0]: Resetting IOCatalogue.
Jul 18 23:35:54 localhost kernel[0]: Matching service count = 0
Jul 18 23:35:54 localhost kernel[0]: Matching service count = 0
Jul 18 23:35:54 localhost kernel[0]: Matching service count = 0
Jul 18 23:35:54 localhost kernel[0]: Matching service count = 0
Jul 18 23:35:54 localhost kernel[0]: Matching service count = 0
Jul 18 23:35:54 localhost kernel[0]: Matching service count = 0
Jul 18 23:35:54 localhost kernel[0]: Previous Shutdown Cause: 0
Jul 18 23:35:54 localhost kernel[0]: CSRHIDTransitionDriver::stop
Jul 18 23:35:54 localhost kernel[0]: BTCOEXIST on
Jul 18 23:35:54 localhost kernel[0]: wl0: Broadcom BCM4328 802.11 Wireless Controller
Jul 18 23:35:54 localhost kernel[0]: 4.170.46.9IOBluetoothHCIController::start Idle Timer Stopped
Jul 18 23:35:54 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Jul 18 23:35:53 localhost memberd[40]: memberd starting up
Jul 18 23:35:53 localhost mDNSResponder-108.6 (Jul 19 2007 11: 41:28)[31]: starting
Jul 18 23:35:53 localhost lookupd[41]: lookupd (version 369.8) starting - Sat Jul 18 23:35:53 2009
Jul 18 23:35:53 localhost DirectoryService[44]: Launched version 2.1 (v353.6)
Jul 18 23:35:55 localhost usbmuxd[34]: usbmuxd-167 built for iTunesEightTwo on May 11 2009 at 13:36:48, running 32 bit
Jul 18 23:35:55 localhost kernel[0]: yukon: Ethernet address 00:1b:63:96:01:17
Jul 18 23:35:55 localhost diskarbitrationd[39]: disk0s2 hfs 64955A85-1720-3C08-B2FF-FF77C91746BC Macintosh HD /
Jul 18 23:35:55 localhost kernel[0]: AirPort_Brcm43xx: Ethernet address 00:1c:b3:71:ae:a7
Jul 18 23:35:55 localhost lookupd[62]: lookupd (version 369.8) starting - Sat Jul 18 23:35:55 2009
Jul 18 23:35:55 localhost kernel[0]: Registering For 802.11 Events
Jul 18 23:35:55 localhost kernel[0]: [HCIController][setupHardware] AFH Is Supported
Jul 18 23:35:55 Shamu configd[37]: setting hostname to "Shamu.local"
Jul 18 23:35:56 Shamu kernel[0]: WLCE_COUNTRY_CODECHANGED
Jul 18 23:35:56 Shamu kernel[0]: en1: 802.11d country code set to 'US'.
Jul 18 23:35:56 Shamu kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 5 6 7 8 9 10 11 1 2 3 4 5 6 7 36 40 44 48 52 56 60 64 149 153 157 161 165 40 48 56 64 153 161 36 44 52 60 149 157
Jul 18 23:35:57 Shamu kernel[0]: WLCE_COUNTRY_CODECHANGED
Jul 18 23:35:57 Shamu kernel[0]: en1: 802.11d country code set to 'X0'.
Jul 18 23:35:57 Shamu kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 5 6 7 8 9 10 11 1 2 3 4 5 6 7 36 40 44 48 52 56 60 64 149 153 157 161 165 40 48 56 64 153 161 36 44 52 60 149 157
Jul 18 23:35:58 Shamu kernel[0]: Authentication Mismatch failure
Jul 18 23:35:58 Shamu mDNSResponder: Adding browse domain local.
Jul 18 23:36:00 Shamu kernel[0]: MAC AUTH succeeded
Jul 18 23:36:00 Shamu /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Jul 18 23:36:00 Shamu loginwindow[67]: Login Window Started Security Agent
Jul 18 23:36:01 Shamu configd[37]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jul 18 23:36:01 Shamu configd[37]: posting notification com.apple.system.config.network_change
Jul 18 23:36:01 Shamu lookupd[77]: lookupd (version 369.8) starting - Sat Jul 18 23:36:01 2009
Jul 18 23:36:02 Shamu configd[37]: target=enable-network: disabled
Jul 18 23:36:02 Shamu VersionCueCS2Daemon[162]: warning: VersionCueCS2Daemon not started by mach_init process (parent pid: 1)
Jul 18 23:36:17 Shamu /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Currently connected to network 435E1
Thanks for any help,
Jason -
I've done all of the steps here: Remove unwanted adware that displays pop-up ads and graphics on your Mac - Apple Support but still have something that wants to be installed when I shut down my mac. I don't know what this is or how to get rid of it. Any suggestions please?
1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a general summary of what you need to do, if you choose to proceed:
☞ Copy a particular line of text to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.
5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is sometimes, but not always, slow, run the test during a slowdown.
You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. Load this linked web page (on the website "Pastebin.") The title of the page is "Diagnostic Test." Below the title is a text box headed by three small icons. The one on the right represents a clipboard. Click that icon to select the text, then copy it to the Clipboard on your computer by pressing the key combination command-C.
If the text doesn't highlight when you click the icon, select it by triple-clicking anywhere inside the box. Don't select the whole page, just the text in the box.
8. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:
[Process started]
Part 1 of 8 done at … sec
Part 8 of 8 done at … sec
The test results are on the Clipboard.
Please close this window.
[Process completed]
The intervals between parts won't be exactly equal, but they give a rough indication of progress. The total number of parts may be different from what's shown here.
Wait for the final message "Process completed" to appear. If you don't see it within about ten minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it and go to the next step. You'll have incomplete results, but still something.
12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.
Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed. -
Macbook Pro 10.6.8 won't shut down. Blue screen with spinning wheel.
it's an 15 inch macbook pro. since I bought this computer was working fine about last year. Somehow, start of this year, the problem begins. Everytime when i opened microsoft word 2011 on mac or Photoshop cs5, and quit the software as normaly. When i try to shut down the blue screen with spinning wheel apears. this spining wheel is endless. But funny thing is that after use other software such as games, web browser (safari) etc. and quit them. when i shut down there was not a problem. only word 2011 for mac and adobe photoshop cs5. Any solutions?
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.
☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.
Step 1
Select "system.log" from the file list. Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged during the time something abnormal was happening. That time might be before or after the boot.
For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. If the problem is a system crash or freeze, post the messages from before the boot time, when the system was about to crash or was failing to shut down. In either case, please include the BOOT_TIME message at the beginning or the end of the log extract.
Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
If the log doesn't go back far enough in time, scroll down in the Console file list to /private/var/log/system.log.0.bz2. Search that archived log, and if necessary the older ones below it, for the same information.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
Step 2
Do the same with kernel.log.
Step 3
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall or hang logs — they're very long and not helpful. -
How do I run a script at shut down?
Hi folks,
I wrote a script that runs at login that gets my dynamic IP and creates a simple web page with a link to my local computer address for Personal Web Sharing, and then uploads that web page with the link to my ISP homepage server.
I wrote another script that creates a web page with no link, but contains a message that my home computer is shut down.
This way, my ISP homepage can have a file that either points to my dynamic IP or has a message that my web server is down.
So How do I get the shut down script to run at shut down?
The shutdown script is basically just this to upload an existing html file:
curl -T shutdown_message.html -u userid:password ftp://ftp.web.isp.server.com/
or you can dynamically create an html file with current date and expected date you will be back on-line, or whatever, with some simple perl code.
Thanks.
G3 Desktop, SonnetEncoreZIF G4 1GHz, 768MB, WingsAV-6MB, DVR-106D, 60GB Maxtor Mac OS X (10.4.7) PCI: TempoUltraATA66-120GB Maxtor, 120GB Seagate; TangoUSB/FW; Radeon9200-17"LCDThanks, guys. For the most part I think the DSL keeps the same IP except when I power down. My power went out just as I finished my login upload script, so my first test was out of necessity, and it worked. I could set it up as a cron job on my local machine to regularly test the IP and upload the page.
reese, When I have a power loss, or non-planned abnormal shutdown, my web page will be out of sync, unless I use something on the ISP server, so that is a good point. I am not sure what kind of scripts I can run on my ISP web server. I don't know if I can set up a regularly scheduled script, or if it would only respond to requests, then it could perform the test on demand. I need to give that some more study. Good suggestion.
As far as a normal planned shutdown, I thought of one possible work around: to create a script that runs my upload and then executes the shutdown, either by AppleScript or UNIX shutdown command line, not sure which is the most graceful.
Gary, I looked in the /System/Library/StartupItems and found the Apache scripts in there. They have a StartService and StopService methods defined. I think I could use that as a template to create my own, or just add my scripts to the Apache methods. Since basically I want to run something as Apache is started and again when it stops. That may be the most graceful method. As Apache can get shut down when the machine remains on via System Preferences. You solved my problem Gary, but I marked your message as helpful already. Post back again and I'll give you the Solved Star & points.
G3 Desktop, SonnetEncoreZIF G4 1GHz, 768MB, WingsAV-6MB, DVR-106D, 60GB Maxtor Mac OS X (10.4.7) PCI: TempoUltraATA66-120GB Maxtor, 120GB Seagate; TangoUSB/FW; Radeon9200-17"LCD -
MDD refuses to sleep or shut down...
Hi,
My mother is having a very frustrating problem with her MDD powermac. It refuses to shutdown or sleep. When I tell it to sleep, the screen goes black, and the fans stop. However, right as the fans stop, they start back up again and the computer is right back where it was. When I tell it to shut down, the computer goes through the shutdown process and restarts instead.
I've repaired the permissions, disk looks okay, reset the PRAM, unplugged all peripherals (except the monitor - third party with no hubs or computer control). I have also checked the engery saver options for auto power on on power failure.
Any ideas on what could be causing this or where to even start?
I did find a couple things that are interesting in the system logs. What do you guys think?
Jul 16 10:25:50 power-mac-g4 kernel[0]: System Sleep
Jul 16 10:25:50 power-mac-g4 kernel[0]: Sound assertion "0 != err" failed in "AppleLegacyAudio/AppleTexas2Audio/AppleTexas2Audio.cpp" at line 3648 goto Exit
Jul 16 10:25:49 power-mac-g4 mDNSResponder: Repeated transitions for interface en0 (FE80:0000:0000:0000:020A:95FF:FE67:3B46); delaying packets by 5 seconds
Jul 16 10:25:50 power-mac-g4 kernel[0]: ^PSystem Wake
Jul 16 10:25:50 power-mac-g4 configd[35]: posting notification com.apple.system.config.network_change
Jul 16 10:25:50 power-mac-g4 kernel[0]: Wake event 0800
Jul 16 10:25:50 power-mac-g4 lookupd[196]: lookupd (version 369.5) starting - Wed Jul 16 10:25:50 2008
Jul 16 10:25:50 power-mac-g4 kernel[0]: rtclock timebase_callback: late old 1000000000 / 41658765 new 1000000000 / 41658675
Jul 16 10:25:50 power-mac-g4 kernel[0]: rtclock timebase_callback: late old 1000000000 / 41658765 new 1000000000 / 41658496
Jul 16 10:25:50 power-mac-g4 kernel[0]: Sound assertion "0 != err" failed in "AppleLegacyAudio/AppleTexas2Audio/AppleTexas2Audio.cpp" at line 960 goto Exit
Jul 16 10:25:50 power-mac-g4 kernel[0]: ^Prtclock timebase_callback: late old 1000000000 / 41658765 new 1000000000 / 41658496
Jul 16 10:25:50 power-mac-g4 kernel[0]: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex
Jul 16 10:25:51 power-mac-g4 kernel[0]: AirPortFirmware: start Sta f/w download
Jul 16 10:25:54 power-mac-g4 launchd: Server 3757 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[196]: exited abnormally: Hangup
MDD PowerMac (Dual 1GHZ)
1.5GB RAM
OS X.4.11
Thanks for the help,
-JoshHi-
Have you tried a SAfe mode boot? Hold Shift whike starting. Safe mode takes a bit longer to boot than a regular boot, as various system checks/repairs are performed. Once in Safe mode, see if the sleep/shut down functions. If so, then it is probably a Startup item.
Another check would be trying a different user account. Setting up a new account with admin privledges is best. If sleep/shut down work in the new user account, then the problem is a Login item.
Troubleshooting Startup and Login Items.
If this fails to help ID/resolve the problem, an Archive and install would probably be enough.
Without testing for startup/login item conflict, an Archive and Install will carry over any existing problems. -
MacMini Hangs When Shutting Down
Hi all.
I've tried looking up the answers to this but I have a slightly different issue from others who had issues when shutting down.
This started a few months ago. What happens is when I click to shut down the computer, everything starts closing out. The top menu bar disappears but then nothing else happens. I'm basically looking at my wallpaper with nothing on it but my dock will still be up. When I look on my dock the only thing that appears to be active is the "Finder" folder. When I click on it nothing happens, however, if I right click it says that the application is not responding and gives me the option to relaunch, but nothing happens. So it seems like there's something going on with the "Finder" folder that is preventing it from shutting down.
For what it's worth, I did run "Verify Disk" from Disk Utilities that said everything came back okay. I unplugged any external devices hooked up via USB like my USB hub to see if there was something going on there.
I have a 2012 Mac Mini.
In the past, I have let it go all night to see if it would eventually shut down and it won't. I have to force shut it down. Ideally, I don't want to do this. Has anyone else had this issue?
Thanks!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.
Step 1
For this step, 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.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
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.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful. -
My computer is not shutting down properly
So i bought my Macbook Pro with Retina display less than a year ago, in late 2013. it had Mac OS X. Back then, i downloaded a few dodgy softwares to try and run Windows 7 as a virtual machine. I don't remember what i downloaded, but i remember i used VMWare and one other before it i installed. Anyway, ever since back then, when ever i shut down my computer, the Finder would close and icons on the desktop would dissappear, but the dock and desktop background would remain, and not shut down. So i used to hold the power button, and then press shutdown and it would shutdown.
Now that i have upgraded to Yosemite OS, when i shutdown the computer, after the Finder goes, and the dock remains, i hold the power button and it shuts down instantly. When i turn the Macbook back on, it gives me a message that i shutdown unexpectedly and asks whether i want to re-open the applications.
There is something holding back this machine from shutting down. i tried deleting the cache, deleting the logs of VM Ware, but i still get this problem....
Can anyone help me?Sorry for the late reply, as I have been busy and avoiding this headache.
In regards to step 1, i hope this helps although i cannot quite see where the problem starts, i hope you can understand this:
05/04/15 22:44:56.850 com.apple.kextcache[425]: IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
05/04/15 22:44:57.035 com.apple.kextcache[425]: kext file:///System/Library/Extensions/DigiDal.kext/ is in hash exception list, allowing to load
05/04/15 22:44:58.000 kernel[0]: Google Chrome He (map: 0xffffff80193840f0) triggered DYLD shared region unnest for map: 0xffffff80193840f0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:45:18.564 com.apple.kextcache[425]: Created prelinked kernel copy "/System/Library/PrelinkedKernels/prelinkedkernel"
05/04/15 22:45:18.564 com.apple.kextcache[425]: Created prelinked kernel "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache"
05/04/15 22:45:18.565 com.apple.kextcache[425]: Created prelinked kernel using "/System/Library/Kernels/kernel"
05/04/15 22:45:23.874 com.apple.kextcache[580]: /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache not cached.
05/04/15 22:45:23.000 kernel[0]: hfs: mounted Recovery HD on device disk0s3
05/04/15 22:45:23.977 mds[32]: (Volume.Normal:2464) volume:0x7fee83053800 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Recovery HD
05/04/15 22:45:24.022 fseventsd[20]: Logging disabled completely for device:1: /Volumes/Recovery HD
05/04/15 22:45:25.245 com.apple.kextcache[580]: Successfully updated disk0s3.
05/04/15 22:45:25.000 kernel[0]: hfs: unmount initiated on Recovery HD on device disk0s3
05/04/15 22:46:38.000 kernel[0]: Google Chrome He (map: 0xffffff801eafc0f0) triggered DYLD shared region unnest for map: 0xffffff801eafc0f0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:46:39.000 kernel[0]: Google Chrome He (map: 0xffffff80193840f0) triggered DYLD shared region unnest for map: 0xffffff80193840f0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:46:40.725 Google Chrome Helper[593]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:46:40.725 Google Chrome Helper[593]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:47:06.000 kernel[0]: Google Chrome He (map: 0xffffff80193842d0) triggered DYLD shared region unnest for map: 0xffffff80193842d0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:47:25.093 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
05/04/15 22:47:25.692 pkd[266]: enabling pid=249 for plug-in com.getdropbox.dropbox.garcon(1.8) 2CE04086-766C-4662-8D60-AB7B9000A825 /Applications/Dropbox.app/Contents/PlugIns/garcon.appex
05/04/15 22:47:25.692 Google Chrome[249]: assertion failed: 14C1514: libxpc.dylib + 97940 [876216DC-D5D3-381E-8AF9-49AE464E5107]: 0x89
05/04/15 22:47:25.711 taskgated[72]: no application identifier provided, can't use provisioning profiles [pid=600]
05/04/15 22:47:25.812 garcon[600]: Failed to connect (colorGridView) outlet from (NSApplication) to (NSColorPickerGridView): missing setter or instance variable
05/04/15 22:47:25.812 garcon[600]: Failed to connect (view) outlet from (NSApplication) to (NSColorPickerGridView): missing setter or instance variable
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny mach-lookup com.apple.ocspd
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny mach-lookup com.apple.ocspd
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny mach-lookup com.apple.ocspd
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny mach-lookup com.apple.ocspd
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny mach-lookup com.apple.ocspd
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny mach-lookup com.apple.ocspd
05/04/15 22:47:25.000 kernel[0]: Sandbox: appleeventsd(24) deny mach-lookup com.apple.ocspd
05/04/15 22:47:25.843 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.868 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.890 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.915 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.936 com.apple.xpc.launchd[1]: (com.apple.quicklook[601]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
05/04/15 22:47:25.941 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.962 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:25.983 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:26.003 sandboxd[210]: ([24]) appleeventsd(24) deny file-read-metadata /Library
05/04/15 22:47:26.430 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
05/04/15 22:47:26.000 kernel[0]: Sandbox: QuickLookSatelli(602) deny file-issue-extension /Users/mohamediskandarani/Library/Caches/com.apple.quicklook.satellite
05/04/15 22:47:26.000 kernel[0]: Sandbox: QuickLookSatelli(602) deny mach-lookup com.apple.nsurlstorage-cache
05/04/15 22:47:26.460 QuickLookSatellite[602]: Failed to obtain sandbox extension for path=/Users/mohamediskandarani/Library/Caches/com.apple.quicklook.satellite. Errno:1
05/04/15 22:47:26.000 kernel[0]: Sandbox: QuickLookSatelli(602) deny file-issue-extension /Users/mohamediskandarani/Library/Caches/com.apple.quicklook.satellite
05/04/15 22:47:26.000 kernel[0]: Sandbox: QuickLookSatelli(602) deny mach-lookup com.apple.nsurlstorage-cache
05/04/15 22:47:26.462 QuickLookSatellite[602]: Failed to obtain sandbox extension for path=/Users/mohamediskandarani/Library/Caches/com.apple.quicklook.satellite. Errno:1
05/04/15 22:47:26.569 garcon[600]: Initialized badges.
05/04/15 22:47:26.570 garcon[600]: Connecting to Dropbox on 'com.getdropbox.dropbox.garcon.cafe_501'
05/04/15 22:47:26.571 garcon[600]: Connected to Dropbox on 'com.getdropbox.dropbox.garcon.cafe_501'.
05/04/15 22:47:26.574 garcon[600]: Invalidating watch set.
05/04/15 22:47:26.574 QuickLookSatellite[602]: CGSConnectionByID: 0 is not a valid connection ID.
05/04/15 22:47:26.574 QuickLookSatellite[602]: Invalid Connection ID 0
05/04/15 22:47:26.581 garcon[600]: Watch set is now: {(
file:///Users/mohamediskandarani/Dropbox/
05/04/15 22:47:51.000 kernel[0]: Google Chrome He (map: 0xffffff801eafce10) triggered DYLD shared region unnest for map: 0xffffff801eafce10, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:47:51.000 kernel[0]: Google Chrome He (map: 0xffffff8014ce6870) triggered DYLD shared region unnest for map: 0xffffff8014ce6870, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:47:52.000 kernel[0]: Google Chrome He (map: 0xffffff8014ce6870) triggered DYLD shared region unnest for map: 0xffffff8014ce6870, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:47:56.000 kernel[0]: Google Chrome He (map: 0xffffff80193842d0) triggered DYLD shared region unnest for map: 0xffffff80193842d0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:49:59.694 CoreServicesUIAgent[242]: Error -60005 creating authorization
05/04/15 22:50:02.056 WindowServer[135]: WSGetSurfaceInWindow : Invalid surface 414910419 for window 217
05/04/15 22:50:04.721 CoreServicesUIAgent[242]: Error -60005 creating authorization
05/04/15 22:50:41.513 WindowServer[135]: WSGetSurfaceInWindow : Invalid surface 301165528 for window 221
05/04/15 22:50:57.000 kernel[0]: Google Chrome He (map: 0xffffff8018e232d0) triggered DYLD shared region unnest for map: 0xffffff8018e232d0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:50:57.000 kernel[0]: Google Chrome He (map: 0xffffff8014ce6870) triggered DYLD shared region unnest for map: 0xffffff8014ce6870, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:05.595 Google Chrome Helper[624]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:51:05.595 Google Chrome Helper[624]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:51:14.000 kernel[0]: Google Chrome He (map: 0xffffff80193842d0) triggered DYLD shared region unnest for map: 0xffffff80193842d0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:15.000 kernel[0]: Google Chrome He (map: 0xffffff801eafce10) triggered DYLD shared region unnest for map: 0xffffff801eafce10, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:16.000 kernel[0]: Google Chrome He (map: 0xffffff801eafce10) triggered DYLD shared region unnest for map: 0xffffff801eafce10, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:22.000 kernel[0]: Google Chrome He (map: 0xffffff8018e232d0) triggered DYLD shared region unnest for map: 0xffffff8018e232d0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:23.090 Google Chrome Helper[628]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:51:23.090 Google Chrome Helper[628]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:51:28.000 kernel[0]: Google Chrome He (map: 0xffffff80193842d0) triggered DYLD shared region unnest for map: 0xffffff80193842d0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:33.000 kernel[0]: Google Chrome He (map: 0xffffff8014ce6870) triggered DYLD shared region unnest for map: 0xffffff8014ce6870, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:35.096 Google Chrome Helper[629]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:51:35.096 Google Chrome Helper[629]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 22:51:36.640 Google Chrome Helper[630]: CGAffineTransformInvert: singular matrix.
05/04/15 22:51:37.000 kernel[0]: Google Chrome He (map: 0xffffff801eafce10) triggered DYLD shared region unnest for map: 0xffffff801eafce10, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:45.000 kernel[0]: Google Chrome He (map: 0xffffff8018e232d0) triggered DYLD shared region unnest for map: 0xffffff8018e232d0, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:51:46.000 kernel[0]: Google Chrome He (map: 0xffffff8018e23a50) triggered DYLD shared region unnest for map: 0xffffff8018e23a50, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:52:39.731 CoreServicesUIAgent[242]: Error -60005 creating authorization
05/04/15 22:56:10.419 CoreServicesUIAgent[242]: Error -60005 creating authorization
05/04/15 22:56:50.599 Dock[257]: void CGSShmemReleaseMappedMemory(CGSShmemID): failed to find shmem ID 998.
05/04/15 22:58:01.125 ntpd[166]: time set +1.476498 s
05/04/15 22:58:01.290 com.apple.iCloudHelper[644]: objc[644]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.
05/04/15 22:58:01.298 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
05/04/15 22:58:01.743 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]
05/04/15 22:58:01.768 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]
05/04/15 22:58:04.788 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]
05/04/15 22:58:04.832 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]
05/04/15 22:58:05.209 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=CoreDAVHTTPStatusErrorDomain Code=401 "The operation couldn’t be completed. (CoreDAVHTTPStatusErrorDomain error 401.)" UserInfo=0x7fc9d0d2b600 {AccountName=Facebook, CalDAVErrFromRefresh=YES, CoreDAVHTTPHeaders=<CFBasicHash 0x7fc9d320d170 [0x7fff7cf8acf0]>{type = immutable dict, count = 9,
entries =>
0 : x-fb-rev = 1674690
1 : Content-Type = <CFString 0x7fc9d321ecf0 [0x7fff7cf8acf0]>{contents = "text/plain; ; charset="utf-8""}
2 : Pragma = no-cache
6 : Date = <CFString 0x7fc9d32130e0 [0x7fff7cf8acf0]>{contents = "Sun, 05 Apr 2015 21:58:01 GMT"}
8 : x-fb-debug = <CFString 0x7fc9d3229bf0 [0x7fff7cf8acf0]>{contents = "it93Aq7h0n+xv47ebGynbAezlcsVVpwP2Vij6+qUAKq0FN726PpZ4hX3OPf3DkedSIf8fDhQRcYpXF IeYMVttA=="}
9 : Www-Authenticate = <CFString 0x7fc9d31ed220 [0x7fff7cf8acf0]>{contents = "OAuth realm="Facebook WebDAV", Basic realm="Facebook WebDAV""}
10 : Content-Length = 40
11 : Expires = <CFString 0x7fc9d321ed70 [0x7fff7cf8acf0]>{contents = "Sat, 01 Jan 2000 00:00:00 GMT"}
12 : Cache-Control = <CFString 0x7fc9d3220a50 [0x7fff7cf8acf0]>{contents = "private, no-cache, no-store, must-revalidate"}
05/04/15 22:58:05.215 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.queue] [Adding [<CalDAVAccountRefreshQueueableOperation: 0x7fc9d0d71810; Sequence: 0>] to failed operations.]
05/04/15 22:58:07.952 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=CoreDAVHTTPStatusErrorDomain Code=401 "The operation couldn’t be completed. (CoreDAVHTTPStatusErrorDomain error 401.)" UserInfo=0x7fc9d30369e0 {AccountName=Facebook, CalDAVErrFromRefresh=YES, CoreDAVHTTPHeaders=<CFBasicHash 0x7fc9d0fcd020 [0x7fff7cf8acf0]>{type = immutable dict, count = 9,
entries =>
0 : x-fb-rev = 1674690
1 : Content-Type = <CFString 0x7fc9d315d4c0 [0x7fff7cf8acf0]>{contents = "text/plain; ; charset="utf-8""}
2 : Pragma = no-cache
6 : Date = <CFString 0x7fc9d31bd910 [0x7fff7cf8acf0]>{contents = "Sun, 05 Apr 2015 21:58:05 GMT"}
8 : x-fb-debug = <CFString 0x7fc9d0eba500 [0x7fff7cf8acf0]>{contents = "kItSFrISck4e/Wgra1HW1ubew1wiK+hcfnHrM+BFR3awaC94aBiQviE8DPXmRfMehLbO3zzfHQ5Rge c2q2yGUg=="}
9 : Www-Authenticate = <CFString 0x7fc9d321a810 [0x7fff7cf8acf0]>{contents = "OAuth realm="Facebook WebDAV", Basic realm="Facebook WebDAV""}
10 : Content-Length = 40
11 : Expires = <CFString 0x7fc9d319e6b0 [0x7fff7cf8acf0]>{contents = "Sat, 01 Jan 2000 00:00:00 GMT"}
12 : Cache-Control = <CFString 0x7fc9d31c96b0 [0x7fff7cf8acf0]>{contents = "private, no-cache, no-store, must-revalidate"}
05/04/15 22:58:07.955 CalendarAgent[219]: [com.apple.calendar.store.log.caldav.queue] [Adding [<CalDAVAccountRefreshQueueableOperation: 0x7fc9d31cc340; Sequence: 0>] to failed operations.]
05/04/15 22:59:01.000 kernel[0]: Google Chrome He (map: 0xffffff8014ce6870) triggered DYLD shared region unnest for map: 0xffffff8014ce6870, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:59:02.000 kernel[0]: Google Chrome He (map: 0xffffff801eafcb40) triggered DYLD shared region unnest for map: 0xffffff801eafcb40, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:59:05.000 kernel[0]: Google Chrome He (map: 0xffffff80164d7780) triggered DYLD shared region unnest for map: 0xffffff80164d7780, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 22:59:07.444 Google Chrome Helper[647]: CGAffineTransformInvert: singular matrix.
05/04/15 22:59:07.444 Google Chrome Helper[647]: CGAffineTransformInvert: singular matrix.
05/04/15 23:02:22.000 kernel[0]: Google Chrome He (map: 0xffffff801eafcb40) triggered DYLD shared region unnest for map: 0xffffff801eafcb40, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 23:02:23.000 kernel[0]: Google Chrome He (map: 0xffffff8014ce6870) triggered DYLD shared region unnest for map: 0xffffff8014ce6870, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 23:02:25.401 Google Chrome Helper[649]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:02:25.401 Google Chrome Helper[649]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:02:56.000 kernel[0]: Google Chrome He (map: 0xffffff801eafcb40) triggered DYLD shared region unnest for map: 0xffffff801eafcb40, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 23:02:58.177 Google Chrome Helper[650]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:02:58.177 Google Chrome Helper[650]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:03:03.523 com.apple.xpc.launchd[1]: (com.apple.PubSub.Agent[651]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.ipc
05/04/15 23:03:03.523 com.apple.xpc.launchd[1]: (com.apple.PubSub.Agent[651]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.notification
05/04/15 23:03:11.000 kernel[0]: Google Chrome He (map: 0xffffff801eafce10) triggered DYLD shared region unnest for map: 0xffffff801eafce10, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 23:03:13.091 Google Chrome Helper[652]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:03:13.091 Google Chrome Helper[652]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:04:13.000 kernel[0]: Google Chrome He (map: 0xffffff80164d7780) triggered DYLD shared region unnest for map: 0xffffff80164d7780, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 23:04:14.000 kernel[0]: Google Chrome He (map: 0xffffff8018e23a50) triggered DYLD shared region unnest for map: 0xffffff8018e23a50, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
05/04/15 23:04:18.396 Google Chrome Helper[656]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:04:18.396 Google Chrome Helper[656]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:04:31.495 Google Chrome Helper[656]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:04:31.495 Google Chrome Helper[656]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
05/04/15 23:07:54.320 ntpd[166]: FREQ state ignoring -0.029622 s
05/04/15 23:07:55.263 mds[32]: (LSOF.Error:239) File '/Volumes/PMBPORTABLE' (fd=22) left open on device 16777226
05/04/15 23:07:58.409 mds[32]: (LSOF.Error:239) File '/Volumes/Untitled' (fd=13) left open on device 16777224
05/04/15 23:09:10.673 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
05/04/15 23:09:10.833 com.apple.iCloudHelper[670]: objc[670]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.
05/04/15 23:09:10.843 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
05/04/15 23:13:39.188 CoreServicesUIAgent[242]: unexpected message <OS_xpc_error: <error: 0x7fff7ca89c60> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff7ca89f70> { length = 18, contents = "Connection invalid" }
}>
05/04/15 23:13:48.941 WindowServer[135]: WSGetSurfaceInWindow : Invalid surface 512951363 for window 228
05/04/15 23:13:56.539 warmd[31]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
05/04/15 23:13:56.934 loginwindow[66]: ERROR | __34-[SessionLogoutManager quitFinder]_block_invoke | Finder is killable, calling SMJobRemove
05/04/15 23:13:56.935 garcon[418]: host connection <NSXPCConnection: 0x6000001121b0> connection from pid 259 invalidated
05/04/15 23:13:56.937 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.937 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.937 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.938 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.938 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.938 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.938 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.939 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.939 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.939 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.939 WindowServer[135]: CGXGetConnectionProperty: Invalid connection 62979
05/04/15 23:13:56.948 CoreServicesUIAgent[242]: unexpected message <OS_xpc_error: <error: 0x7fff7ca89c60> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff7ca89f70> { length = 18, contents = "Connection invalid" }
}>
06/04/15 14:31:41.000 bootlog[0]: BOOT_TIME 1428327101 0
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.AccountPolicyHelper" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/asl" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.authd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.awdd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.callhistory.asl.conf" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.cloudd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.clouddocs" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.commerce.asl" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.CoreDuetAdmissionControl" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.eventmonitor" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.family.asl" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.ical" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.icloud.FindMyDevice" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.install" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.iokit.power" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.mail" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.MessageTracer" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.networking.symptoms" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.networking.symptoms" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.performance" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.secinitd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 syslogd[17]: Configuration Notice:
ASL Module "com.apple.securityd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
06/04/15 14:31:44.000 kernel[0]: Longterm timer threshold: 1000 ms
06/04/15 14:31:44.000 kernel[0]: PMAP: PCID enabled
06/04/15 14:31:44.000 kernel[0]: PMAP: Supervisor Mode Execute Protection enabled
In regards to step 2, I cannot find any crash reports or shutdownstall reports or any of that, but just old reports that i am sure aren't relevant to this problem.
Sorry for those long lines of report. I look forward to hearing back from you.
Regards,
MI -
I've updated to 10.10.3 without any apparent problems but, as I shut down, there's a short flash of an indistinct screen asking if I want to complete the installation. I can't see what application is being referred to. It doesn't seem to be causing issues but I like a tidy system
1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a general summary of what you need to do, if you choose to proceed:
☞ Copy a particular line of text to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.
5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is sometimes, but not always, slow, run the test during a slowdown.
You may have started up in "safe" mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. Load this linked web page (on the website "Pastebin.") The title of the page is "Diagnostic Test." Below the title is a text box headed by three small icons. The one on the right represents a clipboard. Click that icon to select the text, then copy it to the Clipboard on your computer by pressing the key combination command-C.
If the text doesn't highlight when you click the icon, select it by triple-clicking anywhere inside the box. Don't select the whole page, just the text in the box.
8. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:
[Process started]
Part 1 of 8 done at … sec
Part 8 of 8 done at … sec
The test results are on the Clipboard.
Please close this window.
[Process completed]
The intervals between parts won't be exactly equal, but they give a rough indication of progress. The total number of parts may be different from what's shown here.
Wait for the final message "Process completed" to appear. If you don't see it within about ten minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it and go to the next step. You'll have incomplete results, but still something.
12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.
Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed. -
Since installing Yosemite, I must force computer to shut down.
Since I installed Yosemite , It will not shut down or restart normally, I must force a shut down. Than it takes forever to start up. Anyone having that problem?
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.
Step 1
For this step, 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.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
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.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful. -
How can i get my mac to shut down correctly?
This problem started a couple of days ago. I'm speaking of my iMac which is running Mac os Mavericks 10.9.4, it uses an Intel Core 2 Duo cpu as well. Recently when I shut down through the Apple button --> Shut down it simply goes to the white screen with the spinning gear at the bottom and it keeps spinning and does not shut down. The only way I can get my computer to shut down now is to force a shut down with the power button during an attempted shut down or just forcing it to shut down before trying to correctly shut it down through the Apple button --> Shut down. Please help, I've tried resetting the SMC as I've seen in other posts about this topic and any of the other issues that fixed it aren't my issue, I've checked. I'd appreciate any help given to try to fix my computer. Thank you in advance.
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. Click Utilities, then Console in the icon grid.
Step 1
For this step, 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.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Note the timestamps of the BOOT_TIME log messages, which refer to the times when the system was started. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
☞ When posting a log extract, be selective. A few dozen lines are almost always more than enough.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
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.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent of each. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
☞ If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
☞ Please don’t post other kinds of diagnostic report—they're very long and rarely helpful. -
How do I determine why yosemite will no longer shut down?
This is a new problem, not occurring after installing Yosemite. Now my iMac will not shutdown it just has that spinning icon that will go on forever unless I hold down the power button. How do I determine what is causing it?
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.
Step 1
For this step, 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.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
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.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.
Maybe you are looking for
-
Hello, All of the sudden my Safari is very slow, and pages take almost one entire minute to load. Is there anyway I can speed this up or clean up my system?
-
How can I make CONTAINS query work for a date range
In either 9i or 10g (eventual). I have a CONTEXT index that contains multiple columns from multiple tables and using a USER_DATASTORE. E.g., I have names that come from 3 different table locations and dates that come from 4. I can index them fine but
-
Error installing dreamweaver in d disk
When I try to install spanish dreamweaver in d disk, the system says that the cabinet file is damaged, the problem doesn´t occurs en c disk, I need change the drive but with this problem I cant do it
-
How to include an APD process in BW Process Chain
HI, I have an existing process chain that I want to add an APD process to. There are dependencies. For example, I want the last 2 steps in the existing process chain to continue AFTER the APD process runs successfully. So, how would I include an APD
-
Import, Export Data functions hidden
In previous version of Adobe Acrobat, you could import and export data quite easily from a Forms collapsible pane. Now it appears this functionality is hidden. I was only able to find it by searching in tools. But additionally, the section it is unde