Task expiration
-
Would it be possible to have FOG automatically kill tasks and snapins that fail to complete after a set time limit say 24 hours by default.
-
Joseph,
I would hit that like button so many times if it was so easy to accomplish this. I brought this up a few times but there is just a massive amount of work to do this and many issues that could crop-up due to this. I know this isn’t what you wanted to hear but I’ll keep poking possibly we can get this added.
-
Are any of the issues also encountered if I am often killing the old tasks in the web interface.
-
Tasks that did not occur or failed to start will only usually remain in the Task management. These are fine to delete. However, you should investigate why these machines did not execute the tasks that you had given them.
The issues I’m talk about are canceling mid-task. If the auto-cancel option cancels during a multi-cast or uni-cast it may cause issues. However, if these particular tasks take that long(12hrs) then it is due to another factor or you are trying to do way too many machines at once.
-
The usual issues are the tech starting the task is not following thru and the machine is shutdown or an image is sent to a group and one of the machines has been removed or similar issues. Its just a basic housekeeping task because we have such a large site and a large number of admins using fog many of which aren’t under my control or very technically orientated.
-
[quote=“Joseph Hales, post: 44533, member: 18131”]The usual issues are the tech starting the task is not following thru and the machine is shutdown or an image is sent to a group and one of the machines has been removed or similar issues. Its just a basic housekeeping task because we have such a large site and a large number of admins using fog many of which aren’t under my control or very technically orientated.[/quote]
It might be possible to create a separate service that runs independent of FOG, that periodically looks through the active tasks and gets rid of the old ones… based on an expiration amount-of-time set in a .conf file…
I’m learning C++ at the moment, it won’t be long till I’ll be able to write such a thing.
-
I will see if I can look into adding such a feature this weekend.
Wayne, it’s much simpler to just add a schema to specify a “timeout” and if the task creation time and state are not set at that point, have it cancel the task.
