Amanda-Users

Re: problems using amanda with xinetd

2003-06-11 01:57:16
Subject: Re: problems using amanda with xinetd
From: Mike Eldridge <diz AT hiphopanonymous DOT org>
To: Gene Heskett <gene.heskett AT verizon DOT net>
Date: Wed, 11 Jun 2003 00:53:57 -0500
On Tue, Jun 10, 2003 at 05:31:20PM -0400, Gene Heskett wrote:
> >> There has to be some reason the services won't start, so please
> >> post an 'ls -l' of the /usr/local/libexec directory.  Also an 'ls
> >> -l' of the amanda src directory, and a 'cat' of your configuration
> >> script.
> >
> >/usr/local/libexec:
> >
> >-rwxr-xr-x    1 root     disk        53526 May 31 20:29 amandad
> >-rwsr-x---    1 root     disk        43360 May 31 20:29 calcsize
> >-rwsr-x---    1 root     disk        37539 May 31 20:29 killpgrp
> >-rwxr-xr-x    1 root     disk         4855 May 31 20:29 patch-system
> >-rwsr-x---    1 root     disk        34567 May 31 20:29 rundump
> >-rwsr-x---    1 root     disk        35854 May 31 20:29 runtar
> >-rwxr-xr-x    1 root     disk        59150 May 31 20:29 selfcheck
> >-rwxr-xr-x    1 root     disk       115915 May 31 20:29 sendbackup
> >-rwxr-xr-x    1 root     disk        73858 May 31 20:29 sendsize
> >-rwxr-xr-x    1 root     disk        33725 May 31 20:29 versionsuffix
> >
> Okaayy, wrong perms, and where did the rest of it go?

these are the perms that amanda's installation used.  as it works
flawlessly on other machines, i did not attempt to change them.  amandad
*is* executable by the amanda user.  the other utilities are suid.  as
tar is being used (rather than a fs-specific dump utility that accesses
the device), simply being a member of group disk will not suffice to
backup the filesystem.  so i will need to change permissions around.

i will setup permissions to suit the setup, but i highly doubt this is
the source of the problem.

as for "the rest of it", it was never there as i configured using
--without-server.

> Heres mine:
> ----------
> [amanda@coyote DailySet1]$ ls -l /usr/local/libexec
> total 1900
> -rwxr-xr-x    1 amanda   disk        57760 Jun  7 11:23 amandad
> -rw-r--r--    1 amanda   disk          180 Jun  7 11:23 amcat.awk
> -rwxr-xr-x    1 amanda   disk        52563 Jun  7 11:23 amcleanupdisk
> -rwxr-xr-x    1 amanda   disk        59668 Jun  7 11:23 amidxtaped
> -rwxr-xr-x    1 amanda   disk       114258 Jun  7 11:23 amindexd
> -rwxr-xr-x    1 amanda   disk        46638 Jun  7 11:23 amlogroll
> -rw-r--r--    1 amanda   disk        17494 Jun  7 11:23 amplot.awk
> -rw-r--r--    1 amanda   disk         3283 Jun  7 11:23 amplot.g
> -rw-r--r--    1 amanda   disk         3293 Jun  7 11:23 amplot.gp
> -rwxr-xr-x    1 amanda   disk        52927 Jun  7 11:23 amtrmidx
> -rwxr-xr-x    1 amanda   disk        51718 Jun  7 11:23 amtrmlog
> -rwsr-x---    1 root     disk        47398 Jun  7 11:23 calcsize
> -rwxr-xr-x    1 amanda   disk        11069 Jun  7 11:23 chg-chio
> -rwxr-xr-x    1 amanda   disk        10064 Jun  7 11:23 chg-chs
> -rwxr-xr-x    1 amanda   disk         5158 Jun  7 11:23 chg-juke
> -rwxr-xr-x    1 amanda   disk         6765 Jun  7 11:23 chg-manual
> -rwxr-xr-x    1 amanda   disk        13094 Jun  7 11:23 chg-mcutil
> -rwxr-xr-x    1 amanda   disk         5594 Jun  7 11:23 chg-mtx
> -rwxr-xr-x    1 amanda   disk        11960 Jun  7 11:23 chg-multi
> -rwxr-xr-x    1 amanda   disk         1699 Jun  7 11:23 chg-null
> -rwxr-xr-x    1 amanda   disk         4004 Jun  7 11:23 chg-rait
> -rwxr-xr-x    1 amanda   disk         6689 Jun  7 11:23 chg-rth
> -rwxr-xr-x    1 amanda   disk       400412 Jun  7 11:23 chg-scsi
> -rwxr-xr-x    1 amanda   disk        36500 Jun  7 11:23 chg-zd-mtx
> -rwxr-xr-x    1 amanda   disk        97175 Jun  7 11:23 driver
> -rwsr-x---    1 root     disk        90217 Jun  7 11:23 dumper
> -rwsr-x---    1 root     disk        41991 Jun  7 11:23 killpgrp
> -rwxr-xr-x    1 amanda   disk         4846 Jun  7 11:23 patch-system
> -rwsr-x---    1 root     disk        90980 Jun  7 11:23 planner
> -rwsr-x---    1 root     disk        38959 Jun  7 11:23 rundump
> -rwsr-x---    1 root     disk        40270 Jun  7 11:23 runtar
> -rwxr-xr-x    1 amanda   disk        63184 Jun  7 11:23 selfcheck
> -rwxr-xr-x    1 amanda   disk       121096 Jun  7 11:23 sendbackup
> -rwxr-xr-x    1 amanda   disk        79692 Jun  7 11:23 sendsize
> -rwxr-xr-x    1 amanda   disk        93117 Jun  7 11:23 taper
> -rwxr-xr-x    1 amanda   disk        38117 Jun  7 11:23 versionsuffix
> ---------------------------
> you're missing some stuff.
> 
> >~/src/amanda-2.4.4:
> 
> That looks good, all owned by mike, which is alright IF mike 
> is a member of group 'disk' (I think), BUT you are not so
> shown here...

