On Fri, Nov 04, 2016 at 12:37:42PM +0100, Josip Deanovic wrote:
> On Friday 2016-11-04 10:33:03 jahlives wrote:
> > Hi Josip
> >
> > The question was more: why the job is not completely canceled by 02:10
> > (10min after scheduled starttime)? Why took it until 02:36 to cancel it,
> > although bacu
On Friday 2016-11-04 10:33:03 jahlives wrote:
> Hi Josip
>
> Am 04.11.2016 um 09:54 schrieb Josip Deanovic:
> > I am guessing that you have other jobs with higher priority that
> > got run before this job you are monitoring and at the time the
> > bacula was ready to run it, its scheduled time was
Hi Josip
Am 04.11.2016 um 09:54 schrieb Josip Deanovic:
> I am guessing that you have other jobs with higher priority that
> got run before this job you are monitoring and at the time the
> bacula was ready to run it, its scheduled time was already past
> by more than 600 seconds (10 minutes) and
On Friday 2016-11-04 08:50:01 jahlives wrote:
> Hi list
>
> we have the issue with our bacula installation that jobs seems to be
> terminated too late (not as configured).
> We run bacula-dir in version 5.0.0 on a Centos 6.8 box. The job in
> question is configured that it can only run for max 10
Hi list
we have the issue with our bacula installation that jobs seems to be
terminated too late (not as configured).
We run bacula-dir in version 5.0.0 on a Centos 6.8 box. The job in
question is configured that it can only run for max 10 min by
Max Run Time = 600
Max Run Sched Time = 600
Max
