Chris Rodgers wrote: > Does anyone have any ideas what is causing bacula to jam up like this? > > I'm sorry if I have provided too much information, but I don't have any > real idea which parts of the configuration/etc. may be to blame.
That's what used to happen before I added the line # Timeout after ten minutes connecting to ngorongoro FDConnectTimeout = 10 to my bacula-dir.conf file. (See http://laplace.chem.ox.ac.uk/b/bacula-dir.conf) I thought that that would make bacula move on to the next job after 10 min. It seems to _almost_ work --> the director realises that it needs to move onto the new job, but the storage daemon ends up reporting job status "Other" and gets jammed up. (See my first e-mail for details of this.) At least, that's how it seems to me... What do you think? Chris. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
