|
Hi, I have configured a job as following: Job { Name = "Backup-client" JobDefs = "Usuarios" FileSet = "Usuario-Windows" Client = client-fd Write Bootstrap = "/var/bacula/client.bsr" Pool = Client Enabled = yes Messages = Client Schedule = "Usuarios Wed 13:00" Run Before Job = "/etc/bacula/scripts/check-status-client.sh '%c'" } Script "Run Before Job" is this: #! /bin/bash echo "sta client=$1" | bconsole | grep -v -q "Failed to connect to Client" With this configuration, I thought that director tried to connect to the client and, in case of a "Failed to connect to Client", jobs was cancelled and director went on with next scheduled job. However, log from job "cancelled" says it: 0-Jan 14:00 server JobId 12386: Fatal error: No Job status returned from FD. 10-Jan 13:45 server JobId 12386: Warning: bsock.c:129 Could not connect to Client: client-fd on client_IP:9102. ERR=No route to host Retrying ... 10-Jan 13:52 server JobId 12386: Warning: bsock.c:129 Could not connect to Client: client-fd on client_IP:9102. ERR=No route to host Retrying ... 10-Jan 13:59 server JobId 12386: Warning: bsock.c:129 Could not connect to Client: client-fd on client_IP:9102. ERR=No route to host Retrying ... 10-Jan 14:00 server JobId 12386: Fatal error: bsock.c:135 Unable to connect to Client: client-fd on client_IP:9102. ERR=Interrupted system call 10-Jan 14:00 server JobId 12386: Error: Bacula server 3.0.1 (30Apr09): 10-Jan-2010 14:00:44 Build OS: x86_64-unknown-linux-gnu suse 10 JobId: 12386 Job: Backup-client.2010-01-10_13.00.00_59 Backup Level: Incremental, since=2009-12-01 13:16:09 Client: "client-fd" 3.0.2 (18Jul09) Linux,Cross-compile,Win32 FileSet: "Usuario-Windows" 2008-11-24 12:34:05 Pool: "Client" (From Job resource) Catalog: "Catalogo-USUARIOS" (From Client resource) Storage: "BackupRAID5" (From Pool resource) Scheduled time: 10-Jan-2010 13:00:00 Start time: 10-Jan-2010 13:45:34 End time: 10-Jan-2010 14:00:44 Elapsed time: 15 mins 10 secs Priority: 12 FD Files Written: 0 SD Files Written: 0 FD Bytes Written: 0 (0 B) [...] After reading it, I'm trying to understand that job is scheduled at 13:00:00 (OK, because I am the system manager and I configured all clients and schedules), job starts at 13:45:34 (due to previous scheduled jobs), but end time is 14:00:44, so I think director is trying to connect to client during 15 minutes. If "Run Before Job" returns non-zero, jobs should be cancelled... or not?? Please, help!! How can I check if script returns correct value? (0 -> execute job // non-zero -> cancel job) Thanks!!! |
------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
