Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: PROBLEM: Debian Amanda 2.5.1p1 to Windows client = not allowed to execute noop

  1. #11


    I tried that. I get the same message on the server as before.

  2. #12
    Join Date
    Oct 2005
    Bay Area, CA


    Just to make sure, the .amandahosts file that needs to be edited is on the Winows client.
    .amandahosts file : C:\Cygwin\var\lib\amanda\.amandahosts

  3. #13


    That's correct.

  4. #14


    Anyone have an answer?

  5. #15
    Join Date
    Oct 2005


    Quote Originally Posted by JohnWheaton View Post
    I amalso getting this event logged by Windows:
    Application popup: noop.exe - Unable To Locate DLL : The dynamic link library cygwin1.dll could not be found in the specified path C:\cygwin\lib\amanda;.;C:\WINNT\system32;C:\WINNT\ system;C:\WINNT;C:\WINNT\system32;C:\WINNT;C:\WINN T\System32\Wbem;F:\oracle\product\10.2.0\db_1\bin; ;C:\PROGRA~1\CA\SHARED~1\SCANEN~1.

    Please check if cygwin1.dll is installed on the machine.


  6. #16


    It is. I get the same message. (See above. I already answered this question.)

  7. #17



    All of the operations are making on Windows host(bash have to work under amandabackup account under cygwin,the easist way to do that is to launch Start - Programs - Amanda - Amanda Maintenance Shell)

    1). Make shure that you have right content of .amandahosts
    Amanda> more ~/.amandahosts operator amdump
    Where is a unix tape server and operator is an amanda user on that server.

    2). Check rights on the .amandahosts file
    I have following:
    Amanda> ls -al ~
    total 92
    drwxrwxr-x+ 3 Administrator Administrators 0 Mar 18 20:10 ..
    -rwx------ 1 amandabackup Administrators 42 Mar 19 13:06 .amandahosts
    -rwx------ 1 amandabackup None 93 Mar 18 20:28 .amandahosts.orig
    -rwxr-x--- 1 Administrators Backup Operators 803 Jun 6 2007 .amoldrecoverr

    -rwxr-x--- 1 Administrators Backup Operators 783 Jun 6 2007 .amrecoverrc
    -rwxr-x--- 1 Administrator Backup Operators 300 Mar 18 20:11 .bashrc
    -rw-r--r-- 1 Administrators Backup Operators 2899 Jun 6 2007

    -rwxr-x--- 1 Administrators Backup Operators 1208 Jun 6 2007 amkeyswap
    -rwxr-x--- 1 Administrators Backup Operators 766 Jun 6 2007 amsh
    drwxrwx---+ 2 Administrators Backup Operators 0 Mar 18 20:10 gnutar-lists
    -rw-r--r-- 1 Administrators Backup Operators 13661 Jun 6 2007 manifest
    -rwxr-xr-x 1 Administrators Backup Operators 33907 Jun 6 2007
    -rwxr-xr-x 1 Administrators Backup Operators 21652 Jun 6 2007 restore.ico
    -rwxr-xr-x 1 Administrators Backup Operators 2074 Jun 6 2007 setup_logo.jpg
    -rwxr-xr-x 1 Administrators Backup Operators 3516 Jun 6 2007

    3). Cause bsdtcp authentication(which suggested by default!) doesn't work for me on windows with Amanda 2.5.1p1(AmandaBackupClient-2-5-2p1.msi)
    I've changed /etc/inetd.conf to the following:
    Amanda> more /etc/inetd.conf
    # Amanda backup service.

    #amanda stream tcp nowait amandabackup /usr/lib/amanda/amandad.exe amandad -auth=bsdtcp amdump
    #amanda dgram udp wait System /usr/local/libexec/amandad amandad
    amanda dgram udp wait amandabackup /usr/lib/amanda/amandad.exe amandad -auth=bsd amdump

    Don't forget to restart inetd service after

    4). check it!(`amcheck your_config` on the tape server)

    I don't know what was exactly wrong...(it may be spaces, tabs, CR/LF(if you've edited that files in windows before),new line character in the end of configs,
    wrong owner or file permissions... who knows? I haven't time to find the exact reason of the problem.
    Yes, win-amanda is a strange fruit) But after all it works well

Posting Permissions

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