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

Thread: problem with amcheck freebsd

  1. #1
    Join Date
    Sep 2008
    Posts
    32

    Default problem with amcheck (check freebsd)

    hi,
    I've installed amanda client on FreeBSD 7 (from source), succesfully configured inetd and server... now I have something I've never seen before with amanda... I have to tell I'm novice with FreeBSD. so, what I do is:

    Code:
    amanda$ amcheck aaa
    Amanda Tape Server Host Check
    -----------------------------
    Holding disk /vm/amanda/amandahold/aaa: 366436864 kB disk space available, using 366436864 kB
    read label `aaa-02', date `20081002151913'.
    Tape with label aaa-02 is still active and cannot be overwriten.
           (expecting a new tape)
    NOTE: host info dir /var/log/amanda/aaa/curinfo/myfreeBSD does not exist
    NOTE: it will be created on the next run.
    NOTE: index dir /var/log/amanda/aaa/index/myfreeBSD does not exist
    NOTE: it will be created on the next run.
    
    Server check took 6.218 seconds
    
    Amanda Backup Client Hosts Check
    --------------------------------
    WARNING: myfreeBSD: selfcheck request failed: EOF on read from myfreeBSD
    Client check: 1 hosts checked in 5.130 seconds.  1 problem found.
    
    (brought to you by Amanda 2.6.0p2)
    Here's inetd config on freeBSD:

    Code:
    amanda stream tcp nowait amandabackup /usr/local/libexec/amanda/amandad  amandad -auth=bsdtcp amdump #amanda
    and You can see that amanda is listening:

    Code:
    [root@myfreeBSD ~]# netstat -a | grep ama
    tcp4       0      0  *.amanda               *.*                    LISTEN
    User and catalogues are configured correctly, I added amandabackup user to the group wheel. The file .amandahosts is correct (it works on other - non freeBSD machines). And here is my /var/log/messages entry:

    Code:
    Oct  6 14:04:22 myfreeBSD inetd[43016]: initgroups(amandabackup,0): Operation not permitted
    Oct  6 14:04:22 myfreeBSD inetd[43016]: amanda: can't setusercontext(..amandabackup..): Operation not permitted
    I tried to ask google for it, but I found nothing connected to amanda.... any help?

    regards, Michał
    Last edited by michas; October 6th, 2008 at 04:40 AM.

  2. #2
    Join Date
    Sep 2008
    Posts
    32

    Default

    oh, and I know about the tape - I should change it, but I'm to lazy to go downstairs with no real need... ;)

  3. #3
    Join Date
    Mar 2007
    Location
    Chicago, IL
    Posts
    688

    Default

    Those are inetd errors, not Amanda .. does the 'amandabackup' user exist on your system?

  4. #4
    Join Date
    May 2008
    Posts
    45

    Default

    If you look at the port, the standard user for backup and that kind of things is operator. And this user has all required rights to run Amanda so I would suggest that you use user=operator, group=operator as your Amanda user.

    Otherwise make sure to create amandabackup in the operator group. I have not tested, so I am not sure if the Amanda user has to be in the system uid range but I do not think so.

    If you choose to use operator, check out the wiki [URL="http://wiki.zmanda.com/index.php/Zmanda_Windows_Client#Running_ZWC_as_some_other_us er"]http://wiki.zmanda.com/index.php/Zmanda_Windows_Client#Running_ZWC_as_some_other_us er[/URL] how you should change the Windows client configuration to allow access from your backups server.

    /glz

  5. #5
    Join Date
    Sep 2008
    Posts
    32

    Default

    yes, amandabackup exists, is added to wheel group. and I tried to run amandad manually, it works (it is running about half a minute and dies, as it should I suppose). I don't have a clue what to do next....

    regards, Michal

  6. #6
    Join Date
    May 2008
    Posts
    45

    Default

    Did you put --with-group=wheel when you did configure?

    /glz

  7. #7
    Join Date
    Sep 2008
    Posts
    32

    Default

    hello,
    yes, I did do that, I remember I made a typo and had an error while compiling, so I had to rerun the configure script with corrected word... but I'm sure it's right now. oh, and I can see the command now in .bash_history file, so it's definitely allright...

    regards, Michał.

  8. #8
    Join Date
    May 2008
    Posts
    45

    Default

    Just to make 100% sure - inetd is running as root?

    > ps -awjx | grep inetd
    root 1897 1 1897 1897 0 Is ?? 0:00.01 /usr/sbin/inetd -wW -C 60

    and you can do sudo or su to amandabackup?

    I can do this to operator:
    > sudo -u operator ls
    ad12.fdisk amanda-2.6.0.patch bedework.build.properties tapesize.txt
    ad16.fdisk amanda-2.6.0.patch.shar patch-amanda work
    ad20.fdisk amtapetype patch-chg-zd-mtx.sh.in

    and for exampel
    > sudo -u operator amadmin lule2 tape
    Password:
    The next Amanda run should go onto tape GLZ03011 or a new tape.
    tape GLZ03012 or a new tape.
    tape GLZ03013 or a new tape.
    tape GLZ03014 or a new tape.
    tape GLZ03015 or a new tape.
    tape GLZ03016 or a new tape.


    Does this work for you with amandambackup user?
    sudo -u amandambackup ls
    sudo -u amandambackup amadmin lule2 tape

    /glz

  9. #9
    Join Date
    Sep 2008
    Posts
    32

    Default

    I will be able to check this on friday, so I can't give You the answer now... :)

  10. #10
    Join Date
    Sep 2008
    Posts
    32

    Default

    Code:
    [root@myFreeBsd ~]# ps -axwj | grep inet
    root    43667     1 43667 43667    0 Is    ??    0:00.02 /usr/sbin/inetd
    and as I mentioned, this host is amanda client only, so I don't have the amadmin command, I do amcheck on another machine...

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
  •