On Thursday 05 October 2006 15:14, Kern Sibbald wrote: > I have just released Bacula BETA 1.39.24.20061002 source and the Win32 > binaries to Source Forge. This is very likely to be the last beta release > or next to last release before the official 1.40 production release in the
I've just run into a major problem with 1.39.22. As I've not yet pinpointed the cause, I can't tell whether it's still present in .24, but if the final release is looming... In some circumstances the director process eats all available memory and then some. That is, 1GB ram and about 4GB swap on my machine. There is nothing in the log. It has happened twice so far, both times I was running a large job (about 300GB); it was waiting for or writing to the last (of eight) tapes. Some other jobs had been started by schedule and were waiting for a tape from a different pool. I'll try again with trace enabled, but that will take some days. Any ideas what might have gone wrong? And what debug level should I use? MfG, Ulrich -- Heinz Ulrich Stille / Tel.: +49-541-9400473 / Fax: +49-541-9400450 design_d gmbh / Wilhelmstr. 16 / 49076 Osnabrück / www.design-d.de ------------------------------------------------------------------------- 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 Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
