Mac Pro sleeps after being woken up by WOL

Tried searching for "wake" and got some results, as shown below.

Tried searching for "wake reason" and only four lines returned.

14/10/13 7:55:14.000 PM kernel[0]: Wake reason: ARPT (Network)

14/10/13 8:04:01.000 PM kernel[0]: Wake reason: ARPT (Network)

14/10/13 11:23:58.000 PM kernel[0]: Wake reason: ARPT (Network)

14/10/13 11:24:59.000 PM kernel[0]: Wake reason: UHC6

if ARPT is for Airport, what does UHC6 mean? It seems like indicating the way of waking up by hitting the keyboard or clicking the mouse?

Yes, blow lines just match the WOL tests I did when I was talking with Apple Care Support today. But as I remember I did more than 2 times, but only 2 wake-ups were logged.

15/10/13 8:10:04.000 PM kernel[0]: Wake reason: ARPT (Network)

15/10/13 8:10:04.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

15/10/13 8:13:43.331 PM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fd4fb002130> Tue Oct 15 21:05:53 2013 EST (approx)

15/10/13 8:13:43.331 PM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd4fb002130> Tue Oct 15 21:05:53 2013 EST (approx)

15/10/13 8:14:31.000 PM kernel[0]: Wake reason: ARPT (Network)

15/10/13 8:14:31.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

15/10/13 8:15:17.954 PM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fd4fe008220> Tue Oct 15 21:05:53 2013 EST (approx)

15/10/13 8:15:17.954 PM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd4fe008220> Tue Oct 15 21:05:53 2013 EST (approx)

Thanks again.

R C-R wrote:

I assume "ARPT" means Airport. Do the times for those lines match when you have tried to wake the Mac from the network with a WOL?

As requested.

Hardware Information:

Mac Pro (Mid 2012)

Mac Pro - model: MacPro5,1

2 2.4 GHz 6-Core Intel Xeon CPUs: 12 cores

64 GB RAM

Video Information:

ATI Radeon HD 5770 - VRAM: 1024 MB

System Software:

OS X 10.8.5 (12F45) - Uptime: 0 days 2:23:41

Disk Information:

HL-DT-ST DVD-RW GH80N disk2 : (727.4 MB)

WKSSTE06CD2 (disk2s0) /Volumes/WKSSTE06CD2: 633.4 MB (Zero KB free)

APPLE SSD SM512E disk0 : (500.28 GB)

disk0s1 (disk0s1) <not mounted>: 209.7 MB

MACPRO_SSD (disk0s2) /: 499.42 GB (133.04 GB free)

Recovery HD (disk0s3) <not mounted>: 650 MB

APPLE HDD HDS723020ALA640 disk1 : (2 TB)

disk1s1 (disk1s1) <not mounted>: 209.7 MB

MACPRO_HD1 (disk1s2) /Volumes/MACPRO_HD1: 1 TB (340.23 GB free)

MACPRO_HD2 (disk1s3) /Volumes/MACPRO_HD2: 999.72 GB (296.01 GB free)

USB Information:

SMI Corporation USB DISK

Apple Inc. BRCM2046 Hub

Apple Inc. Bluetooth USB Host Controller

FireWire Information:

Thunderbolt Information:

Kernel Extensions:

com.AmbrosiaSW.AudioSupport (4.1.2)

com.vmware.kext.vmci (90.4.18)

com.vmware.kext.vsockets (90.4.23)

com.vmware.kext.vmnet (0104.03.86)

com.vmware.kext.vmx86 (0104.03.86)

com.vmware.kext.vmioplug.10.1.24 (10.1.24)

Problem System Launch Daemons:

Problem System Launch Agents:

Launch Daemons:

[loaded] com.adobe.fpsaud.plist

[loaded] com.ambrosiasw.ambrosiaaudiosupporthelper.daemon.plist

[loaded] com.bjango.istatmenusdaemon.plist

[loaded] com.microsoft.office.licensing.helper.plist

Launch Agents:

[loaded] com.bjango.istatmenusagent.plist

User Launch Agents:

[loaded] com.google.keystone.agent.plist

[loaded] com.microsoft.LaunchAgent.SyncServicesAgent.plist

User Login Items:

iTunesHelper

SpeechSynthesisServer

3rd Party Preference Panes:

Flash Player

Internet Plug-ins:

Flash Player.plugin

FlashPlayer-10.6.plugin

JavaAppletPlugin.plugin

