Results 1 to 2 of 2

Thread: Strange amrecover behaviour

  1. #1
    Join Date
    Jul 2013
    Posts
    12

    Default Strange amrecover behaviour

    Hello everybody,

    I've configured an amanda server (2.6.1p2) and several clients (same version) on SL 6.3 (RHen 6.3 like).
    It's working perfeclty everywhere except on a client where everytime I launch amrecover it fails twice and then works. Always following this sequence:

    Code:
    # amrecover 
    AMRECOVER Version 2.6.1p2. Contacting server on coresrv09.linux.crg.es ...
    [request failed: recv error: Connection reset by peer]
    # amrecover 
    AMRECOVER Version 2.6.1p2. Contacting server on coresrv09.linux.crg.es ...
    NAK: user root from galaxy.crg.eu is not allowed to execute the service amindexd: Please add the line "galaxy.crg.eu root amindexd amidxtaped" to /var/lib/amanda/.amandahosts on the server
    # amrecover 
    AMRECOVER Version 2.6.1p2. Contacting server on coresrv09.linux.crg.es ...
    220 coresrv09 AMANDA index server (2.6.1p2) ready.
    Setting restore date to today (2013-07-09)
    200 Working date set to 2013-07-09.
    200 Config set to Services.
    200 Dump host set to galaxy.crg.es.
    Use the setdisk command to choose dump disk to recover
    amrecover> listdisk
    200- List of disk for host 
    201- mysql_3
    200 List of disk for host 
    amrecover> quit
    200 Good bye.
    It's conf is

    Code:
    /etc/amanda/amanda-client.conf 
    # amanda.conf - sample Amanda client configuration file.
    #
    # This file normally goes in /etc/amanda/amanda-client.conf.
    #
    conf "Services" # your config name
    
    index_server "coresrv09.linux.crg.es" # your amindexd server
    
    tape_server "coresrv09.linux.crg.es" # your amidxtaped server
    
    #tapedev "/dev/null" # your tape device
    # auth - authentication scheme to use between server and client.
    # Valid values are "bsd", "bsdudp", "bsdtcp" and "ssh".
    # Default: [auth "bsdtcp"]
    
    auth "bsdtcp"
    and the server part

    Code:
    Client 			root			amindexd 	amidxtaped
    IT's strange the way it works because I always see the above errors in the same order.

    Anyone have seen this before?

    Thanks in advance,
    Arnau

  2. #2
    Join Date
    Jul 2013
    Posts
    12

    Default

    Hello,

    I did find the source of the problem. The client hostname resolves to an alias with 3 names (.es, .cat, .eu), so if the returned hostname isn't the one listed in amandahosts, the client fails.
    I've added the 3 entries and now it works perfeclty.

    Arnau

Posting Permissions

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