Hi people. Yesterday my bacula-dir process was killed by the OOM-killer. We are running 2.0.3 (no patches) on Dapper/amd64 compiled from source. The system has 10GB of memory and 4GB of swap. MySQL is taking roughly 1GB - but the rest can be consumed by bacula-*. This means that bacula-dir consumed ~13GB of memory at the time the OOM-killer decided it had to be put down.
The system was only running a few days and had run 120 backup jobs. It died in the middle of migration (we always do backup to disk and migrate to tape). I've seen bacula-dir grow big (4-5GB) on this system before - but it has never OOMet. Per. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
