I have to second Paul on this one. If you would like, you could go through
any number of processes to make sure the AMANDA code is the same as it was a
month ago when everything was fine (MD5SUM against backups, Re-install,
etc.) and I expect you will still have the problem, which leaves either (a)
non-AMANDA software, or (b) hardware. As the hardware is subject to thermal
stress, and the sofware is only subject to stray alpha particles and disk
error, I'd lean towards hardware. As a test, if you have another server
available, you could build AMANDA on another machine and move the tape
subsystem over. If the problem doesn't follow...

> -----Original Message-----
> From: Paul Bijnens [mailto:paul.bijnens AT xplanation DOT com]
> Sent: Thursday, September 18, 2003 4:52 PM
> To: Crashers, Bart -- MFG, Inc.
> Cc: Amanda Users (E-mail)
> Subject: Re: Crashing machine
> 
> 
> Crashers, Bart -- MFG, Inc. wrote:
> 
> > Any ideas here?  Anyone heard of such a thing?  Am I 
> barking up the wrong
> > tree thinking that amanda might be responsible for my 
> crashes?  It's a real
> 
> Amanda just stresses your hardware a lot, uses a lot of cpu/memory 
> (gzip), loads the disks (holdingdisk), network (scsi-)bus, and will
> much faster trigger the problem.  I still suspect hardware.
> 
> 
> 
>