uh, no, i'm not (and will not ever be) a member of group disk.  what
does the source have to do with the binaries?

> I'm gonna snip it since my wordwrap wrecked it anyway.
> [...]
> >
> >/usr/local/etc/amanda/normal/amanda.conf:
> >
> >    # amanda configuration file
> >
> >    # configuration name
> >    org "DailyBackup"
> >
> >    # general options
> >    mailto "diz AT hiphopanonymous DOT org"
> >    dumpuser "amanda"
> >    logdir "/var/log/amanda"
> >    tapelist "/var/lib/amanda/tapelist"
> >
> >    # cycle information
> >    dumpcycle 7
> >    tapecycle 1
> One tape?  You'll need at least dumpcycle + one, and preferably 
> (since there is no runspercycle spec here, the assumption by
> amanda is everyday, so runspercycle=dumpcycle I believe) 2 or
> more 'runspercycle' tapes in the rotation.  Thats at least 14.
> 
> This is so that you have a system full at any time
> as long as the last runspercycle backups are available.

they don't *have* 14 tapes.  i suppose i'll just have to change
dumpcycle to 0 and run it weekly.  i'll convince them to purchase at
*least* one additional tape, if not the 14 needed for the cycle.

> >     filemark 100 kbytes
> >     speed 4 mbps
> >    }
> >
> >    # dump type definition for use in archiving the local machine's
> > drive define dumptype normal-local {
> >     comment "local, normal backup, no software compression"
> >     dumpcycle 7
> strange place for a dumpcycle spec??

it's listed in the amanda documentation.  perhaps i want different
dumpcycles for different machines...

> >     compress none   # never use software compression
> >     holdingdisk no  # this is local, don't use the holding disk
> why not?  Excluse it yes, but do use it.  Amanda will stream to tape
> if you do, but may shoeshine the drive, wasting tape and wear
> and tear on the drive if you don't.

my reasoning, from amanda(8):

    holdingdisk "boolean"
        Default:  yes.   Whether a holding disk should be used for these
        backups or whether they should go  directly  to  tape.  If  the
        holding disk is a portion of another file system that Amanda is
        backing up, that file system should refer  to  a  dumptype with
        holdingdisk  set to no to avoid backing up the holding disk into
        itself.

perhaps someone should make some changes...

[snip]

> When thats done, see if xinetd still has a tummy ache
> when restarted.  I'm betting this will be the dose of
> pepto-bismal it needs.

i fail to see how this will correct my problem as i have 3 other
machines (including the tape server) that work flawlessly under inetd.

however, i will give your pedantic suggestion a try.

-mike

------------------------------------------------------------------------
   /~\  the ascii                         subvert the dominant paradigm
   \ /  ribbon campaign
    X   against html
   / \  email!