>>>>> On Wed, 21 Sep 2005 16:49:57 +0200, Stephan Ebelt <[EMAIL PROTECTED]> >>>>> said:
Stephan> Martin Simmons wrote: >> >> Well I can't repeat this here with 1.36.3 on FreeBSD. What should happen is >> >> that the director says >> >> >> >> Fatal error: FD gave bad response to ClientRunBeforeJob command: wanted 2000 OK RunBefore >> >> got: 2905 Bad RunBeforeJob command. >> Stephan> now we get closer: I modified my ClientRunBeforeJob to exit with 100. Stephan> And I get exactly what your director says. Here's the output: >> >> Interesting. What is the largest number that behaves like this? Stephan> looks like it's 199. I suppose that makes sense in a warped kind of way :-) >> Does returning 5 like you did initially always return in "Backup OK -- with >> warnings" with "Non-fatal FD errors: 1"? Stephan> as ClientRunAfterJob it does. Ah, sorry, I misread your original post and was looking at ClientRunBeforeJob. However, I still don't get any Non-fatal errors on FreeBSD with the ClientRunAfterJob. In fact, it should be impossible because that number is returned to the Director before the ClientRunAfterJob runs! Stephan> as ClientRunBeforeJob returning 5 behaves as expected - the Job fails Stephan> with fatal error. The message in that case is rather normal: Stephan> 21-Sep 16:48 dd-lx-oracle3.dd.net-linx: DD31.2005-09-21_16.48.18 Fatal Stephan> error: ClientRunBeforeJob returned non-zero status=268435461. ERR=Child Stephan> exited with code 5 Stephan> when I do the same thing as ClientRunAfterJob it does /not/ error out Stephan> like this [1]. So it looks like there's a difference between Stephan> ClientRunBeforeJob and ClientRunAfterJob return codes. >> >> Yes, the result of ClientRunAfterJob is probably ignored because it is >> pointless making the job fail after it has finished. Stephan> hmmm, in my case not. Since I may have stored something that is not Stephan> (entirely) useful. Stephan> The background of this is that my ClientRunBeforeJob initiates a Oracle Stephan> database full export. The actual data is written to a FIFO pipe where Stephan> bacula sucks the data from during the backup job. This works pretty well Stephan> so far. Stephan> Finally I use the ClientRunAfterJob to parse the log file that oracle Stephan> creates. Since sometimes the database is not /entirely/ exported. The Stephan> dump might not contain everything we would need/want to restore. E.g. Stephan> somebody could have locked a single table. Or oracle produced a variety Stephan> of other warnings. In that case it is necessary to run the export again. Stephan> Thus the backup job should fail and notify us this way. Ah, I see. I don't know of any way to make that situation record a failed job. __Martin ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
