abb668b8-e67d-45d2-8fe4-b2a87dc2831e Posted January 22, 2014 Report Share Posted January 22, 2014 All of my Retrospect jobs say Execution Completed Successfully inside of the Running queue. None of the backups are excecuting because all the jobs are stuck in the Running queue. Anyone else run into this? I'll restart the server which should free this up, but would like to know if there are any solutions to keep this from happening in the first place. Quote Link to comment Share on other sites More sharing options...
twickland Posted January 22, 2014 Report Share Posted January 22, 2014 Have you confirmed that the backup jobs are actually stalled? It may just be that the console is failing to update properly. Quote Link to comment Share on other sites More sharing options...
abb668b8-e67d-45d2-8fe4-b2a87dc2831e Posted January 22, 2014 Author Report Share Posted January 22, 2014 I've checked on my client computer running the Retrospect console and running the Retrospect console on the Retrospect server. Both reporting the same thing. Quote Link to comment Share on other sites More sharing options...
Don Lee Posted January 22, 2014 Report Share Posted January 22, 2014 Wow. I've never seen this. I have seen the engine stuck where it would not *start* pro-active backups, though. I restarted the engine to fix it. Quote Link to comment Share on other sites More sharing options...
abb668b8-e67d-45d2-8fe4-b2a87dc2831e Posted January 27, 2014 Author Report Share Posted January 27, 2014 This happened again today. Last Friday I rebooted the server in order to clear the Queue. Came in today and all the jobs are stalled in the Running queue with an Excecution completed successfully status. I did leave the Retrospect client running on my machine over the weekend? I'm wondering if this is what is causing the issue? Quote Link to comment Share on other sites More sharing options...
abb668b8-e67d-45d2-8fe4-b2a87dc2831e Posted January 27, 2014 Author Report Share Posted January 27, 2014 I just logged into the server running Retrospect server. Tried to stop the engine by going into system preferences, and clicking on stop. Nothing happened. Looked in activity monitor, and Retrospect is running 100% of one of the CPU's. Quote Link to comment Share on other sites More sharing options...
abb668b8-e67d-45d2-8fe4-b2a87dc2831e Posted January 27, 2014 Author Report Share Posted January 27, 2014 After Force Quitting the process in activity monitor, the Retrospect in Mac System Preferences showed that the engine had stopped. I started the Retrospect engine again and the Running Queue is cleared. Quote Link to comment Share on other sites More sharing options...
hgv Posted February 20, 2014 Report Share Posted February 20, 2014 I bumped into an identical problem. My guess is your email settings are the cause. Try disabling both successful and unsuccessful email notifications and see what happens. Quote Link to comment Share on other sites More sharing options...
abb668b8-e67d-45d2-8fe4-b2a87dc2831e Posted February 20, 2014 Author Report Share Posted February 20, 2014 I'll give that a shot. Although it doesn't have anything to do with my email settings. There's quite a few bugs in Retrospect... email is one of them. See this post where I successfully tested getting to my email server using the terminal and the same email settings in Retrospect. http://forums.retrospect.com/index.php?/topic/150965-unable-to-send-email-from-retrospect/ Also, once this happens I can't just stop the retrospect engine and start it. I have to reboot the server. % Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.