Hi list,
I've got a strange problem, and my current search didn't find a
solution yet, although I was able to find people with similar
problems, but the several mentioned solutions didn't match my problem
here.
Randomly, some jobs don't seem to be finished correctly. I'm running
bacula 2.4.3 on both the server (SLES10-SP2) and the client (Debian
Lenny).
The status of the director mentions this about the client's state:
Running Jobs:
JobId Level Name Status
======================================================================
59 Increme client.hostname.tld.2009-01-07_00.30.46 has terminated
====
While the "status client" tells me that everything is fine:
Connecting to Client client-fd at client.hostname.tld:9102
client-fd Version: 2.4.3 (10 October 2008) i486-pc-linux-gnu debian lenny/sid
Daemon started 02-Jan-09 11:51, 6 Jobs run since started.
Heap: heap=991,232 smbytes=82,664 max_bytes=530,982 bufs=75 max_bufs=1,055
Sizeof: boffset_t=8 size_t=4 debug=0 trace=0
Running Jobs:
Director connected at: 07-Jan-09 09:57
No Jobs running.
====
Terminated Jobs:
JobId Level Files Bytes Status Finished Name
======================================================================
37 Full 675,908 37.54 G OK 02-Jan-09 14:44 client-fd
43 Incr 1,815 363.6 M OK 03-Jan-09 00:41 client-fd
46 Incr 2,315 897.6 M OK 04-Jan-09 00:37 client-fd
49 Incr 2,408 766.2 M OK 05-Jan-09 00:35 client-fd
53 Full 678,763 37.65 G OK 06-Jan-09 03:24 client-fd
59 Incr 3,322 894.4 M OK 07-Jan-09 00:36 client-fd
====
When I'm scrolling back at the console, I see that the job has
terminated successfully, since I find the output which would be mailed
as status report:
[...]
Termination: Backup OK
07-Jan 00:35 backup-dir JobId 59: Begin pruning Jobs.
07-Jan 00:35 backup-dir JobId 59: No Jobs found to prune.
07-Jan 00:35 backup-dir JobId 59: Begin pruning Files.
07-Jan 00:35 backup-dir JobId 59: No Files found to prune.
07-Jan 00:35 backup-dir JobId 59: End auto prune.
But, I'm missing the final status report email and the client is still
referenced as "has terminated" within the console. The sql data as
been updated as well, so it looks to me like the job has been run
successfully but the email has not been generated and the status
within the director didn't get updated.
When restarting the director, everything is fine again. But this
shouldn't be an option to solve this...
Does anyone here have an idea on this case?
--
Le deagh dhùraghd,
Frank Altpeter
There is no way to happiness. Happiness is the way.
-- Buddha
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
