#1
|
|||
|
|||
SD & Growl notification issue
Hi
Got a strange event happening, I have growl set up to send an email to me only if a scheduled copy fails, nothing else. I am getting an email stating the below, yet when I log into my server, I am not presented with SD showing the red failed area, in fact SD has quit as it should, I have checked the log and that says Copy complete, this is quite odd behavior, does any one have any suggestions as to why this may be happening? “Copy of Macintosh to BATCAVE (Backup) failed. SuperDuper! got an error: Connection is invalid.” |
#2
|
||||
|
||||
Hm. Have you tried deleting and recreating the schedule?
__________________
--Dave Nanian |
#3
|
|||
|
|||
hey Dave
no, I will delete and recreate the next one which is scheduled to fire at 3pm today and see if that does it, plus ill delete and recreate the schedule with the issue, ill have to wait for it to fire tomorrow. |
#4
|
|||
|
|||
ok, I deleted all of the scheduled backup's, and the problem is still happening
error: "Connection is invalid.”, yet the copy is completed with no issues. My before copy always repairs permissions. I have checked all the logs and they are fine. The server has been rebooted, have run Disk Warrior, and done a fsck -fy very strange, is any body else seeing this issue? |
#5
|
||||
|
||||
"Connection is invalid" should have gone away in 2.7.5; I haven't heard of people having it recently. That's what you're using? Basically, it means that SuperDuper! quit before the schedule did, which shouldn't happen.
__________________
--Dave Nanian |
#6
|
|||
|
|||
using 2.7.5 (v95) OSX 10.10.3, OSX Server 4.1
|
#7
|
||||
|
||||
I don't know why you're be getting that. I'm not seeing it at all...
__________________
--Dave Nanian |
#8
|
|||
|
|||
ok, well i’m not sure where to go from here, I guess my work around for now is to not have SD quit after the scheduled copy is completed, and have a on idle apple script running in the back ground that will quit SD only when it’s process becomes idle.
|
#9
|
||||
|
||||
A scheduled copy automatically quits if SD! wasn't already running. There's no need to set a "Quit" in Options.
__________________
--Dave Nanian |
#10
|
|||
|
|||
interesting, that my 11am scheduled backup has not done it, so this is random
|
#11
|
||||
|
||||
Random and extremely uncommon...
__________________
--Dave Nanian |
#12
|
|||
|
|||
my mum always said I was special, ill keep monitoring it
|
#13
|
|||
|
|||
1pm backup sweet...
|
#14
|
|||
|
|||
ok, all backup's have gone ok since yesterday, until now, just had the same error thrown, this time I was watching the end of the backup, SD finished and quit, then the growl notification came up with the error: Connection is invalid, is there no way to stop this happening?
|
#15
|
||||
|
||||
Do you have a lot of scheduled backups, and have all of them been deleted and recreated?
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Any plans to support Notification Center? | stevenjklein | General | 1 | 01-06-2013 08:31 PM |
Another sneak peek: Backup Notification with Growl! | dnanian | General | 47 | 01-24-2008 08:39 AM |
Growl Issue: process "SuperDuper!" doesn't understand the exists message | Mr. CoBalt | General | 5 | 01-16-2007 12:26 PM |
Growl Notifications not sticking. | raptor256 | General | 4 | 12-07-2006 09:14 PM |
Growl send notification-network | Budgie | General | 6 | 06-14-2006 06:44 PM |