Hmmm,
It looks like I spoke too soon. The wait change did indeed make the
timeout error go away, but when the backup actually occured later that
night I remembered why I had changed the wait to no in the first place:
my_computer /dev/hda2 lev 0 FAILED [nak error:amandad busy]
So, I changed wait back to no, and added the EXTRAPOTIONS="-loop 100" to
/etc/sysconfig/xinetd.
That allowed it to run for several hours and into the backup. Only one
partition failed with:
my_computer /dev/hda3 lev 1 FAILED [could not connect to my_computer]
I've flushed the iptables, so it's not a firewall issue.
Any additional suggestions would be greatly appreciated.
My original message and reply follows.
Thanks,
Jenn
Jennifer Peterson wro
te:
> I would like to thank everybody for their replies. Changing my wait =
> no to wait = yes in xinetd.d/amanda did the trick.
>
> Jennifer Peterson wrote:
>
>> Hi,
>>
>> I wonder if anybody can help me out with this problem. I installed
>> amanda-client-2.4.2p2-1.i386.rpm on my Redhat 7.1 box, and I have
>> amandad running through xinetd like so:
>> service amanda
>> {
>> socket_type = dgram
>> protocol = udp
>> wait = no
>> user = amanda
>> group = disk
>> server = /usr/lib/amanda/amandad
>> disable = no
>> groups = yes
>> only_from = "backup_computer"
>> }
>>
>> When I restart xinetd, the amanda service starts up just fine, and
>> when I amcheck from my backup computer, no errors are reported.
>> However, after about 20 minutes or so, I get this in my syslog:
>>
>> Oct 22 15:24:11 my_computer xinetd[29480]: amanda service was
>> deactivated because of looping
>> Oct 22 15:24:41 my_computer amandad[30051]: error receiving message:
>> timeout
>>
>> The amandad error log on my_computer reads basically the same thing:
>> amandad: dgram_recv: timeout after 30 seconds
>> amandad: error receiving message: timeout
>>
>> At this point amcheck also fails.
>>
>> If I restart xinetd right before the backup begins, then the backup
>> works.
>>
>> Any suggestions?
>>
>> Thanks,
>>
>> Jenn Peterson
>>
>>
>
>
