Martin Simmons wrote:

  >> Which version of bacula is running on dd-lx-oracle3?

Stephan> sorry, I totaly forgot: it's the bacula-client-1.36.3-1 RPM package Stephan> running on FC3.

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.

now we get closer: I modified my ClientRunBeforeJob to exit with 100. And I get exactly what your director says. Here's the output:

21-Sep 14:54 dd-lx-backup.dd.net-linx: Start Backup JobId 1015, Job=DD31.2005-09-21_14.54.35 21-Sep 14:54 dd-lx-oracle3.dd.net-linx: DD31.2005-09-21_14.54.35 Fatal error: ClientRunBeforeJob returned non-zero status=268435556. ERR=Child exited with code 100 21-Sep 14:54 dd-lx-backup.dd.net-linx: DD31.2005-09-21_14.54.35 Fatal error: FD gave bad response to ClientRunBeforeJob command: wanted 2000 OK RunBefore
 got: 2905 Bad RunBeforeJob command.

21-Sep 14:54 dd-lx-backup.dd.net-linx: DD31.2005-09-21_14.54.35 Error: Bacula 1.36.3 (22Apr05): 21-Sep-2005 14:54:39
  JobId:                  1015
  Job:                    DD31.2005-09-21_14.54.35
  Backup Level:           Incremental, since=2005-09-21 10:53:10
  Client:                 dd-lx-oracle3
  FileSet:                "Data-UNIX-Oracle" 2005-08-05 19:00:01
  Pool:                   "disk4"
  Storage:                "disk4"
  Start time:             21-Sep-2005 14:54:37
  End time:               21-Sep-2005 14:54:39
  FD Files Written:       0
  SD Files Written:       0
  FD Bytes Written:       0
  SD Bytes Written:       0
  Rate:                   0.0 KB/s
  Software Compression:   None
  Volume name(s):
  Volume Session Id:      33
  Volume Session Time:    1127203794
  Last Volume Bytes:      0
  Non-fatal FD errors:    0
  SD Errors:              0
  FD termination status:
  SD termination status:  OK
  Termination:            *** Backup Error ***


when I do the same thing as ClientRunAfterJob it does /not/ error out like this [1]. So it looks like there's a difference between ClientRunBeforeJob and ClientRunAfterJob return codes.

Stephan

[1] thats what I need since my ClientRunAfterJob parses a log file that
    is created during ClientRunBeforeJob - only then I know whether that
    backup has failed



-------------------------------------------------------
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

Reply via email to