Hello, On 6/20/2006 7:18 PM, Przemysław Staniszewski wrote: > Hello people :) > > I write here because I use backula and I don't know how can I make it > working. > My situation: > - some jobs are scheduled, when the time comes and they don't start > (because they are offline for example), they become canceled but the > next job which should run is not running. > I just have - waiting for max on the storage > > And if I check status of storage it's doesn't run anything. > > When I tray run some job later when nothing happen it become with status > waiting on max... > > I don't understand this situation. It shouldn't happen. I bacula-dir be > manually restared it works fine and and everything is ok. But if I don't > restart it every day it's in deadlock. > > Can anybody tell me what happens here?
Depends. How long do you wait when a job can't run? Bacula uses some long time-outs, so it might be that you'd have to wait for two hours before the director and SD finally decide that the job can not run and don't keep that job active. A good way to work around that, by the way, is a simple "Run Before Job" script that pings the host in question and exits with a return code of 0 if the host replies, or anything else otherwise. Arno > Regards > -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
