[Taskforest-discuss] Fwd: failure after rerun in taskforestd
Brought to you by:
enoor
From: Aijaz A. <en...@us...> - 2009-05-25 23:35:27
|
Yes, that would do it. When you request a job be rerun and then delete the job from the Family before the job can be rerun, the status command (which is what the website is invoking) tries to access the missing record and that causes the error that you see. The system should handle this condition more gracefully. I'll fix this in the next release. The next version is 1.30, which is already out for testing, so I'll schedule this fix for the next release after that (it should be only a couple of lines of code). Thanks, Aijaz. ---------- Forwarded message ---------- From: Teresia Arthur Date: Fri, May 22, 2009 at 11:24 AM Subject: RE: [Taskforest-discuss] failure after rerun in taskforestd To: Aijaz Ansari <en...@us...> Ahhh….I found it. I was testing and clicked ‘rerun’ on a job then I stopped both taskforest and taskforestd. I replaced the family file with a much shorter one and restarted both taskforest and taskforestd. After doing that it seemed to get lost and I could never get the status page to show. I only got the errors which I sent you. Just now, I replaced the family file with the original and the status page is working again. Very interesting. |