2008/5/17 FL <[EMAIL PROTECTED]>: > amanda was running fine against one client, until recently: amandad > thinks it's busy. > I'm not at all sure what changed or why it thinks it is busy: > > > Amanda Tape Server Host Check > ----------------------------- > Holding disk /var/tmp/amanda: 16963120 KB disk space available, that's > plenty > amcheck-server: slot 28: date 20080516 label Daily028 (active tape) > amcheck-server: slot 29: date 20080312 label Daily029 (exact label match) > NOTE: skipping tape-writable test > Tape Daily029 label ok > Server check took 152.753 seconds > > Amanda Backup Client Hosts Check > -------------------------------- > ERROR: NAK m248.gc.cuny.edu: amandad busy > Client check: 6 hosts checked in 10.798 seconds, 1 problem found > > (brought to you by Amanda 2.4.4p3) >
Maybe an old amandad process is still running? I don't know if amandad creates a pid file when it's running but there might be a pid file not deleted even though amandad has exited after the last backup run. Craig. -- Craig Dewick ([EMAIL PROTECTED]). http://lios.apana.org.au/~craig RailZone Australia: http://www.railzone.org ([EMAIL PROTECTED]) The SunShack: http://www.sunshack.org ([EMAIL PROTECTED]) ClassicSaab: http://www.classicsaab.net ([EMAIL PROTECTED])
