Why is Sleep & Shutdown so slow!

[tripmusic]

30 seconds is not normal. I seem to remember that is close to how long a process can stop the sleep process from running until the OS force terminates it.

I had a similar issue, but can't remember the exact terminal command to run to find the problem (it was years ago)

You could try pmset -g

If sleep has a value of 0 it should also say what interrupted it (it gives a process id)

You could also do pmset -g log then do a search for sleep which may provide some information

pmset -g assertions could also provide some useful information

I'll see if I can find out the command I ran before

You could also try a different user account to see if they have the problem

Ok thanks, that actually helped to find out the possible culprit. Sleep showed 30 and said there was a "user eventagent" as the culprit. Where are they located? I get different results from each use of the command

 

[Rev0l2ti0n]

I had the same issue on a Clean Install of the Public Beta. I've since done a clean install (and update) of the Developer Preview and it's significantly better in almost every regard, less graphical glitches, less lag, etc.

 

[GGERARD]

I've modified ( yesterday ) my prefer. System.like this


Now, all seam to be correct...... wait and see!
waking looks to be okay at each time.
GGERARD

 

[crjackson2134]

I've had issues like this in the past. It almost always involves something using network connections. iCloud Sync. has done this to me before.

 

[dyn]

But how much memory contents need to be written to disk if you never even logged into your account and obviously no apps or launch agents could open. I have booted-up the computer waited and then press sleep or shutdown directly from the login screen.

The /var/vm/sleepimage is usually the same size as the amount of physical mem in the machine. All the contents in memory will be written to disk.

It seems strange to suddenly change so significantly in 1 version of OSX whilst the rest of the operating system performs without delay.

Always take a look at the logs first as they usually reveal what's going on. Sometimes apps get stuck (due to being incompatible with the OS X version or because of a bug in the app) and prevent the machine to enter the sleep/hibernate state. This will be reflected in the log as you've already found out. Other things that are notorious for preventing sleep/hibernate: usb devices and network (doesn't matter if it is OS X, Windows or Linux).

 

[RandomKamikaze]

Ok thanks, that actually helped to find out the possible culprit. Sleep showed 30 and said there was a "user eventagent" as the culprit. Where are they located? I get different results from each use of the command

View attachment 577501

software_notify_agent is self explanatory. Do you have any software or updates waiting to be installed from MAS?

apsd is the Apple Push Notification Service

AddressBookSyncSource is also self explanatory.

UserEventAgent and powerd alone aren't going to provide that much information on their own.

You could also run pmset -g pslog to get real time logging. When you have run the command sleep the computer, then wake it again and review the information.

You'll also need to cross-reference what's going on in Console.

Did you try a different user account? If not, create a new user account and completely logout of yours. Sign in to the new user account and try and sleep again. Does it still take 30 seconds?

 

[tripmusic]

software_notify_agent is self explanatory. Do you have any software or updates waiting to be installed from MAS?

apsd is the Apple Push Notification Service

AddressBookSyncSource is also self explanatory.

UserEventAgent and powerd alone aren't going to provide that much information on their own.

You could also run pmset -g pslog to get real time logging. When you have run the command sleep the computer, then wake it again and review the information.

You'll also need to cross-reference what's going on in Console.

Did you try a different user account? If not, create a new user account and completely logout of yours. Sign in to the new user account and try and sleep again. Does it still take 30 seconds?

Tried a different user account with the same result. Now it's actually saying 62 for sleep. I just recently installed the latest beta. Can I post the console log for you to take a look at? I have no clue about this stuff

 

[RandomKamikaze]

Robbed from another thread on the forum:

hey guys,

I Just signed up to post the reply.
I found the solution for this, you have to search for the logs and see what is taking too much time. Use the following command :

pmset -g log

In my case it was an old print job which I had sent my mistake to an offline printer and forgot to delete it from the queue.
I went to "print and fax" in system preferences and found the printer, checked the queue and deleted the job.
Now my lovey MBP sleeps in 2 seconds like an infant.

If still no luck then yeah, post log file

 

[tripmusic]

Robbed from another thread on the forum:



If still no luck then yeah, post log file