SD not sleeping computer

[badlydrawnboy]

I have a nightly back-up schedule where I have SD set to sleep the computer after it is finished. Normally it works just fine. However, the last couple of mornings I've woken up to find my computer on.

Here are the last entries from SD's log:


| 10:45:42 PM | Info | ......COMMAND => Sleeping computer
| 10:45:42 PM | Info | Copy complete.


And here is the final entry last night from console:


4/12/08 10:45:42 PM com.apple.launchd[1] (0x10d020.nohup[1883]) Could not setup Mach task special port 9: (os/kern) no access

And here is the first entry this morning from Console (there are about six of these right in a row):


4/13/08 6:55:42 AM SuperDuper![2416] .scriptSuite warning for attribute 'boundsAsQDRect' of class 'NSWindow' in suite 'NSCoreSuite': 'NSData<QDRect>' is not a valid type name.

Any ideas Dave?

[dnanian]

The warnings are entirely normal and expected, but have you tried restarting your Mac?

[badlydrawnboy]

I just ran the maintenance scripts and repaired permissions. We'll see if it happens again tonight.

So there's no indication on why the computer woke up from sleep on its own?

[dnanian]

No... not in the log. Might not have gone to sleep at all.

[badlydrawnboy]

No... not in the log. Might not have gone to sleep at all.

What could cause that to happen? SD has been putting the computer to sleep after backups every night.

[dnanian]

Something in the OS that was messed up, which is why I suggested restarting.

[rmf]

I had this issue. I did a deep cache clean using leopard cache cleaner and all was good after.

[badlydrawnboy]

Okay, I'm having this issue again - and more frequently this time. Here's what the Console has to say:

4/28/08 10:30:00 PM com.apple.launchd[1] (0x10d500.cron[3495]) Could not setup Mach task special port 9: (os/kern) no access

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextScaleCTM: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextGetCTM: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextSaveGState: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextConcatCTM: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextSaveGState: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextTranslateCTM: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextRotateCTM: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextTranslateCTM: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextDrawImage: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextRestoreGState: invalid context

4/28/08 10:31:58 PM [0x0-0x1a31a3].com.blacey.SuperDuper![3486] Mon Apr 28 22:31:58 Chris-Kressers-Mac-Pro.local SuperDuper![3486] <Error>: CGContextRestoreGState: invalid context

4/28/08 10:45:00 PM com.apple.launchd[1] (0x10d300.cron[3598]) Could not setup Mach task special port 9: (os/kern) no access

Note that 10:30 is the time that I have SD set to automatically backup.

Does this tell you anything, Dave?

[dnanian]

The 'context' issues are rather expected in some configurations, and not a problem. Nothing in there has much to do with sleeping, no...