QuickTime Plugin.plugin

SharePointBrowserPlugin.plugin

User Internet Plug-ins:

Bad Fonts:

None

Top Processes by CPU:

273% vmware-vmx

8% firefox

1% WindowServer

1% com.apple.quicklook.satellite

1% EtreCheck

1% fontd

1% Finder

1% VMware Fusion

0% SystemUIServer

0% hidd

Top Processes by Memory:

31.55 GB vmware-vmx

590 MB
firefox

197 MB
Google Chrome

131 MB
mds

131 MB
VMware Fusion

131 MB
SystemUIServer

131 MB
WindowServer

66 MB Console

66 MB SpeechSynthesisServer

66 MB Finder

Virtual Memory Statistics

25.92 GB Free RAM

2.45 GB
Active RAM

17.94 GB Inactive RAM

17.66 GB Wired RAM

32.46 GB Page-ins

0 B Page-outs

But for those events woken by UHC device, the they are followed by the same message saying "powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake". I have confirmed that if the Mac is woken up by keyboard or mouse, it can stay awake for never or the period of time specified in Energy Saver even if I don't touch the keyboard or mouse again.

However, as you mentioned, I too believe the short awake period means it is a dark wake.

R C-R wrote:

...

And from the "powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake" part, ... which is probably why it doesn't stay awake any longer than it takes to check for any pending maintenance tasks or light the screen (thus the "dark wake" part).

I also tried first waking up the Mac via WOL and keeping using the computer by typing something, then the Mac would keep awake until reached the time limit given in Energy Saver. Hence I think your logic is right. But the follow-up issue is for my scenario the remote access after WOL is not something compatible with Bonjour Sleep Proxy, it is RDP to Windows VMs running on the Mac.

Please understand that all this is just a guess on my part. I suspect the logic is since nobody is actually at the keyboard waking the Mac there is no good reason to wake the monitor display or keep the Mac awake if there is nothing for it to do, so unless the WOL "magic packet" is followed by some request for the Mac to do something, it goes back to sleep.

I tried, as just mentioned, PINGing or RDPing to the VMs does not help, the Mac just slept again after a while.

Is there a way to implement a Full Wake on the Mac via WOL?

Have you tried just accessing it from another local device, without doing anything to specifically issue a WOL packet? ... That's all it takes to wake the other Mac.

Thanks heaps, again.

FYI

On the same network using the same methods (local router and external site) my iMac can be successfully woken up and stay awake as expected. The iMac is running Snow Leopard 10.6.8 Build 10K549.

The corresponding log items indicate System Wake only, no Dark Wake. There is no Dark Wake on Snow Leopard?

I believe you are right.

But beside the approaches to make other protocols or products compatible with the Mac way of WOL, can we find out a method to simply let the Mac to always do Full Wake instead of Dark Wake?

I think, after working through the effort, the issue can be summarized to: WOL only wakes the Mac in Dark Wake mode, and a tweak to Full Wake is required.

Am I correct?

R C-R wrote:

bengmugenr wrote:

I tried, as just mentioned, PINGing or RDPing to the VMs does not help, the Mac just slept again after a while.

Is there a way to implement a Full Wake on the Mac via WOL?

I think a ping isn't something that would keep the Mac awake unless you did it periodically, often enough to keep the Mac awake. I have no idea what RDP would do since that is a proprietary protocol of Microsoft that requires client software installed on other platforms & you are (I assume) running Windows as a VM on OS X through VMware Fusion. (You might want to contact VMWare's customer support to see if Fusion supports RDP on virtualized Windows machines, but I doubt that it is since the 'parent' OS is still OS X.)

So, assuming I am getting this right, you need to either find & install the client software that implements RDP on OS X (which probably will involve a kernel extension or launch daemon), or boot directly into Windows (like through Boot Camp) instead of running a virtualized version if you want to keep the Mac Pro awake to access any Windows side stuff.

Any Full Wake related settings in System Preferences or somewhere in a plist under the Libary?

Thanks again.

R C-R wrote:

... I think the "tweak" you are looking for is some OS X add on client software that implements the protocol for OS X ...

Thanks so much for the trick.

When I tried to modify com.apple.Boot.plist using TextEdit, I got the following error. In the profile of current user, "allow user to administer this computer" is checked.

How to edit the plist file as an real administrator?

Dabluest wrote:

Addendum: I also read darkwake=8 may be more suitable if 0 interferes with sleep.