Apple Event: May 7th at 7 am PT

> Learn more

> Add to your calendar 

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Matt-HTX
Matt-HTX Author
User level: Level 1
0 points

Process causing machines to exit screensaver

Greetings,

I've searched high and low, and found similar issues, but not with the same cause that I found on one of our machines.

We have numerous Macs deployed, all running the OS 10.10.5.

I'm having a problem with them exiting out of their screensavers numerous times a day, for no obvious reason.

I checked a few of the using Activity Monitor, but there were no processes running on any of them, that showed as preventing sleep.

Finally waited for one to exit out of screensaver, and immediately checked the system log.

I'm pasting a the critical portion of the log, where it shows approx 8 entries prior to ending of the screensaver service, the actually end service entry, and 1 following entry.

Any help is greatly appreciated.


[System log entries start]

1/26/16 11:40:01.305 AM com.apple.xpc.launchd[1]: (com.apple.MediaLibraryService) Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

1/26/16 11:40:10.349 AM secinitd[231]: com.apple.secinitd.connection-from.6681: registration request failed: (0x13, 0xd) Incoming message euid does not match xpcd uid (203 != 0).

1/26/16 11:40:12.092 AM com.apple.xpc.launchd[1]: (com.apple.MediaLibraryService[6681]) Service exited due to signal: Illegal instruction: 4

1/26/16 11:40:12.093 AM com.apple.xpc.launchd[1]: (com.apple.MediaLibraryService) Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

1/26/16 11:40:21.139 AM secinitd[231]: com.apple.secinitd.connection-from.6682: registration request failed: (0x13, 0xd) Incoming message euid does not match xpcd uid (203 != 0).

1/26/16 11:40:21.163 AM com.apple.xpc.launchd[1]: (com.apple.ReportCrash.Root[6683]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash.DirectoryService

1/26/16 11:40:22.916 AM com.apple.xpc.launchd[1]: (com.apple.MediaLibraryService[6682]) Service exited due to signal: Illegal instruction: 4

1/26/16 11:40:22.916 AM com.apple.xpc.launchd[1]: (com.apple.MediaLibraryService) Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

1/26/16 11:40:31.095 AM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x1000002b.ScreenSaverEngine[6519]) Service exited due to signal: Terminated: 15

1/26/16 11:40:34.095 AM loginwindow[6353]: ERROR | -[Application hardKill:] | Application hardKill returned -600

[System log entries end]

Posted on Jan 26, 2016 1:38 PM

Reply
8 replies
User profile for user: Matt-HTX
Matt-HTX Author
User level: Level 1
0 points

Feb 24, 2016 4:23 PM in response to Matt-HTX

Bummer - no replies.

This is taking place on approximately 100 Macs we currently have deployed.

My main concern, is screen burn-in do to the units staying at the login screen so often, and not staying in screensaver.

To add to it, I'm using Open Directory to manage many settings, including a nightly reboot.

The machines are not rebooting at all, as scheduled.

I can't help but think the same thing that's constantly causing them to exit the screensaver, is also preventing them from their nightly scheduled reboots.

Reply
User profile for user: ihatohr
ihatohr
User level: Level 1
0 points

Mar 4, 2016 3:05 AM in response to Matt-HTX

Hey Matt-HTX,


Just came in this morning to my iMac to find it had powered itself off. Looking in system.log I found these entries:

Mar 3 21:00:32 my-imac kernel[0]: aio_queue_async_request(): too many in flight for proc: 16. ...skipped a bunch of 1password log entries Mar 3 21:05:13 my-imac com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x100001d4.ScreenSaverEngine[29875]): Service exited due to signal: Terminated: 15 Mar 3 21:05:13 my-imac loginwindow[29737]: ERROR | -[Application terminate] | Application terminate returned -600 Mar 3 21:05:16 my-imac loginwindow[29737]: ERROR | -[Application hardKill:] | Application hardKill returned -600 ...skipped another bunch of 1password log entries Mar 3 21:07:48 iohr-imac 2BUA8C4S2C.com.agilebits.onepassword4-helper[26679]: ....

It looks like it just killed the loginwindow process, and that in turn shut down my mac after about 2 mins and 30 seconds. The last line you see here is the very last entry before timestamps showing 10:36 the next day, when I powered it back on.


Wondering if some unforeseen behaviour kicks in when loginwindow is killed, that just shuts down OSX. Did you ever find anything else out about this?

Reply
User profile for user: Matt-HTX
Matt-HTX Author
User level: Level 1
0 points

Mar 8, 2016 7:44 AM in response to Matt-HTX

Update: I unchecked the "Wake for Network Access" option on a test group of machines last night (I logged into a few clients to make the setting change was successfully deployed).

Everything was looking okay this morning - at first.

Unfortunately the test group exited out of screensavers, and back to the login screens, a bit later.

If definitely is scheduled background task of some type, as the test machines all exited their screensavers at pretty much the same time.

There are a few other things I'm looking at.

One being a cloud-sync task being executed by iPhoto, or iTunes.........

I'll keep you posted on any breakthroughs.

Regards,

Matt

Reply

Process causing machines to exit screensaver

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up