Hi.
I see the same thing. My log:
...
24-Apr 10:08 bkpsrv-sd JobId 4063: Job frontier-var.2009-04-24_10.08.29_05
marked to be canceled.
24-Apr 10:09 bkpsrv-sd JobId 4063: Failed command: Jmsg Job=frontier-
var.2009-04-24_10.08.29_05 type=6 level=1240556927 bkpsrv-sd JobId 4063: Job
frontier-var
RE logs...
Looks like the cancel request is put in, but results in an error.
Note that the message about there being no "SL500-changer" with type
"LTO-3" in the SD resources seems bogus -- that's the storage device and
type with which all the non-canceled jobs successfully run.
sample log (se
> On Wed, 22 Apr 2009 16:07:49 -0700, Stephen Thompson said:
>
> I recently upgrade from 2.4.4 to 3.0.0. Everything went very smoothly
> and the new version is running at least as well as the previous.
>
> Once peculiar thing I've noticed is that if I cancel a job, rather than
> the job be
Hi,
23.04.2009 01:07, Stephen Thompson wrote:
> Hello everyone.
>
> I recently upgrade from 2.4.4 to 3.0.0. Everything went very smoothly
> and the new version is running at least as well as the previous.
>
> Once peculiar thing I've noticed is that if I cancel a job, rather than
> the job be
Hello everyone.
I recently upgrade from 2.4.4 to 3.0.0. Everything went very smoothly
and the new version is running at least as well as the previous.
Once peculiar thing I've noticed is that if I cancel a job, rather than
the job being set to a "Canceled by user" state, it winds up being set
