Re: [Bacula-users] how to debug a job
2015-01-21 21:44:36
On 01/21/2015 06:41 PM, Bill Arlofski wrote:
> Bacula has a hard-coded 6 day limit on a job's run time. 518401 seconds =
> 6.00001157 days, so it appears that is the cause for the watchdog killing the
> job.
Hard-coded, huh? Nobody's tried backing up that big data I keep hearing
about?
> Does it ask you for a new volume?
No. Good guess, but the storage is a vchanger and it's working just fine.
I killed the lot and replaced the spool disk in the unlikely case that
was slowing things down -- unlikely because it's a tler disk and
shouldn't have this particular failure mode. I restarted the offending
job, we'll see what happens...
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|