Hi Alan
Is 1.38.9 meant to be an older version?
Jobs that fail are follow-up jobs where the predecessor succeeded.
For example:
First job succeeds fine.
Twenty minutes later the said follow-up job starts at scheduled time, requiring the same(!) volume, which is still in the drive and is not used by any other job. This jobs fails after the following output:
07-Jul 23:00 heem-sd: 3301 Issuing autochanger "loaded drive 0" command.
07-Jul 23:00 heem-sd: 3991 Bad autochanger "loaded drive 0" command: ERR=Operation not permitted.
07-Jul 23:00 heem-sd: 3301 Issuing autochanger "loaded drive 0" command.
07-Jul 23:00 heem-sd: 3991 Bad autochanger "loaded drive 0" command: ERR=Operation not permitted.
07-Jul 23:00 heem-sd: 3304 Issuing autochanger "load slot 15, drive 0" command.
07-Jul 23:00 heem-sd: A-1_dali-AAW-Con-Fin-Man_________.2006-07-07_23.00.00 Fatal error: 3992 Bad autochanger "load slot 15, drive 0": ERR=Child exited with c
ode 1.
07-Jul 22:59 dali-fd: A-1_dali-AAW-Con-Fin-Man_________.2006-07-07_23.00.00 Fatal error: job.c:1617 Bad response to Append Data command. Wanted 3000 OK data
, got 3903 Error append data
After that a third job starts, also going on the self-same volume (still in the drive): It can issue its "loaded drive 0" commands, gets its responses and succeeds just fine.
Strange!
Any ideas?
As to concurrent jobs:
I have no concurrent jobs running. Settings of "Maximum Concurrent Jobs" are "1" everywhere except for the -bacula-dir.conf: Director resource- and the -bacula-sd.conf: Storage resource- where the default value is 20.
Is that o.k.?
Greetings,
Christoff
Alan Brown <[EMAIL PROTECTED]> wrote on 11.07.2006 15:20:59:
> On Mon, 10 Jul 2006, Christoff Buch wrote:
>
> > Ok. But thanks for your time all the same!
> >
> >
> > "user100" <[EMAIL PROTECTED]> wrote on 10.07.2006 16:10:37:
> >
> >> Sorry forget it: "Fatal error: job.c: 1617 Bad response to Append Data
> >> command. Wanted 3000 OK data" - does not seems like the "permission-bug"
> >> here.
>
> This is an error on older versions of Bacula and happens when it attempts
> to start a job requiring a different volume to the one which is already in
> the drive _and_ in use by another job,
>
> It only occurs when concurrent jobs is set higher than 1
>
> It should be fixed in 1.38.11
>
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
