Results 1 to 10 of 10

Thread: amrecover timeout waiting for ACK

  1. #1
    Join Date
    Feb 2011
    Location
    Memphis TN USA
    Posts
    7

    Default amrecover timeout waiting for ACK

    Greetings to the forum.
    I have Amanda 3.2.1 installed on an Ubuntu 10.04 backup server and it's backing up beautifully but I am having problem with restores.
    I'm backing up to vtapes on disk so I can restore using dd and tar, but would really like to leverage the power of Amanda.
    When I attempt as root (sudo -s) to amrecover MyConfig I get the following:

    AMRECOVER Version 3.2.1. Contacting server on localhost ...
    [request failed: timeout waiting for ACK]


    I'm a neophyte Amanda user, so I'm still learning what logs to look in - these are in syslog:

    Mar 1 10:01:06 baksvr xinetd[16290]: execv( /usr/lib/amanda/amandad ) failed: No such file or directory (errno = 2)

    I suspect this is probably the issue - xinetd can't see the amandad daemon.

    There is a /var/log/amanda/amandad directory but there are no recent entries there.

    In /var/log/amanda/client/ConfigName there is an amrecover debug log:
    Mon Feb 28 10:31:23 2011: amrecover: pid 14977 ruid 0 euid 0 version 3.2.1: start at Mon Feb 28 10:31:23 2011
    Mon Feb 28 10:31:23 2011: amrecover: config_overrides: conf Projects
    Mon Feb 28 10:31:23 2011: amrecover: pid 14977 ruid 0 euid 0 version 3.2.1: rename at Mon Feb 28 10:31:23 2011
    Mon Feb 28 10:31:23 2011: amrecover: security_getdriver(name=bsd) returns 0xb771ac20
    Mon Feb 28 10:31:23 2011: amrecover: security_handleinit(handle=0x9da5930, driver=0xb771ac20 (BSD))
    Mon Feb 28 10:31:23 2011: amrecover: dgram_bind: setting up a socket with family 2
    Mon Feb 28 10:31:23 2011: amrecover: bind_portrange2: Try port 604: Available - Success
    Mon Feb 28 10:31:23 2011: amrecover: dgram_bind: socket 3 bound to 0.0.0.0.604
    Mon Feb 28 10:31:23 2011: amrecover: dgram_send_addr(addr=0x9da5950, dgram=0xb7723564)
    Mon Feb 28 10:31:23 2011: amrecover: (sockaddr_in *)0x9da5950 = { 2, 10080, 127.0.0.1 }
    Mon Feb 28 10:31:23 2011: amrecover: dgram_send_addr: 0xb7723564->socket = 3
    Mon Feb 28 10:31:33 2011: amrecover: dgram_send_addr(addr=0x9da5950, dgram=0xb7723564)
    Mon Feb 28 10:31:33 2011: amrecover: (sockaddr_in *)0x9da5950 = { 2, 10080, 127.0.0.1 }
    Mon Feb 28 10:31:33 2011: amrecover: dgram_send_addr: 0xb7723564->socket = 3
    Mon Feb 28 10:31:43 2011: amrecover: dgram_send_addr(addr=0x9da5950, dgram=0xb7723564)
    Mon Feb 28 10:31:43 2011: amrecover: (sockaddr_in *)0x9da5950 = { 2, 10080, 127.0.0.1 }
    Mon Feb 28 10:31:43 2011: amrecover: dgram_send_addr: 0xb7723564->socket = 3
    Mon Feb 28 10:31:53 2011: amrecover: security_seterror(handle=0x9da5930, driver=0xb771ac20 (BSD) error=timeout waiting for ACK)
    Mon Feb 28 10:31:53 2011: amrecover: security_close(handle=0x9da5930, driver=0xb771ac20 (BSD))


    Any help?

  2. #2
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    amrecover use the 'bsd' auth, is it what you want?
    What is the xinetd configuration?
    Do /usr/lib/amanda/amandad is the correct path, where do you installed the deamon?

  3. #3
    Join Date
    Feb 2011
    Location
    Memphis TN USA
    Posts
    7

    Default amandad is missing

    Thanks very much for your reply.

    Since I'm restoring a file to a temporary directory on the local host, I guess bsd authentication should be fine - the backup server is backing up another server; it's using ssh authentication and shared keys to authenticate to the target server and that's working.

    There is no amandad file in /usr/lib/amanda
    There is one in /usr/libexec/amanda but I think that's an old version left from when I tried to install Amanda from the Ubuntu repositories, which was 2.6.p1 I believe. I removed that installation and used dpkg to install 3.2.1. What's strange is after my initial installation I did a restore of a test directory successfully using amrecover, but it's nto working now.

    There are two files in /etc/xinetd.d - amanda and amandaserver

    amanda
    # default: on
    # description: The amanda service
    service amanda
    {
    # only_from = <Amanda server>
    socket_type = dgram
    protocol = udp
    wait = yes
    user = backup
    group = backup
    groups = yes
    server = /usr/lib/amanda/amandad
    server_args = -auth=bsd amdump amindexd amidxtaped
    disable = no


    amandaserver
    # default: on
    #
    # description: Amanda services for Amanda server and client.
    #

    service amanda
    {
    disable = no
    flags = IPv4
    socket_type = stream
    protocol = tcp
    wait = no
    user = amandabackup
    group = disk
    groups = yes
    server = /usr/libexec/amanda/amandad
    server_args = -auth=bsdtcp amdump amindexd amidxtaped


    I am pretty sure the problem is the missing amandad file - I'm not sure why it's not there.
    I've extracted and looked at the content of the amandaserver .deb file for this version and don't see amandad in it - I'm not sure where it should be installed from.
    Thanks again for your time and attention.

  4. #4
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    The amanda file is for bsd auth.
    The amandaserver file is configured for bsdtcp auth
    Both should have the same amandad path, or you can remove them if you don't use them.
    You can run 'amgetconf build.amlibexecdir' to find the directory where amandad is.

    You can use the 'local' auth since you restore on the server

  5. #5
    Join Date
    Feb 2011
    Location
    Memphis TN USA
    Posts
    7

    Default Still [request failed: timeout waiting for ACK]

    Verified that amandad is in /usr/libexec/amanda/
    Edited both xinetd.d entries as follows:

    amanda
    # default: on
    # description: The amanda service
    service amanda
    {
    # only_from = <Amanda server>
    socket_type = dgram
    protocol = udp
    wait = yes
    user = backup
    group = backup
    groups = yes
    server = /usr/libexec/amanda/amandad
    server_args = -auth=local amdump amindexd amidxtaped
    disable = no
    }


    amandaserver
    # default: on
    #
    # description: Amanda services for Amanda server and client.
    #

    service amanda
    {
    disable = no
    flags = IPv4
    socket_type = stream
    protocol = tcp
    wait = no
    user = amandabackup
    group = disk
    groups = yes
    server = /usr/libexec/amanda/amandad
    server_args = -auth=local amdump amindexd amidxtaped
    }


    I did service xinetd.d restart but still get the timeout waiting for ACK error.
    When I attempt to do amrecover without a config, it creates a
    /var/log/amanda/client/DailySet1 directory even though there is no DailySet1 config - not sure where that's coming from.
    In the amrecover.20110302100613.debug file, I can see it's still trying to use BSD authentication instead of local. I think you are correct - it's an authentication issue.
    Debug log:
    Wed Mar 2 10:06:13 2011: amrecover: pid 17957 ruid 0 euid 0 version 3.2.1: start at Wed Mar 2 10:06:13 2011
    Wed Mar 2 10:06:13 2011: amrecover: pid 17957 ruid 0 euid 0 version 3.2.1: rename at Wed Mar 2 10:06:13 2011
    Wed Mar 2 10:06:13 2011: amrecover: security_getdriver(name=bsd) returns 0xb7746c20
    Wed Mar 2 10:06:13 2011: amrecover: security_handleinit(handle=0x976f938, driver=0xb7746c20 (BSD))
    Wed Mar 2 10:06:13 2011: amrecover: dgram_bind: setting up a socket with family 2
    Wed Mar 2 10:06:13 2011: amrecover: bind_portrange2: Try port 794: Available - Success
    Wed Mar 2 10:06:13 2011: amrecover: dgram_bind: socket 3 bound to 0.0.0.0.794
    Wed Mar 2 10:06:13 2011: amrecover: dgram_send_addr(addr=0x976f958, dgram=0xb774f564)
    Wed Mar 2 10:06:13 2011: amrecover: (sockaddr_in *)0x976f958 = { 2, 10080, 127.0.0.1 }
    Wed Mar 2 10:06:13 2011: amrecover: dgram_send_addr: 0xb774f564->socket = 3
    Wed Mar 2 10:06:23 2011: amrecover: dgram_send_addr(addr=0x976f958, dgram=0xb774f564)
    Wed Mar 2 10:06:23 2011: amrecover: (sockaddr_in *)0x976f958 = { 2, 10080, 127.0.0.1 }
    Wed Mar 2 10:06:23 2011: amrecover: dgram_send_addr: 0xb774f564->socket = 3
    Wed Mar 2 10:06:33 2011: amrecover: dgram_send_addr(addr=0x976f958, dgram=0xb774f564)
    Wed Mar 2 10:06:33 2011: amrecover: (sockaddr_in *)0x976f958 = { 2, 10080, 127.0.0.1 }
    Wed Mar 2 10:06:33 2011: amrecover: dgram_send_addr: 0xb774f564->socket = 3
    Wed Mar 2 10:06:43 2011: amrecover: security_seterror(handle=0x976f938, driver=0xb7746c20 (BSD) error=timeout$
    Wed Mar 2 10:06:43 2011: amrecover: security_close(handle=0x976f938, driver=0xb7746c20 (BSD))


    Any idea where it's getting the "DailySet1" from and where the file is that is telling amrecover to use BSD auth?
    Thanks again for your help - it's really helped me zero in. I think we're almost to the point where I'll have a fix.

  6. #6
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    Why do you changed the -auth argument?
    The UDP protocol is always for bsd
    The TCP protocol is for bsdtcp
    The local auth do not use xinetd.

    DailySet1 is the default configuration
    amrecover use the auth set in amanda-client.conf (default is bsd) , you can also overwrite it on the command line with the -oauth=??? argument

  7. #7
    Join Date
    Feb 2011
    Location
    Memphis TN USA
    Posts
    7

    Default Thanks - that was the solution

    Thanks again for your patience working with a neophyte.
    I was missing the amanda-client.conf file. Now that I added one for each of my configs, I am able to restore very nicely on the local host.

    Thank you very much once more for your precise questions and guidance - despite my ignorance you led me to the answer.

    I am in your debt. (doffs hat, bows in gratitude). Thank you sir! (or ma'am, as the case may be).

  8. #8
    Join Date
    Dec 2010
    Posts
    25

    Default amrecover ACK timeout

    Hi, I have the same problem, will not let me throw amrecover command, I get the ACK timeout error, can you help me?

    Thanks
    Greetings

  9. #9
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    Do not hijack a thread.
    You have the same symtom, but probably a different problem.
    Open your own thread and post a lot more information because nobody can help if you only say that you get 'ACK timeout'

  10. #10
    Join Date
    Dec 2010
    Posts
    25

    Default

    Sorry for the intrusion in the thread, I will open a new case.



    Greetings

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •