 |
Reschedule on error is not intended to cover Bareos Director restart. However, it should work if you restart the fd. |
|
|
Can we reopen this. I never got notification that it was in progress. So, is it indicative of a problem when the log TRIES to reschedule the job - but simply doesn't? |
|
|
OK. It DID work when I killed the fd. However, can you tell me what sorts of errors WILL trigger a restart (I don't see that in the manual). We're not just concerned with file errors, but also... - Tape drive failure. - Accidental system restart or server power failure. - OS crash or hang. - Daemon crashes or hangs. |
|
|
This can be marked as resolved |
|
|
How was this resolved? Is there some kind of documentation by now? |
|
|
I don't see what kind of documentation you expect? Reschedule on error does not work for a director restart (and was never intended to do this). Its purpose is to rerun a job that failed. So what else do you need? |
|
|
Well I did not reproduce this but the Log of rightmirem says that the job terminated with an error and therefore it should be rescheduled as far as I understand. https://docs.bareos.org/Configuration/Director.html?highlight=reschedule#config-Dir_Job_RescheduleOnError Although I see that this feature is not intended to cover director crashes the documentation should mention on what kind of failure a user can expect a reschedule and what does not trigger one (like the already mentioned 'Cancel') However the log should never report that a job is rescheduled if that one is not going to be executed. |
|
|
The problem is probably that the director does not have a persistent schedule. So when the job is rescheduled (and the reschedule log message is written) and then the director is restarted, the scheduling information is lost during the restart. With the current design of rescheduling this cannot be fixed. However, we can document that limitation. |
|
|
Thanks for the info! I would appreciate if the doc explains that behaviour and as far as I'm concerned this ticket can be closed then. |
|
|
When the director starts, couldn't it load the information from the database to re-discover jobs that have been rescheduled? This should be applicable to the cancel waiting jobs issue (https://bugs.bareos.org/view.php?id=1148) also. I don't see where a complete re-write/re-design is necessary to accomplish either of these features, while adding quite a bit of value to BareOS. |
|
|
What you're describing requires a redesign and probably also a major rewrite of the feature. It would have to work based on the job history in the catalog instead of the way it currently works. |
|
|
Warning in documentation is added in PR1543 |
- Anonymous
