gene heskett wrote:
On Wednesday, May 25, 2011 11:23:04 AM Jean-Louis Martineau did opine:

gene heskett wrote:
On Wednesday, May 25, 2011 08:30:37 AM Jean-Louis Martineau did opine:

Telling me to re-read amanda-auth.  I have, several times, but it is
not clear to me what else I need to do.  You also asked for my
complete xinetd.d/amanda file:
-------------------------------
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons & such it needs
service amanda
{

        disable = no

#       only_from       = coyote.coyote.den

        flags           = IPv4
        socket_type     = dgram
        protocol        = udp
        wait            = yes
        user            = amanda
        group           = disk
        groups          = yes
        server          = /usr/local/libexec/amanda/amandad
        server_args     = -auth=bsdtcp amdump amindexd amidxtaped

}
I don't remember how many times I told you to look at the man
page!!!!!!!!!!!
Please look at the example for bsdtcp in the amanda-auth man page:
       Client example of using bsdtcp authorization for xinetd server
       and for Amanda user "amandabackup":

       service amanda
       {
            only_from       = amandaserver.example.com
amandaclient.example.com
            socket_type     = stream
            protocol        = tcp
            wait            = no
            user            = amandabackup
            group           = disk
            groups          = yes
            server          = /path/to/amandad
            server_args     = -auth=bsdtcp amdump
            disable         = no
       }

Now that you finally posted your xinetd file, I can tell you what's
wrong. Fix the socket_type, protocol and wait lines.

Tell me how the man page can be improved?

By pointing out that the wait, socket type, and protocol also change.  If
it is mentioned, it is not mentioned in the context that seems to apply.
It is in the example for xinetd configuration for bsdtcp, what is wrong with that example?
Now, I have done those changes to my local xinetd.d/amanda, so it looks like 
this:

[root@coyote example]# cat /etc/xinetd.d/amanda
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons & such it needs
service amanda
{
        disable = no
        only_from       = coyote.coyote.den shop.coyote.den
        flags           = IPv4
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amanda
        group           = disk
        groups          = yes
        server          = /usr/local/libexec/amanda/amandad
        server_args     = -auth=bsdtcp amdump
#       amindexd amidxtaped
}
#service amandaidx
#{
#       disable = no
#        socket_type     = stream
#        protocol        = tcp
#        wait            = no
#        user            = amanda
#        group           = disk
#        groups          = yes
#        server          = /usr/local/libexec/amanda/amindexd
#}
#service amidxtape
#{
#       disable = no
#        socket_type     = stream
#        protocol        = tcp
#        wait            = no
#        user            = amanda
#        group           = disk
#        groups          = yes
#        server          = /usr/local/libexec/amanda/amidxtaped
#}

And amcheck is now happy with _this_ machine. However when I made similar changes to the shop machines inetd.conf as show by this grep:



I changed inetd.conf on the shop machine to:
amanda stream tcp nowait backup /usr/lib/amanda/amandad amandad -auth=bsdtcp 
amdump

But the amcheck still fails:
WARNING: shop: selfcheck request failed: Connection refused
Client check: 2 hosts checked in 10.050 seconds.  1 problem found.
inetd config looks good, do you restarted inetd daemon?
That amcheck*debug is attached. I also found the log files on the shop machine, but these amcheck runs are not generating a log.
If inetd do not execute amandad, then amandad is not run and it can write a log file.
You must check the inetd log.

Jean-Louis

Reply via email to