Scott Ruckh wrote: > I don't think it is the power supply. Running bacula causes the crash. > The machine only crashes when bacula is involved. This machine does not > do 24x7 backups. Full backups, for 3 clients, take at most 6 hours. > Incremental backups for these same 3 clients takes about 20 minutes. > Bacula may not be the root cause of the problem, but it is definitely > indirectly the cause of the problem.
*Nothing* should be able to cause the kernel to crash. It is either a kernel bug (not bacula's fault), or faulty hardware (also not bacula's fault). Even if it is only bacula that is successfully pushing marginal hardware over the edge, that is not bacula's fault. I have seen hardware that appears to work perfectly but cannot compile software due to numerous unreproducible internal compiler errors. Turned out to be faulty RAM that only seemed to ever cause problems in compiles. I have hardware that will run memtest86 fine for 6 days and then fail on the seventh. IMO you are trying to fix the symptoms, not the cause of the problem. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
