Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: amrecover problem

  1. #1
    Join Date
    Sep 2008
    Posts
    32

    Default amrecover problem

    hi, I have a problem with amrecover... this is what I do:

    Code:
    -bash-3.2# /usr/local/sbin/amrecover new -s myserver.mycompany.com -t myserver.mycompany.com
    AMRECOVER Version 2.6.0p2. Contacting server on myserver.mycompany.com ...
    [request failed: timeout waiting for ACK]
    -bash-3.2#
    amdump is working, it seems that there's no answer from the server - deamon that handles recovery action.... here's my /etc/inetd.conf:

    Code:
    amanda stream tcp nowait amanda /usr/local/libexec/amanda/amandad  amandad -auth=bsdtcp amdump amindexd amidxtaped # amanda
    and I added another line (for user root, as amrecover must be run as root):

    Code:
    amanda stream tcp nowait root /usr/local/libexec/amanda/amandad  amandad -auth=bsdtcp amdump amindexd amidxtaped # amanda
    I work on solaris sxde (solaris 10) as server, and trying to communicate with itself, here's amanda.conf for "new" config:

    Code:
    amanda$ cat new/amanda.conf
    # amanda.conf - Amanda configuration file for full dumps
    
    org "mycompany.com"          # your organization name for reports
    
    mailto "myemail@mycompany.com"  # space separated list of operators at your site
    
    dumpuser "amanda" # the user to run dumps under
    
    inparallel 15         # maximum dumpers that will run in parallel (max 63)
    
    dumporder "ttBTBTBTBTBTBTB" # specify the priority order of each dumper
                     
    netusage  10000000 Kbps # maximum net bandwidth for Amanda, in KB per sec
    
    #dumpcycle 4 weeks # the number of days in the normal dump cycle
    
    #runspercycle 20          # the number of amdump runs in dumpcycle days
    
    #tapecycle 25 tapes # the number of tapes in rotation
    
    bumpsize 20 Mb   # minimum savings (threshold) to bump level 1 -> 2
    
    bumpdays 1       # minimum days at each level
    
    bumpmult 4       # threshold = bumpsize * bumpmult^(level-1)
    
    etimeout 600     # number of seconds per filesystem for estimates.
    
    dtimeout 1800    # number of idle seconds before a dump is aborted.
    
    ctimeout 30      # maximum number of seconds that amcheck waits
                     # for each client host
    
    tapebufs 20
    
    tapedev "tape:/dev/rmt/0"  #myown
    
    runtapes 1         # number of tapes to be used in a single run of amdump
    
    tapetype LTO2
    
    labelstr "^New-[0-9][0-9]*$" # label constraint regex: all tapes must match
    
    holdingdisk hd1 {
        comment "main holding disk"
        directory "/vm/amanda/amandahold/new" # where the holding disk is
    }
    
    reserve 0
    
    autoflush yes
    
    columnspec "HostName=0:12,Disk=1:12,Level=1:1,OrigKB=1:7,OutKB=1:7,DumpTime=1:6,DumpRate=1:7,TapeTime=1:6,TapeRate=1:7,Compress=1:0"
    
    infofile "/var/log/amanda/new/curinfo" # database DIRECTORY
    
    logdir   "/var/log/amanda/new"         # log directory
    
    indexdir "/var/log/amanda/new/index" # index directory
    
    #generatred by amtapetype -t LTO2 -e 200g -f /dev/rmt/0 on server
    define tapetype LTO2 {
        comment "just produced by tapetype prog (hardware compression on)"
        length 180736 mbytes
        filemark 0 kbytes
        speed 18667 kps
    }
    
    #myown:
    define dumptype comp-tar {
        program "GNUTAR"
        #exclude file "/usr/local/var/amanda/gnutar-lists"
        compress fast
        index yes
        record no           # Important! avoid interfering with production runs
        auth "bsdtcp"
        strategy noinc
    }
    
    #dell interface 1Gb eth (192.168.4.4)
    define interface bnx1 {
            comment "1 Gbps ethernet"
            use 9000000 kbps
    }
    and my .amandahosts file:

    Code:
    amanda$ cat .amandahosts
    myserver.mycompany.com   amanda  amdump
    
    myserver.mycompany.com root amindexd amidxtaped amandaidx
    what else should I do?

    regards, Michał
    Last edited by michas; September 29th, 2008 at 04:34 AM.

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

    Default

    Did amandad get executed? If so, post the amandad.*.debug file. If no, check system log for error to execute amandad

  3. #3
    Join Date
    Sep 2008
    Posts
    32

    Default

    ok, I see that amandad did not execute... here is /tmp/amanda/client/new/amrecover.20080929143442.debug file:

    Code:
    1222691682.302848: amrecover: pid 20275 ruid 0 euid 0: start at Mon Sep 29 14:34:42 2008
    1222691682.303301: amrecover: warning: errors processing config file "/usr/local/etc/amanda/amanda-client.conf" (non-fatal)
    1222691682.303461: amrecover: warning: errors processing config file "/usr/local/etc/amanda/new/amanda-client.conf" (non-fatal)
    1222691682.303657: amrecover: pid 20275 ruid 0 euid 0: rename at Mon Sep 29 14:34:42 2008
    1222691682.303740: amrecover: security_getdriver(name=bsd) returns fef22620
    1222691682.303804: amrecover: security_handleinit(handle=807d580, driver=fef22620 (BSD))
    1222691682.305033: amrecover: bind_portrange2: Try  port 661: Available - Success
    1222691682.305104: amrecover: dgram_bind: socket 4 bound to 0.0.0.0.661
    1222691682.305342: amrecover: dgram_send_addr(addr=807d5a0, dgram=fef27f44)
    1222691682.305354: amrecover: (sockaddr_in *)807d5a0 = { 2, 10080, 192.168.4.4 }
    1222691682.305362: amrecover: dgram_send_addr: fef27f44->socket = 4
    1222691692.311969: amrecover: dgram_send_addr(addr=807d5a0, dgram=fef27f44)
    1222691692.311995: amrecover: (sockaddr_in *)807d5a0 = { 2, 10080, 192.168.4.4 }
    1222691692.312003: amrecover: dgram_send_addr: fef27f44->socket = 4
    1222691702.322000: amrecover: dgram_send_addr(addr=807d5a0, dgram=fef27f44)
    1222691702.322027: amrecover: (sockaddr_in *)807d5a0 = { 2, 10080, 192.168.4.4 }
    1222691702.322035: amrecover: dgram_send_addr: fef27f44->socket = 4
    1222691712.331894: amrecover: security_seterror(handle=807d580, driver=fef22620 (BSD) error=timeout waiting for ACK)
    1222691712.331931: amrecover: security_close(handle=807d580, driver=fef22620 (BSD))
    but I don't think this is very useful...
    Last edited by michas; September 29th, 2008 at 04:52 AM.

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

    Default

    amandad should never be run by root, remove your second inetd entry.

    inetd is configure to execute amandad with the bsdtcp auth, but amrecover use the bsd auth
    try: amrecover -oauth=bsdtcp
    or add: auth "bsdtcp"
    to the /etc/amanda/amanda-client.conf file

  5. #5
    Join Date
    Sep 2008
    Posts
    32

    Default

    ok, after I added needed lines to amanda-client.conf file I get:

    Code:
    -bash-3.2# /usr/local/sbin/amrecover new -s myserver -t myserverAMRECOVER Version 2.6.0p2. Contacting server on dell2.lodz ...
    NAK: amindexd: invalid service, add 'amindexd' as argument to amandad
    and my /tmp/amanda/amandad/amandad.20080929145836.debug file:

    Code:
    1222693116.934256: amandad: pid 20621 ruid 5555 euid 5555: start at Mon Sep 29 14:58:36 2008
    1222693116.934729: amandad: warning: errors processing config file "/usr/local/etc/amanda/amanda-client.conf" (non-fatal)
    1222693116.934892: amandad: security_getdriver(name=bsdtcp) returns fef42680
    1222693116.934931: amandad: version 2.6.0p2
    1222693116.934940: amandad:     build: VERSION="Amanda-2.6.0p2"
    1222693116.934947: amandad:            BUILT_DATE="Mon Sep 8 11:10:15 MEST 2008"
    1222693116.934953: amandad:            BUILT_MACH="i386-pc-solaris2.11" BUILT_REV="1267"
    1222693116.934960: amandad:            BUILT_BRANCH="amanda-260" CC="/usr/sfw/bin/gcc"
    1222693116.934966: amandad:     paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
    1222693116.934973: amandad:            libexecdir="/usr/local/libexec"
    1222693116.934979: amandad:            amlibexecdir="/usr/local/libexec/amanda"
    1222693116.934985: amandad:            mandir="/usr/local/share/man" AMANDA_TMPDIR="/tmp/amanda"
    1222693116.934992: amandad:            AMANDA_DBGDIR="/tmp/amanda"
    1222693116.934998: amandad:            CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/"
    1222693116.935005: amandad:            RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump"
    1222693116.935011: amandad:            RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF
    1222693116.935017: amandad:            XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
    1222693116.935024: amandad:            SAMBA_CLIENT="/opt/csw/bin/smbclient"
    1222693116.935030: amandad:            GNUTAR="/usr/bin/gtar" COMPRESS_PATH="/usr/bin/gzip"
    1222693116.935037: amandad:            UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lpr"
    1222693116.935043: amandad:            MAILER="/usr/bin/mailx"
    1222693116.935049: amandad:            listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
    1222693116.935056: amandad:     defs:  DEFAULT_SERVER="myserver.mycompany.com" DEFAULT_CONFIG="DailySet1"
    1222693116.935062: amandad:            DEFAULT_TAPE_SERVER="myserver.mycompany.com" DEFAULT_TAPE_DEVICE=""
    1222693116.935069: amandad:            HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM LOCKING=**NONE**
    1222693116.935075: amandad:            SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
    1222693116.935083: amandad:            CLIENT_LOGIN="amanda" CHECK_USERID HAVE_GZIP
    1222693116.935090: amandad:            COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
    1222693116.935096: amandad:            COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
    1222693116.936162: amandad: security_handleinit(handle=806f6b0, driver=fef42680 (BSDTCP))
    1222693116.936202: amandad: security_streaminit(stream=8071218, driver=fef42680 (BSDTCP))
    1222693116.936383: amandad: accept recv REQ pkt:
    <<<<<
    SERVICE amindexd
    OPTIONS features=ffffffff9ffeffffffff00;auth=bsdtcp;
    >>>>>
    1222693116.936401: amandad: amindexd: invalid service
    1222693116.936418: amandad: sending NAK pkt:
    <<<<<
    ERROR amindexd: invalid service, add 'amindexd' as argument to amandad
    >>>>>
    1222693116.936458: amandad: security_close(handle=806f6b0, driver=fef42680 (BSDTCP))
    1222693116.936470: amandad: security_stream_close(8071218)
    1222693116.936874: amandad: pid 20621 finish time Mon Sep 29 14:58:36 2008
    I can see there's some progress... now what?

    regards, Michał

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

    Default

    Quote Originally Posted by michas View Post
    ok, after I added needed lines to amanda-client.conf file I get:

    Code:
    -bash-3.2# /usr/local/sbin/amrecover new -s myserver -t myserver
    AMRECOVER Version 2.6.0p2. Contacting server on dell2.lodz ...
    NAK: amindexd: invalid service, add 'amindexd' as argument to amandad
    That's strange as your inetd config already have amindexd as argument to amandad
    Did you restarted inetd after you updated the file?

  7. #7
    Join Date
    Sep 2008
    Posts
    32

    Default

    yes, that's what confuses me too... I restarted inet few times... still the same error. Maybe I should put there full path to amindexd?

    regards, Michał

  8. #8
    Join Date
    Sep 2008
    Posts
    32

    Default

    full path doesn't work...

  9. #9
    Join Date
    Sep 2008
    Posts
    32

    Default

    it's me again, still have the same problem... here's my /tmp/amanda/amandad/amandad.20081001085111.debug file:

    Code:
    1222843871.609889: amandad: pid 8479 ruid 5555 euid 5555: start at Wed Oct  1 08:51:11 2008
    1222843871.610341: amandad: warning: errors processing config file "/usr/local/etc/amanda/amanda-client.conf" (non-fatal)
    1222843871.610502: amandad: security_getdriver(name=bsdtcp) returns fef42680
    1222843871.610541: amandad: version 2.6.0p2
    1222843871.610550: amandad:     build: VERSION="Amanda-2.6.0p2"
    1222843871.610556: amandad:            BUILT_DATE="Mon Sep 8 11:10:15 MEST 2008"
    1222843871.610563: amandad:            BUILT_MACH="i386-pc-solaris2.11" BUILT_REV="1267"
    1222843871.610569: amandad:            BUILT_BRANCH="amanda-260" CC="/usr/sfw/bin/gcc"
    1222843871.610575: amandad:     paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
    1222843871.610582: amandad:            libexecdir="/usr/local/libexec"
    1222843871.610588: amandad:            amlibexecdir="/usr/local/libexec/amanda"
    1222843871.610595: amandad:            mandir="/usr/local/share/man" AMANDA_TMPDIR="/tmp/amanda"
    1222843871.610601: amandad:            AMANDA_DBGDIR="/tmp/amanda"
    1222843871.610607: amandad:            CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/"
    1222843871.610614: amandad:            RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump"
    1222843871.610620: amandad:            RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF
    1222843871.610626: amandad:            XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
    1222843871.610633: amandad:            SAMBA_CLIENT="/opt/csw/bin/smbclient"
    1222843871.610639: amandad:            GNUTAR="/usr/bin/gtar" COMPRESS_PATH="/usr/bin/gzip"
    1222843871.610645: amandad:            UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lpr"
    1222843871.610652: amandad:            MAILER="/usr/bin/mailx"
    1222843871.610658: amandad:            listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
    1222843871.610665: amandad:     defs:  DEFAULT_SERVER="myserver.mycompany.com" DEFAULT_CONFIG="DailySet1"
    1222843871.610671: amandad:            DEFAULT_TAPE_SERVER="myserver.mycompany.com" DEFAULT_TAPE_DEVICE=""
    1222843871.610678: amandad:            HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM LOCKING=**NONE**
    1222843871.610684: amandad:            SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
    1222843871.610692: amandad:            CLIENT_LOGIN="amanda" CHECK_USERID HAVE_GZIP
    1222843871.610699: amandad:            COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
    1222843871.610705: amandad:            COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
    1222843871.611721: amandad: security_handleinit(handle=806f6b0, driver=fef42680 (BSDTCP))
    1222843871.611759: amandad: security_streaminit(stream=8071218, driver=fef42680 (BSDTCP))
    1222843871.611948: amandad: accept recv REQ pkt:
    <<<<<
    SERVICE amindexd
    OPTIONS features=ffffffff9ffeffffffff00;auth=bsdtcp;
    >>>>>
    1222843871.611967: amandad: amindexd: invalid service
    1222843871.611984: amandad: sending NAK pkt:
    <<<<<
    ERROR amindexd: invalid service, add 'amindexd' as argument to amandad
    >>>>>
    1222843871.612021: amandad: security_close(handle=806f6b0, driver=fef42680 (BSDTCP))
    1222843871.612034: amandad: security_stream_close(8071218)
    1222843871.612585: amandad: pid 8479 finish time Wed Oct  1 08:51:11 2008

    can anybody tell me, what can I do with this line: "ERROR amindexd: invalid service, add 'amindexd' as argument to amandad" from the file above? amindexd is added as an argument to amandad in inetd.conf file... I don't know what to do with this...

    regards, Michał

  10. #10
    Join Date
    Sep 2008
    Posts
    32

    Default

    ok, I finally solved the problem. the cause was that solaris is managing services with its own manager, even the services defined in inetd.conf, these services entries are transformed to xml files (/var/svc/manifest) which are the used. Even if I change the inetd.conf entries these changes are NOT refreshed in these xml files, even entries that are commented out are NOT refreshed and appropriate xml files still exists and these services deleted in inetd.conf are still running... You have to stop them manually using this svcadm service manager and delete these xml files manually. Then You can add new entries in inetd.conf and refresh services (map them to the xml files). This is a bit weird, sounds like a bug... but that's it :) thanks for help anyway,

    regards,
    Michał

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
  •