Re: Permissions, configuration, and errors, oh my!
On Tuesday 23 July 2002 12:10, Dave Belfer-Shevett wrote: >Hiya folks, me again. > >I've made huge strides in getting amanda set up on 'tub', our > hinky cool Solaris box that is driving the Overland tape changers > (mmm. AIT-3. Nothing like 5+terabytes of storage available) > >I'm running into some pesky permission and configuration issues > though. I'm going to put aside the fact that I can't get the tape > changer going right now... getting one dump running to one tape > will be a great start, I'll fiddle with the changer later. > >I have .amandahosts set up right, and amcheck now runs with the > following messages. I only have one entry in the disklist file, > and that's for 'tub's local root partition... > >[operator@tub]:~$ amcheck tub >Amanda Tape Server Host Check >- >Holding disk /dumps: 69886570 KB disk space available, that's > plenty amcheck-server: slot 1: date 20020723 label qbn-backup01 > (active tape) amcheck-server: slot 2: slot 2 is empty >amcheck-server: slot 3: slot 3 is empty >amcheck-server: slot 4: slot 4 is empty >amcheck-server: slot 0: slot 0 is empty >ERROR: new tape not found in rack > (expecting a new tape) >NOTE: skipping tape-writable test >NOTE: info dir /usr/adm/amanda/tub/curinfo/tub/_dev_dsk_c0t0d0s1: > does not exist >Server check took 81.639 seconds > >Amanda Backup Client Hosts Check > >ERROR: tub: [could not access /dev/rdsk/c0t0d0s1 > (/dev/dsk/c0t0d0s1): Permission denied] >ERROR: tub: [can not read/write /etc/dumpdates: Permission denied] >Client check: 1 host checked in 0.088 seconds, 2 problems found > >(brought to you by Amanda 2.4.2p2) > >Question: appartently amanda is simply trying to run 'dump', but > can't because it doesn't have root access. Well duh, its logging > in as 'operator'. Is there some setuid stuff i'm missing > somewhere, so that the amanda app can actually run dump and > updated /etc/dumpdates? > >Second - the message is saying there's a labelled tape in the > drive (qbn-backup01) which I created with 'amlabel'. But it > seems to think that's not a writable tape, its expecting a new > one. Can I tell amanda "no, that's your tape. Go toss data on > it!" or am I misunderstanding how tape labelling / allocation > work? Has it written data to that tape previously? In which case it will not re-write to that tape until 'tapecycle' other tapes have been used in order. And it sounds like you have all sorts of perms problems. These all go away if the correct build order is done, to wit: unpack amanda, then as root, chown -R amanda:disk(or whatever you have set for amanda's username and group membership) name_of_unpacked_dir. Become amanda, and cd to that directory and do whatever steps you normally do to build amanda. I use a script with all the options to run ./configure as then its not up to me to remember all that gritty stuff from build to build. That script I use here looks like this: #!/bin/sh make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld \ --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=192.168.1.3 \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda -- adjust to suit your system of course. While still as user amanda, make it. exit to user root and cd back into this directory, and do the 'make install'. The installer will take care of all the perms if you do it in that order. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
Re: Permissions, configuration, and errors, oh my!
On Tue, Jul 23, 2002 at 12:10:25PM -0400, Dave Belfer-Shevett wrote: > ERROR: tub: [could not access /dev/rdsk/c0t0d0s1 (/dev/dsk/c0t0d0s1): > Permission denied] > ERROR: tub: [can not read/write /etc/dumpdates: Permission denied] > Question: appartently amanda is simply trying to run 'dump', but can't > because it doesn't have root access. Well duh, its logging in as > 'operator'. Is there some setuid stuff i'm missing somewhere, so that the > amanda app can actually run dump and updated /etc/dumpdates? No. The conventional way is to give amanda group read on /dev/rdsk/c0t0d0s1, and group write on /etc/dumpdates, like: % groups amanda amanda : sys % ls -lLg /dev/rdsk/c0t0d0s0 /etc/dumpdates crw-r- 1 root sys 32, 0 Aug 28 2000 /dev/rdsk/c0t0d0s0 -rw-rw-r-- 1 root sys 1440 Jul 23 03:42 /etc/dumpdates > amcheck-server: slot 1: date 20020723 label qbn-backup01 (active tape) > Second - the message is saying there's a labelled tape in the drive > (qbn-backup01) which I created with 'amlabel'. But it seems to think > that's not a writable tape, its expecting a new one. Can I tell amanda > "no, that's your tape. Go toss data on it!" or am I misunderstanding how > tape labelling / allocation work? Amanda believes you wrote to that tape, on July 23, 2002. Are you sure you didn't? If you're still just playing and don't care about the data currently on qbn-backup01, you can 'amrmtape tub qbn-backup01' and start over, or 'amlabel -f tub qbn-backup02' it and have amanda pretend it's a new tape. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Permissions, configuration, and errors, oh my!
On Tue, 23 Jul 2002, Frank Smith wrote: > I'll leave the (edited out) dump permission question for others, but your > tape problem is due to Amanda thinking it has already used qbn-backup01. > It may not actually have anything written to it, but if Amdump made a > run then the tape is marked as 'active' and won't be overwritten until it > goes through the rest of your tapecycle. > While you are testing just do an 'amrmtape tub qbn-backup01' and > then you can re-use it. DOH! Yes. That's it. The command I was missing. I didn't see it in a 'see also' anywhere, so it slipped past the radar. Thanks! Now to fix the permissions issue *looks around the lurkers* --.. Dave Belfer-Shevett\ KB1FWR \ www.homeport.org>` [EMAIL PROTECTED] / How much deeper would the ocean be without \ --< sponges. | \__/
Re: Permissions, configuration, and errors, oh my!
--On Tuesday, July 23, 2002 12:10:25 -0400 Dave Belfer-Shevett <[EMAIL PROTECTED]> wrote: > > [operator@tub]:~$ amcheck tub > Amanda Tape Server Host Check > - > Holding disk /dumps: 69886570 KB disk space available, that's plenty > amcheck-server: slot 1: date 20020723 label qbn-backup01 (active tape) > amcheck-server: slot 2: slot 2 is empty > amcheck-server: slot 3: slot 3 is empty > amcheck-server: slot 4: slot 4 is empty > amcheck-server: slot 0: slot 0 is empty > ERROR: new tape not found in rack >(expecting a new tape) > NOTE: skipping tape-writable test > NOTE: info dir /usr/adm/amanda/tub/curinfo/tub/_dev_dsk_c0t0d0s1: does not > exist > Server check took 81.639 seconds > > > Second - the message is saying there's a labelled tape in the drive > (qbn-backup01) which I created with 'amlabel'. But it seems to think > that's not a writable tape, its expecting a new one. Can I tell amanda > "no, that's your tape. Go toss data on it!" or am I misunderstanding how > tape labelling / allocation work? > I'll leave the (edited out) dump permission question for others, but your tape problem is due to Amanda thinking it has already used qbn-backup01. It may not actually have anything written to it, but if Amdump made a run then the tape is marked as 'active' and won't be overwritten until it goes through the rest of your tapecycle. While you are testing just do an 'amrmtape tub qbn-backup01' and then you can re-use it. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Permissions, configuration, and errors, oh my!
I'm not sure about the rest but when I created the amanda user in Solaris'
admintool I set the user type as setuid only - no login and haven't run into
any issues.
Dave Belfer-Shevett wrote:
> Hiya folks, me again.
>
> I've made huge strides in getting amanda set up on 'tub', our hinky cool
> Solaris box that is driving the Overland tape changers (mmm. AIT-3.
> Nothing like 5+terabytes of storage available)
>
> I'm running into some pesky permission and configuration issues though.
> I'm going to put aside the fact that I can't get the tape changer going
> right now... getting one dump running to one tape will be a great start,
> I'll fiddle with the changer later.
>
> I have .amandahosts set up right, and amcheck now runs with the following
> messages. I only have one entry in the disklist file, and that's for
> 'tub's local root partition...
>
> [operator@tub]:~$ amcheck tub
> Amanda Tape Server Host Check
> -
> Holding disk /dumps: 69886570 KB disk space available, that's plenty
> amcheck-server: slot 1: date 20020723 label qbn-backup01 (active tape)
> amcheck-server: slot 2: slot 2 is empty
> amcheck-server: slot 3: slot 3 is empty
> amcheck-server: slot 4: slot 4 is empty
> amcheck-server: slot 0: slot 0 is empty
> ERROR: new tape not found in rack
>(expecting a new tape)
> NOTE: skipping tape-writable test
> NOTE: info dir /usr/adm/amanda/tub/curinfo/tub/_dev_dsk_c0t0d0s1: does not
> exist
> Server check took 81.639 seconds
>
> Amanda Backup Client Hosts Check
>
> ERROR: tub: [could not access /dev/rdsk/c0t0d0s1 (/dev/dsk/c0t0d0s1):
> Permission denied]
> ERROR: tub: [can not read/write /etc/dumpdates: Permission denied]
> Client check: 1 host checked in 0.088 seconds, 2 problems found
>
> (brought to you by Amanda 2.4.2p2)
>
> Question: appartently amanda is simply trying to run 'dump', but can't
> because it doesn't have root access. Well duh, its logging in as
> 'operator'. Is there some setuid stuff i'm missing somewhere, so that the
> amanda app can actually run dump and updated /etc/dumpdates?
>
> Second - the message is saying there's a labelled tape in the drive
> (qbn-backup01) which I created with 'amlabel'. But it seems to think
> that's not a writable tape, its expecting a new one. Can I tell amanda
> "no, that's your tape. Go toss data on it!" or am I misunderstanding how
> tape labelling / allocation work?
>
> Thanks, we're close to moving Huge Tracts o Data!
>
> -d
>
> --..
> Dave Belfer-Shevett\ KB1FWR \
> www.homeport.org>`
> [EMAIL PROTECTED] / If you drink, don't park. Accidents cause \
> --< people. ("Extreme Bumper Stickers") |
>\__/
--
Scott Sanders
Systems Administrator
Concepts Direct, Inc.
2950 Colorful Ave.
Longmont, CO 80504
Permissions, configuration, and errors, oh my!
Hiya folks, me again.
I've made huge strides in getting amanda set up on 'tub', our hinky cool
Solaris box that is driving the Overland tape changers (mmm. AIT-3.
Nothing like 5+terabytes of storage available)
I'm running into some pesky permission and configuration issues though.
I'm going to put aside the fact that I can't get the tape changer going
right now... getting one dump running to one tape will be a great start,
I'll fiddle with the changer later.
I have .amandahosts set up right, and amcheck now runs with the following
messages. I only have one entry in the disklist file, and that's for
'tub's local root partition...
[operator@tub]:~$ amcheck tub
Amanda Tape Server Host Check
-
Holding disk /dumps: 69886570 KB disk space available, that's plenty
amcheck-server: slot 1: date 20020723 label qbn-backup01 (active tape)
amcheck-server: slot 2: slot 2 is empty
amcheck-server: slot 3: slot 3 is empty
amcheck-server: slot 4: slot 4 is empty
amcheck-server: slot 0: slot 0 is empty
ERROR: new tape not found in rack
(expecting a new tape)
NOTE: skipping tape-writable test
NOTE: info dir /usr/adm/amanda/tub/curinfo/tub/_dev_dsk_c0t0d0s1: does not
exist
Server check took 81.639 seconds
Amanda Backup Client Hosts Check
ERROR: tub: [could not access /dev/rdsk/c0t0d0s1 (/dev/dsk/c0t0d0s1):
Permission denied]
ERROR: tub: [can not read/write /etc/dumpdates: Permission denied]
Client check: 1 host checked in 0.088 seconds, 2 problems found
(brought to you by Amanda 2.4.2p2)
Question: appartently amanda is simply trying to run 'dump', but can't
because it doesn't have root access. Well duh, its logging in as
'operator'. Is there some setuid stuff i'm missing somewhere, so that the
amanda app can actually run dump and updated /etc/dumpdates?
Second - the message is saying there's a labelled tape in the drive
(qbn-backup01) which I created with 'amlabel'. But it seems to think
that's not a writable tape, its expecting a new one. Can I tell amanda
"no, that's your tape. Go toss data on it!" or am I misunderstanding how
tape labelling / allocation work?
Thanks, we're close to moving Huge Tracts o Data!
-d
--..
Dave Belfer-Shevett\ KB1FWR \
www.homeport.org>`
[EMAIL PROTECTED] / If you drink, don't park. Accidents cause \
--< people. ("Extreme Bumper Stickers") |
\__/
