/tmp has 1.8 GB free (all other partitions have plenty of space as well) and I did a dig on the name as well as checked the /etc/hosts file and the correct information comes back from both of them. I have tried to start amdump as the user amanda by running "amdump DailySet1" and I get the same thing kicked back to me in the email with no errors coming back to me on the terminal.
On Thu, 2004-04-29 at 00:52, [EMAIL PROTECTED] wrote: > may be your DNS was altered. check it out via dig/nslookup > > another strange thing I've had somtime was that the filesystem for the logs > / tmp was running out of space... check it with df -k > > have you ever tried to start it manually? the same error occurs? > > > > > > > Kris Vassallo To: [EMAIL PROTECTED] > . > <[EMAIL PROTECTED]> cc: (bcc: Arne Briesenick/DBS/GDB) > > Sent by: Subject: amdump: request timed > out.. already read FAQ & troubleshooting > [EMAIL PROTECTED] [Deutsche Boerse Systems:Virus checked] > > rg > > > > > > 29.04.2004 09:37 > > > > > > > > > > One day last week after AMANDA had been running fine for months it > just broke and I now am seeing this in my email log daily: > > FAILURE AND STRANGE DUMP SUMMARY: > host.domain /backup/repo lev 0 FAILED [Request to host.domain.com > timed out.] > host.domain /home lev 0 FAILED [Request to host.domain.com timed > out.] > (with host.domain being a FQDN which the machine can resolve) > > - I am getting debug logs in /tmp/amanda > - I have checked that amandaidx and amandad are both enabled in > xinetd.d and have restarted xinetd.d > - running "su - amanda -c "amcheck DailySet1" " reveals: > Amanda Backup Client Hosts Check > -------------------------------- > Client check: 3 hosts checked in 0.226 seconds, 0 problems found > > - The host that is having the problem is also the server, yet it is > backing up 2 other hosts just fine. > - I have the FQDN in .amandahosts > - Running amandad as the amanda user causes ~30 of hanging before it > times out like its supposed to > - There is nothing about amandad or xinetd being broken in > /var/log/messages > > I am starting to run out of hair to pull out! Does anyone have any > ideas on what could be causing this?
