Mac Pro sleeps after being woken up by WOL

The Mac Pro was just bought, it should be the latest version of Mid 2012. Is it a Dark Wake model?

From the email alert I knew RCR posted a comment to this thread, but it is interesting that I cannot see the comment from here. Anything wrong?

Do you mean the re-sleep issue of Mac or the post hiding problems of Jive?

Linc Davis wrote:

I don't know where this is documented, if at all, but I don't think the behavior is abnormal.

Thanks a lot for the information.

R C-R wrote:

... What is wrong is ASC runs on site hosting software called "Jive" (not made by Apple) that is currently having a lot of problems, among them displaying some replies until long after they have been posted.

The workaround is either to wait a while & check the topic again, or post a new reply to any recent message in the topic, which usually gets the missing ones to show up immediately ...

The behavior is normal when clicking the mouse or pressing the key to wake the Mac, the issue only occurs when trying to wake via WOL. Never thought the same wake process could have different results.

Linc Davis wrote:

I mean the sleep issue.

I checked that Bonjour Sleep Proxy article before. It seems not applicable here as I don't have any this kind of proxy such as Airport Extreme products on my network.

As shown below, I checked "All Messages" and typed "RTC" in the search field and no any log returned. However, I am sure I did often press the keyboard to wake the Mac and did several waking up tests via WOL, so it should be some logs recorded against this.

R C-R wrote:

I'm not sure but I think by "dark wake" Linc means what Apple describes in "Bonjour Sleep Proxy." As the link mentions, that briefly wakes your Mac if you have an Apple Airport device or an Apple TV on your network & have Wake on Demand enabled on the Mac.

When Wake on Demand is enabled, while the Mac is asleep about every two hours its Real Time Clock (RTC) will wake it briefly so that it can check in with the Bonjour Sleep Proxy. This is separate from network requests to wake the Mac, like for iTunes sharing or whatever.

Try this: open Console (in Applications > Utilities) to the "All Messages" section. In the filter box at the top right enter (without quotes) "RTC" & look for messages that say "Wake reason: RTC (Alarm)." Any messages like that indicate the Mac's clock has awakened the system, not some network event.

> Now I am able to wake up the machine from my local router or across the Internet, but just wake up for a little while only.

From my local router, I use below way to wake up the Mac Pro.

I can also wake up the Mac this way over the Internet.

For your information, I can successfully wake up other WOL enabled Windows machines this way on the same network with no problem.

As mentioned, both ways can only wake up the Mac Pro for about 30 seconds, then machine will automatically sleep again though at System Preferences I have set the computer to sleep after "3 hrs" or "never", as shown below.

What I expect is just to make the Mac Pro back to work the same way like I locally press the keyboard or click the mouse, not to automatically sleep again in seconds.

Any thought please? Thanks!

R C-R wrote:

bengmugenr wrote:

The behavior is normal when clicking the mouse or pressing the key to wake the Mac, the issue only occurs when trying to wake via WOL. Never thought the same wake process could have different results.

Please explain specifically how you are trying to WOL, what you want to accomplish by doing so, & how long you think whatever it is you want to accomplish should take.

Also, what VM's are you running & by what method do they run (like via Parallels or whatever).

Just an update - The suggestion from Apple Care Support:

Cache folders that can be emptied

~/Library/Caches

~/Library/Inputmanager

~/Library/Inputmethods

~/Library/Launchagents

/Library/Caches

/Library/Input Methods

/Library/Launchagents

/Library/Launchdaemons

/Library/Startupitems

I don't understand why the Sleep Mode is related to the above folders. I also worry about the impact of deleting these folders as I do have heaps of files under /Library/Caches, /Library/LaunchAgents, /Library/LaunchDaemons, ~/Library/Caches, ~/Library/LaunchAgents, especially the bold ones.

Any comments please? Thanks in advance.