On Wednesday 28 May 2003 12:20, Michael Martinez wrote:
>But why would it connect during "amcheck" but not during
> "amdump."?
>
>mike

Possibly an xinetd problem?  In all 3 sections of the amanda related 
file(s) put in the /etc/xinetd.d directory, the line containing the 
word 'disable' should be set to 'no'
I'm a bit ambiguous about the file count there because you can have 
3 seperate files, or you can combine them into one, xinetd doesn't 
seem to care.  Here's mine:
-------------------
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons & such it needs
service amanda
{
        disable = no
        socket_type     = dgram
        protocol        = udp
        wait            = yes
        user            = amanda
        group           = disk
        groups          = yes
        server          = /usr/local/libexec/amandad
}
service amandaidx
{
        disable = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amanda
        group           = disk
        groups          = yes
        server          = /usr/local/libexec/amindexd
}
service amidxtape
{
        disable = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amanda
        group           = disk
        groups          = yes
        server          = /usr/local/libexec/amidxtaped
}
---------------------
which is simply called 'amanda' but could in fact be named almost 
anything since its presence and contents are apparently what count.

>>On Wed, 2003-05-28 at 10:28, Jon LaBadie wrote:
>> On Wed, May 28, 2003 at 10:20:53AM -0400, Michael Martinez wrote:
>> > I'm running amanda server and clients on redhat linux systems.
>> >
>> > My tape server is a machine called "vision.csrees.usda.gov".
>> > It runs amanda 2.4.2p2 installed from rpm on Redhat 7.1.
>> >
>> > My new tape client is a machine called "plone" (listed below)
>> > which runs amanda 2.4.4 installed from source on Redhat 8.0.
>> >
>> > /usr/sbin/amcheck DailySet1 gives the green light for "plone",
>> > but /usr/sbin/amdump produces the following failure:
>> >
>> > FAILURE AND STRANGE DUMP SUMMARY:
>> >   plone.csre /boot lev 0 FAILED [could not connect to
>> > plone.csrees.usda.gov] plone.csre / lev 0 FAILED [input: can't
>> > open: ?
>> >   plone.csre / lev 0 FAILED [dump to tape failed]
>> >
>> > Why is the backup failing?
>>
>> The message said:
>>
>>   [could not connect to plone.csrees.usda.gov]
>>
>> Looks like network connectivity/permission problems.
>>
>> --
>> Jon H. LaBadie                  jon AT jgcomp DOT com
>>  JG Computing
>>  4455 Province Line Road        (609) 252-0159
>>  Princeton, NJ  08540-4322      (609) 683-7220 (fax)

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.