Re: Amanda changes bite me again.

[Gene Heskett]

On Thursday, September 30, 2010 12:04:37 pm ad...@geronimoalloys.com did 
opine:

> Will you please take my email off the distibution list.
> 
> ad...@geronimoalloys.com
> bran...@geronimoalloys.com
> *...@geronimoalloys.com
> *...@tejasalloys.com
> 
> 
> Thanks
> 
I do not readily know how to do that, other than you must reply in the 
affirmative to a request sent to your address to complete the un-subscription 
process.  Most mailing lists attach a link to the bottom of every message, 
some have that link in the headers that most folks turn off the viewing of.  
This lists mail server does neither.  so I looked around at amanda.org, and 
found the mailing lists link at:



and follow the instructions there exactly, and which must be done from the 
same address you used when you originally subscribed.

Are you no longer using amanda for your backups?  And why?  Losing a user 
makes us a little sad.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
God isn't dead, he just couldn't find a parking place.

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Wed, Sep 29, 2010 at 1:51 PM, Gene Heskett  wrote:
> Wed Sep 29 14:41:23 2010: amcheck-device: set_current: symlinking 
> /amandatapes/test/data to slot1

And is this link in place on the filesystem now?  What's the
difference between the 14:31 and 14:41 runs of amcheck?

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Gene Heskett]

On Wednesday, September 29, 2010 02:51:47 pm Dustin J. Mitchell did opine:

> On Wed, Sep 29, 2010 at 12:53 PM, Chris Nighswonger
> 
>  wrote:
> > Line 473 should have a double colon rather than a single... ie.
> > Amanda::Debug::debug rather than Amanda::Debug::debug
> 
> Sorry about that, Gene.  You can just edit the file under /usr, rather
> than re-making Amanda, if that's easier.
> 
> Dustin

Mochs Nichs, I didn't know any better so I did it. ;-)
See my other replies for the confusing amcheck-device-debug logs.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"If you lived today as if it were your last, you'd buy up a box of rockets 
and 
fire them all off, wouldn't you?"
-- Garrison Keillor

Re: Amanda changes bite me again.

[Gene Heskett]

On Wednesday, September 29, 2010 02:32:52 pm Chris Nighswonger did opine:

> > amcheck dead in water:
> > [ama...@coyote amanda-3.2.0alpha.svn.3460]$ amcheck Daily
> > Amanda Tape Server Host Check
> > -
> > Holding disk /usr/dumps: 620929024 kB disk space available, using
> > 620417024 kB
> > amcheck-device: syntax error at
> > /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 473, near
> > "Amanda::Debug:"
> > syntax error at /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm
> > line 497, near ")
> >symlink"
> 
> Line 473 should have a double colon rather than a single... ie.
> Amanda::Debug::debug rather than Amanda::Debug::debug
> 
> Kind Regards,
> Chris

Thanks Chris.  Also line 497 needed a semicolon terminator.
the amcheck-device log after the reinstall & an amcheck session:

Wed Sep 29 14:31:47 2010: amcheck-device: pid 20091 ruid 501 euid 501 version 
3.2.0alpha.svn.3460: start at Wed Sep 29 14:31:47 2010
Wed Sep 29 14:31:47 2010: amcheck-device: pid 20091 ruid 501 euid 501 version 
3.2.0alpha.svn.3460: rename at Wed Sep 29 14:31:47 2010
Wed Sep 29 14:31:47 2010: amcheck-device: Amanda::Taper::Scan::traditional 
stage 1: search for oldest reusable volume
Wed Sep 29 14:31:47 2010: amcheck-device: Amanda::Taper::Scan::traditional 
oldest reusable volume is 'Dailys-3'
Wed Sep 29 14:31:47 2010: amcheck-device: Amanda::Taper::Scan::traditional 
stage 1: searching oldest reusable volume 'Dailys-3'
Wed Sep 29 14:31:47 2010: amcheck-device: Amanda::Taper::Scan::traditional 
result: 'Dailys-3' on file:/amandatapes/Dailys/drive0 slot 3, mode 
2
Wed Sep 29 14:31:47 2010: amcheck-device: pid 20091 finish time Wed Sep 29 
14:31:47 2010

Which seems identical to yesterdays run:

Tue Sep 28 19:22:25 2010: amcheck-device: pid 13296 ruid 501 euid 501 version 
3.2.0alpha.svn.3457: start at Tue Sep 28 19:22:25 2010
Tue Sep 28 19:22:25 2010: amcheck-device: pid 13296 ruid 501 euid 501 version 
3.2.0alpha.svn.3457: rename at Tue Sep 28 19:22:25 2010
Tue Sep 28 19:22:25 2010: amcheck-device: Amanda::Taper::Scan::traditional 
stage 1: search for oldest reusable volume
Tue Sep 28 19:22:25 2010: amcheck-device: Amanda::Taper::Scan::traditional 
oldest reusable volume is 'Dailys-2'
Tue Sep 28 19:22:25 2010: amcheck-device: Amanda::Taper::Scan::traditional 
stage 1: searching oldest reusable volume 'Dailys-2'
Tue Sep 28 19:22:25 2010: amcheck-device: Amanda::Taper::Scan::traditional 
result: 'Dailys-2' on file:/amandatapes/Dailys/drive0 slot 2, mode 
2
Tue Sep 28 19:22:25 2010: amcheck-device: pid 13296 finish time Tue Sep 28 
19:22:25 2010

Shouldn't there be additional info in the first one?

Just for grins, the results of an amcheck on the test setup:
Wed Sep 29 14:41:23 2010: amcheck-device: pid 21391 ruid 501 euid 501 version 
3.2.0alpha.svn.3460: start at Wed Sep 29 14:41:23 2010
Wed Sep 29 14:41:23 2010: amcheck-device: pid 21391 ruid 501 euid 501 version 
3.2.0alpha.svn.3460: rename at Wed Sep 29 14:41:23 2010
Wed Sep 29 14:41:23 2010: amcheck-device: Amanda::Taper::Scan::traditional 
stage 1: search for oldest reusable volume
Wed Sep 29 14:41:23 2010: amcheck-device: Amanda::Taper::Scan::traditional no 
oldest reusable volume
Wed Sep 29 14:41:23 2010: amcheck-device: Amanda::Taper::Scan::traditional 
stage 2: scan for any reusable volume
Wed Sep 29 14:41:23 2010: amcheck-device: get_current: /amandatapes/test/data = 
slot1
Wed Sep 29 14:41:23 2010: amcheck-device: set_current: symlinking 
/amandatapes/test/data to slot1
Wed Sep 29 14:41:23 2010: amcheck-device: Amanda::Taper::Scan::traditional 
result: 'test-1' on file:/amandatapes/test/drive0 slot 1, mode 2
Wed Sep 29 14:41:23 2010: amcheck-device: pid 21391 finish time Wed Sep 29 
14:41:23 2010

Same amcheck, dated 3 minutes ago. WT&$...@???

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Kissing a smoker is like licking an ashtray.

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Wed, Sep 29, 2010 at 12:53 PM, Chris Nighswonger
 wrote:
> Line 473 should have a double colon rather than a single... ie.
> Amanda::Debug::debug rather than Amanda::Debug::debug

Sorry about that, Gene.  You can just edit the file under /usr, rather
than re-making Amanda, if that's easier.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Nathan Stratton Treadway]

On Wed, Sep 29, 2010 at 13:40:27 -0400, Gene Heskett wrote:
> On Wednesday, September 29, 2010 01:35:19 pm Dustin J. Mitchell did opine:
> > Can you add some debug prints to Amanda/Changer/disk.pm?
> > 
> > 494 # TODO: locking
> >   Amanda::Debug::debug("set_current: symlinking $curlink to slot$slot")
> > 495 symlink("slot$slot", $curlink);
> > 
> > and
> > 
> > 471 if (-l $curlink) {
> > 472 my $target = readlink($curlink);
> >   Amanda::Debug:debug("get_current: $curlink = $target");
> > 473 if ($target =~ "^slot([0-9]+)/?") {

[...]
> amcheck dead in water:
> [ama...@coyote amanda-3.2.0alpha.svn.3460]$ amcheck Daily
> Amanda Tape Server Host Check
> -
> Holding disk /usr/dumps: 620929024 kB disk space available, using 620417024 
> kB
> amcheck-device: syntax error at 
> /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 473, near 
> "Amanda::Debug:"
> syntax error at /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 
> 497, near ")
> symlink"

There should be a semicolon at the end of the new line that's added
between 494 and 495

Nathan

Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: Amanda changes bite me again.

[Chris Nighswonger]

> amcheck dead in water:
> [ama...@coyote amanda-3.2.0alpha.svn.3460]$ amcheck Daily
> Amanda Tape Server Host Check
> -
> Holding disk /usr/dumps: 620929024 kB disk space available, using 620417024
> kB
> amcheck-device: syntax error at
> /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 473, near
> "Amanda::Debug:"
> syntax error at /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line
> 497, near ")
>    symlink"

Line 473 should have a double colon rather than a single... ie.
Amanda::Debug::debug rather than Amanda::Debug::debug

Kind Regards,
Chris

Re: Amanda changes bite me again.

[Gene Heskett]

On Wednesday, September 29, 2010 01:35:19 pm Dustin J. Mitchell did opine:

> On Wed, Sep 29, 2010 at 11:33 AM, Gene Heskett  
wrote:
> > Note the --with-config=Daily \, but the subdir when running am* Daily
> > is /amandatapes/Dailys,  note the plural.  Is this line even
> > required?
> 
> No, --with-config is largely ignored, and the name of the vtape
> directory need not match the name of the configuration.
> 
> > The test amanda.conf is the Daily/amanda.conf copied to the
> > $configdir/test tree, with all instances of 'Daily' or in the case of
> > vtape paths, Dailys, edited to be 'test' in those strings.  And the
> > test checks are running the code built by the above gh.cf file.
> >  Could this missmatch be a problem with the new code?
> 
> It's certainly possible that there's a bug here - I'm just baffled as
> to what's going on.
> 
> > Now, I do see one item that will need moved to the
> > /usr/local/var/amanda/configname directory, amandates exists as
> > /usr/local/var/amanda/amandates & that will not do for a test run of
> > 'test'.
> > 
> > Humm, that location is in the Makefiles as a default.  So is it
> > definable in the /configdir/amanda,conf?  The man pages for
> > amanda.conf don't mention it.
> > 
> > If this move of amandates can be done by moving it to
> > /usr/local/var/amanda/configname/amandates, I believe this is the last
> > connection that exists between the "Daily" and "test" configs.
> > 
> > Please add that ability to parse /configname/amanda.conf for the
> > location of the amandates file.
> 
> The location for 'amandates' can only be set at configure time.
> However, amandates is rarely, if ever, used, so I don't think that the
> overlap is a problem.
> 
> Can you add some debug prints to Amanda/Changer/disk.pm?
> 
> 494 # TODO: locking
>   Amanda::Debug::debug("set_current: symlinking $curlink to slot$slot")
> 495 symlink("slot$slot", $curlink);
> 
> and
> 
> 471 if (-l $curlink) {
> 472 my $target = readlink($curlink);
>   Amanda::Debug:debug("get_current: $curlink = $target");
> 473 if ($target =~ "^slot([0-9]+)/?") {
> 
> and see what appears in the amcheck-device debug log?
> 
> Dustin

Done, but make did not detect the changes in the disk.pm file, so I had to 
do a make clean etc.

amcheck dead in water:
[ama...@coyote amanda-3.2.0alpha.svn.3460]$ amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /usr/dumps: 620929024 kB disk space available, using 620417024 
kB
amcheck-device: syntax error at 
/usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 473, near 
"Amanda::Debug:"
syntax error at /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 
497, near ")
symlink"
BEGIN not safe after errors--compilation aborted at 
/usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 508.
Compilation failed in require at (eval 14) line 1.
BEGIN failed--compilation aborted at (eval 14) line 1.

Server check took 0.240 seconds

Amanda Backup Client Hosts Check

Client check: 2 hosts checked in 6.304 seconds.  0 problems found.

(brought to you by Amanda 3.2.0alpha.svn.3460)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Just because everything is different doesn't mean anything has changed.
-- Irene Peter

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Wed, Sep 29, 2010 at 11:33 AM, Gene Heskett  wrote:
> Note the --with-config=Daily \, but the subdir when running am* Daily is
> /amandatapes/Dailys,  note the plural.  Is this line even required?

No, --with-config is largely ignored, and the name of the vtape
directory need not match the name of the configuration.

> The test amanda.conf is the Daily/amanda.conf copied to the $configdir/test
> tree, with all instances of 'Daily' or in the case of vtape paths, Dailys,
> edited to be 'test' in those strings.  And the test checks are running the
> code built by the above gh.cf file.  Could this missmatch be a problem with
> the new code?

It's certainly possible that there's a bug here - I'm just baffled as
to what's going on.

> Now, I do see one item that will need moved to the
> /usr/local/var/amanda/configname directory, amandates exists as
> /usr/local/var/amanda/amandates & that will not do for a test run of
> 'test'.
>
> Humm, that location is in the Makefiles as a default.  So is it definable in
> the /configdir/amanda,conf?  The man pages for amanda.conf don't mention it.
>
> If this move of amandates can be done by moving it to
> /usr/local/var/amanda/configname/amandates, I believe this is the last
> connection that exists between the "Daily" and "test" configs.
>
> Please add that ability to parse /configname/amanda.conf for the location of
> the amandates file.

The location for 'amandates' can only be set at configure time.
However, amandates is rarely, if ever, used, so I don't think that the
overlap is a problem.

Can you add some debug prints to Amanda/Changer/disk.pm?

494 # TODO: locking
  Amanda::Debug::debug("set_current: symlinking $curlink to slot$slot")
495 symlink("slot$slot", $curlink);

and

471 if (-l $curlink) {
472 my $target = readlink($curlink);
  Amanda::Debug:debug("get_current: $curlink = $target");
473 if ($target =~ "^slot([0-9]+)/?") {

and see what appears in the amcheck-device debug log?

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Gene Heskett]

On Wednesday, September 29, 2010 11:24:04 am Dustin J. Mitchell did opine:

> On Wed, Sep 29, 2010 at 7:39 AM, Gene Heskett  
wrote:
> > For S&G, I removed the data link from the test setup.  Running amcheck
> > test does restore it.
> > 
> > Removing it from the running setup and running amcheck Daily does not.
> >  But it doesn't seem to effect amdump or amcheck in any way.
> 
> So we need to figure out what's different between these two.  Any ideas?
> 
> Dustin

The only thing that comes to mind is that I have, in the existing build 
from this script:

#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo "!! Warning !!!"
echo "Amanda needs to be configured and built by the"
echo "user amanda, but must be installed by user root."
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-gnu-ld \
--prefix=/usr/local/ \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=coyote \
--with-bsdtcp-security --with-amandahosts \
--with-configdir=/usr/local/etc/amanda \
--with-config=Daily \
--with-gnutar=/bin/tar
echo "sleeping 15 seconds for reading configures warnings"
echo "a make as amanda will continue after..."
sleep 15
make

Note the --with-config=Daily \, but the subdir when running am* Daily is 
/amandatapes/Dailys,  note the plural.  Is this line even required? 

However, the test setup seems to have no problem running correctly when the 
test config and the subdir are test and /amandatapes/test.

The test amanda.conf is the Daily/amanda.conf copied to the $configdir/test 
tree, with all instances of 'Daily' or in the case of vtape paths, Dailys, 
edited to be 'test' in those strings.  And the test checks are running the 
code built by the above gh.cf file.  Could this missmatch be a problem with 
the new code?

I've removed that line from the configure script shown above and it didn't 
fuss.  3460 installing now.  It finishes with a run of amcheck Daily.  If it 
fixes the data pointer I will be quite pleasantly surprised.  No it didn't.

Now, I do see one item that will need moved to the 
/usr/local/var/amanda/configname directory, amandates exists as 
/usr/local/var/amanda/amandates & that will not do for a test run of 
'test'.

Humm, that location is in the Makefiles as a default.  So is it definable in 
the /configdir/amanda,conf?  The man pages for amanda.conf don't mention it.

If this move of amandates can be done by moving it to 
/usr/local/var/amanda/configname/amandates, I believe this is the last 
connection that exists between the "Daily" and "test" configs.

Please add that ability to parse /configname/amanda.conf for the location of 
the amandates file.

Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Death is Nature's way of recycling human beings.

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Wed, Sep 29, 2010 at 7:39 AM, Gene Heskett  wrote:
> For S&G, I removed the data link from the test setup.  Running amcheck test
> does restore it.
>
> Removing it from the running setup and running amcheck Daily does not.  But
> it doesn't seem to effect amdump or amcheck in any way.

So we need to figure out what's different between these two.  Any ideas?

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Gene Heskett]

On Wednesday, September 29, 2010 08:23:54 am Dustin J. Mitchell did opine:

> On Tue, Sep 28, 2010 at 10:19 PM, Gene Heskett  
wrote:
> > Like run a catchup loop of at least 2 runs?  Or just plain "amdump
> > test" by hand and see what falls out for two runs?
> 
> No, no amdump, no amflush.  Just amtape (which worked for your main
> config) and amcheck (which didn't), checking the data link in between.
>  Find the underlying pattern, so we can map that pattern to a
> solution.
> 
> Dustin

For S&G, I removed the data link from the test setup.  Running amcheck test
does restore it.

Removing it from the running setup and running amcheck Daily does not.  But 
it doesn't seem to effect amdump or amcheck in any way.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
What is worth doing is worth the trouble of asking somebody to do.

Re: Amanda changes bite me again.

[Gene Heskett]

On Wednesday, September 29, 2010 12:36:54 am Dustin J. Mitchell did opine:

> On Tue, Sep 28, 2010 at 10:19 PM, Gene Heskett  
wrote:
> > Like run a catchup loop of at least 2 runs?  Or just plain "amdump
> > test" by hand and see what falls out for two runs?
> 
> No, no amdump, no amflush.  Just amtape (which worked for your main
> config) and amcheck (which didn't), checking the data link in between.
>  Find the underlying pattern, so we can map that pattern to a
> solution.
> 
> Dustin

There appears to be tracking, I did 'amtape test slot next' all the way 
around to slot-1 again and everything worked, however all tapes are "new" 
so amcheck is happy with any tape as indicated by its following the data 
link without ever searching for the 'next usable tape'.  Maybe its late, 
but it seems we haven't learned anything.

Now, if I switch configs look at Dailys, I have a data link to slot-5, left 
by an experiment earlier today with amtape, but amcheck says it will be 
using slot-2 in about 3 minutes.  Yup, the first dump written went to 
Dailys-2 according to amstatus.  And the 'data' link is still set to 
slot-5.

Call this canary that sings double bass puzzled.  Nap time, amanda will do 
what amanda does.  If I've got the wrappers fixed, it will work.

And I went to bed w/o sending.  My fixes worked.  Every thing went into 
slot2(Dailys-2). And data still points at slot5,


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
  We're overpaying him, but he's worth it. -Samuel Goldwyn

Re: Amanda changes bite me again.

[Gene Heskett]

On Tuesday, September 28, 2010 11:16:55 pm Dustin J. Mitchell did opine:

> On Tue, Sep 28, 2010 at 9:06 PM, Gene Heskett  
wrote:
> > Anyway, its setup, and awaiting orders Cap'n.  Next?
> 
> Can you replicate any of the failure-to-update-data errors with this
> test config?
> 
> Dustin

Like run a catchup loop of at least 2 runs?  Or just plain "amdump test" by 
hand and see what falls out for two runs?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"... freedom ... is a worship word..."
"It is our worship word too."
-- Cloud William and Kirk, "The Omega Glory", stardate unknown

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Tue, Sep 28, 2010 at 9:06 PM, Gene Heskett  wrote:
> Anyway, its setup, and awaiting orders Cap'n.  Next?

Can you replicate any of the failure-to-update-data errors with this
test config?

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Gene Heskett]

On Tuesday, September 28, 2010 09:42:43 pm Dustin J. Mitchell did opine:

> On Tue, Sep 28, 2010 at 6:26 PM, Gene Heskett  
wrote:
> > I now see a 'data' link to slot 5, I nuked that 2 days ago because
> > nothing was paying an attention to it, and neither amcheck nor amdump
> > was updating it, and the loss causes no errors, none, nada, zip.  My
> > helper script no longer pays any attention to it either.
> 
> That's really weird.  I can't replicate this behavior at all.  Having
> reviewed the code, chg-disk actually looks at what the 'data' symlink
> is pointing to in order to determine the "current" slot.
> 
> In particular, I don't see why amtape would set the symlink, but
> amcheck and amdump would not.  Reasons I can think of off the top of
> my head:
>  - permissions problems
Everything involved is either amanda:amanda or amanda:disk
>  - wrapper scripts?

I only read what amanda sets in those, no writes.

>  - multiple copies of Amanda installed?

Yeah, about the last 30 snapshots, but all the working links are to 3457 
stuff.  I nuked the rest which didn't results in any broken links, and 
anything in those dirs that was not dated the 27th when I installed 3457.

>  - voodoo?

I thought of that, but I'm not very good at that sort of thing. ;-)
 
> Can you set up a smaller config without using your wrapper script and
> with a fresh set of vtapes and a simple DLE (/boot or something like
> that), and see how amtape and amcheck behave?  Don't run amdump..
> 
> Dustin

That took about an hour and a whole bunch of detail edits in the copied 
amanda.conf to /usr/local/etc/amanda/test/amanda.conf, plus some re-writing 
of my mkvtapes-test test script, but here is what I wind up with.
[ama...@coyote GenesAmandaHelper-0.6]$ amtape test show
amtape: scanning all 10 slots in changer:
slot   1: date X  label test-1
slot   2: date X  label test-2
slot   3: date X  label test-3
slot   4: date X  label test-4
slot   5: date X  label test-5
slot   6: date X  label test-6
slot   7: date X  label test-7
slot   8: date X  label test-8
slot   9: date X  label test-9
slot  10: date X  label test-10

and 
[ama...@coyote GenesAmandaHelper-0.6]$ amcheck test
Amanda Tape Server Host Check
-
Holding disk /usr/amandatest: 620937216 kB disk space available, using 
620425216 kB
slot 1: volume 'test-1'
Will write to volume 'test-1' in slot 1.
NOTE: skipping tape-writable test
NOTE: conf info dir /usr/local/var/amanda/test/curinfo does not exist
NOTE: it will be created on the next run.
NOTE: index dir /usr/local/var/amanda/test/index does not exist
NOTE: it will be created on the next run.
Server check took 0.187 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 6.018 seconds.  0 problems found.

(brought to you by Amanda 3.2.0alpha.svn.3457)

[ama...@coyote GenesAmandaHelper-0.6]$ ls -l /amandatapes/test
total 44
lrwxrwxrwx 1 amanda amanda5 2010-09-28 21:40 data -> slot1/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot1/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot10/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot2/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot3/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot4/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot5/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot6/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot7/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot8/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot9/
-rw--- 1 amanda amanda  131 2010-09-28 21:40 state

Now, I suspect I can nuke that 'data' link without bothering a thing, but 
haven't.  My mkvtapes-test script uses it to display the contents of 'data' 
as the individual vtape is created.  There amlabel correctly modifies the 
data link as it labels, so in order for it to order the generated tapelist, 
the for n in 10 9 8 7 6 5 4 3 2 1 reverses the order so it winds up with 
data pointed at slot-1 and the usage pattern is then in 1 2 3 etc order.

I have this setup in parallel, with a separate holding disk, a separate  
/usr/local/var/amanda/test for a database location.  Theoretically I should 
be able to run it without interaction with the normal 'Daily' setup.  
Theoretically, usually Murphy proves he is alive and well.

The one dle disklist:
coyote  /boot   coyote-tar  1   local

And I still don't have a tapedev defined.  What should that be for a vtape 
setup running to /amandatapes/test/slot-* as the vtape?

Anyway, its setup, and awaiting orders Cap'n.  Next?

 

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Prediction is very difficult, especially of the future.
- Niels Bohr

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Tue, Sep 28, 2010 at 6:26 PM, Gene Heskett  wrote:
> I now see a 'data' link to slot 5, I nuked that 2 days ago because nothing
> was paying an attention to it, and neither amcheck nor amdump was updating
> it, and the loss causes no errors, none, nada, zip.  My helper script no
> longer pays any attention to it either.

That's really weird.  I can't replicate this behavior at all.  Having
reviewed the code, chg-disk actually looks at what the 'data' symlink
is pointing to in order to determine the "current" slot.

In particular, I don't see why amtape would set the symlink, but
amcheck and amdump would not.  Reasons I can think of off the top of
my head:
 - permissions problems
 - wrapper scripts?
 - multiple copies of Amanda installed?
 - voodoo?

Can you set up a smaller config without using your wrapper script and
with a fresh set of vtapes and a simple DLE (/boot or something like
that), and see how amtape and amcheck behave?  Don't run amdump..

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Gene Heskett]

On Tuesday, September 28, 2010 07:14:47 pm Dustin J. Mitchell did opine:

> On Sun, Sep 26, 2010 at 6:03 PM, Dustin J. Mitchell  
wrote:
> > That said, the new chg-disk *is* supposed to duplicate the data
> > symlink quirk, so I'll take a look at why it's not doing that.
> 
> And I just verified that this works for me -- it's also tested for by
> the installchecks.
> 
> Can you do an ls -l of your vtape root directory (the one containing
> slot1, slot2, ..), 
[ama...@coyote ~]$ ls -l  /amandatapes/Dailys
total 124
drwxr-x--- 2 amanda disk   4096 2010-09-28 06:16 slot1/
drwxr-x--- 2 amanda disk   4096 2010-09-07 02:48 slot10/
drwxr-x--- 2 amanda disk   4096 2010-09-08 02:56 slot11/
drwxr-x--- 2 amanda disk   4096 2010-09-09 02:48 slot12/
drwxr-x--- 2 amanda disk   4096 2010-09-10 02:57 slot13/
drwxr-x--- 2 amanda disk   4096 2010-09-11 12:30 slot14/
drwxr-x--- 2 amanda disk   4096 2010-09-12 02:54 slot15/
drwxr-x--- 2 amanda disk   4096 2010-09-13 02:45 slot16/
drwxr-x--- 2 amanda disk   4096 2010-09-14 02:56 slot17/
drwxr-x--- 2 amanda disk   4096 2010-09-15 02:49 slot18/
drwxr-x--- 2 amanda disk   4096 2010-09-16 02:57 slot19/
drwxr-x--- 2 amanda disk   4096 2010-09-16 02:58 slot2/
drwxr-x--- 2 amanda disk   4096 2010-09-17 21:18 slot20/
drwxr-x--- 2 amanda disk   4096 2010-09-27 02:49 slot21/
drwxr-x--- 2 amanda disk   4096 2010-09-19 06:22 slot22/
drwxr-x--- 2 amanda disk   4096 2010-09-20 03:13 slot23/
drwxr-x--- 2 amanda disk   4096 2010-09-21 02:51 slot24/
drwxr-x--- 2 amanda disk   4096 2010-09-22 08:35 slot25/
drwxr-x--- 2 amanda disk   4096 2010-09-23 02:39 slot26/
drwxr-x--- 2 amanda disk   4096 2010-09-24 03:15 slot27/
drwxr-x--- 2 amanda disk   4096 2010-09-25 03:01 slot28/
drwxr-x--- 2 amanda disk   4096 2010-09-26 06:34 slot29/
drwxr-x--- 2 amanda disk   4096 2010-08-31 02:34 slot3/
drwxr-x--- 2 amanda disk   4096 2010-09-28 03:24 slot30/
drwxr-x--- 2 amanda disk   4096 2010-09-01 02:25 slot4/
drwxr-x--- 2 amanda disk   4096 2010-09-02 03:00 slot5/
drwxr-x--- 2 amanda disk   4096 2010-09-03 02:49 slot6/
drwxr-x--- 2 amanda disk   4096 2010-09-04 02:54 slot7/
drwxr-x--- 2 amanda disk   4096 2010-09-05 02:47 slot8/
drwxr-x--- 2 amanda disk   4096 2010-09-06 02:58 slot9/
-rw--- 1 amanda amanda  195 2010-09-28 05:20 state

[ama...@coyote ~]$ amtape Daily slot 5
slot   5: time 20100902005009 label Dailys-5
changed to slot 5
[ama...@coyote ~]$ ls -l  /amandatapes/Dailys
total 124
lrwxrwxrwx 1 amanda amanda5 2010-09-28 19:18 data -> slot5/
drwxr-x--- 2 amanda disk   4096 2010-09-28 06:16 slot1/
drwxr-x--- 2 amanda disk   4096 2010-09-07 02:48 slot10/
drwxr-x--- 2 amanda disk   4096 2010-09-08 02:56 slot11/
drwxr-x--- 2 amanda disk   4096 2010-09-09 02:48 slot12/
drwxr-x--- 2 amanda disk   4096 2010-09-10 02:57 slot13/
drwxr-x--- 2 amanda disk   4096 2010-09-11 12:30 slot14/
drwxr-x--- 2 amanda disk   4096 2010-09-12 02:54 slot15/
drwxr-x--- 2 amanda disk   4096 2010-09-13 02:45 slot16/
drwxr-x--- 2 amanda disk   4096 2010-09-14 02:56 slot17/
drwxr-x--- 2 amanda disk   4096 2010-09-15 02:49 slot18/
drwxr-x--- 2 amanda disk   4096 2010-09-16 02:57 slot19/
drwxr-x--- 2 amanda disk   4096 2010-09-16 02:58 slot2/
drwxr-x--- 2 amanda disk   4096 2010-09-17 21:18 slot20/
drwxr-x--- 2 amanda disk   4096 2010-09-27 02:49 slot21/
drwxr-x--- 2 amanda disk   4096 2010-09-19 06:22 slot22/
drwxr-x--- 2 amanda disk   4096 2010-09-20 03:13 slot23/
drwxr-x--- 2 amanda disk   4096 2010-09-21 02:51 slot24/
drwxr-x--- 2 amanda disk   4096 2010-09-22 08:35 slot25/
drwxr-x--- 2 amanda disk   4096 2010-09-23 02:39 slot26/
drwxr-x--- 2 amanda disk   4096 2010-09-24 03:15 slot27/
drwxr-x--- 2 amanda disk   4096 2010-09-25 03:01 slot28/
drwxr-x--- 2 amanda disk   4096 2010-09-26 06:34 slot29/
drwxr-x--- 2 amanda disk   4096 2010-08-31 02:34 slot3/
drwxr-x--- 2 amanda disk   4096 2010-09-28 03:24 slot30/
drwxr-x--- 2 amanda disk   4096 2010-09-01 02:25 slot4/
drwxr-x--- 2 amanda disk   4096 2010-09-02 03:00 slot5/
drwxr-x--- 2 amanda disk   4096 2010-09-03 02:49 slot6/
drwxr-x--- 2 amanda disk   4096 2010-09-04 02:54 slot7/
drwxr-x--- 2 amanda disk   4096 2010-09-05 02:47 slot8/
drwxr-x--- 2 amanda disk   4096 2010-09-06 02:58 slot9/
-rw--- 1 amanda amanda  195 2010-09-28 19:18 state

I now see a 'data' link to slot 5, I nuked that 2 days ago because nothing 
was paying an attention to it, and neither amcheck nor amdump was updating 
it, and the loss causes no errors, none, nada, zip.  My helper script no 
longer pays any attention to it either.

Now, just for S&G:

[ama...@coyote ~]$ amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /usr/dumps: 620818432 kB disk space available, using 620306432 
kB
Searching for label 'Dailys-2':found in slot 2: volume 'Dailys-2'
Will write to volume 'Dailys-2' in slot 2.
NOTE: skipping tape-writable test
Server check took 0.479 seconds

Amanda Backup Client Hosts Check

Client check: 2 hosts checked in 6.654 se

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Sun, Sep 26, 2010 at 6:03 PM, Dustin J. Mitchell  wrote:
> That said, the new chg-disk *is* supposed to duplicate the data
> symlink quirk, so I'll take a look at why it's not doing that.

And I just verified that this works for me -- it's also tested for by
the installchecks.

Can you do an ls -l of your vtape root directory (the one containing
slot1, slot2, ..), then use 'amtape' to switch to a different slot,
and do another ls -l?  Also, what are tpchanger and tapedev set to in
your configuration?

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Gene Heskett]

On Sunday, September 26, 2010 10:26:49 pm Dustin J. Mitchell did opine:

> On Sun, Sep 26, 2010 at 4:34 PM, Gene Heskett  
wrote:
> > Yes I did, but that didn't give me a clue that the 'data' link to
> > whatever had been deprecated and that for cleanliness, I should go
> > around an nuke it.  No mention of it in the ChangeLog, I read it
> > again early this morning from about the middle of July.
> 
> The new changer was added sometime before that.  YOU changed your
> configuration to use it in August.  In retrospect, we should have
> named it something different -- perhaps chg-vfs or the like -- to
> avoid this confusion.  It's a completely reimplemented changer, and
> isn't intended to reproduce every quirk of the old one.
> 
> That said, the new chg-disk *is* supposed to duplicate the data
> symlink quirk, so I'll take a look at why it's not doing that.
> 
> Dustin

I believe I have my stuff fixed for that now, tonight's run will tell that 
tale, and if no one else has been bitten, then I suggest its dead code and 
could, even should, be deleted.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Every country has the government it deserves.
-- Joseph De Maistre

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Sun, Sep 26, 2010 at 4:34 PM, Gene Heskett  wrote:
> Yes I did, but that didn't give me a clue that the 'data' link to whatever
> had been deprecated and that for cleanliness, I should go around an nuke
> it.  No mention of it in the ChangeLog, I read it again early this morning
> from about the middle of July.

The new changer was added sometime before that.  YOU changed your
configuration to use it in August.  In retrospect, we should have
named it something different -- perhaps chg-vfs or the like -- to
avoid this confusion.  It's a completely reimplemented changer, and
isn't intended to reproduce every quirk of the old one.

That said, the new chg-disk *is* supposed to duplicate the data
symlink quirk, so I'll take a look at why it's not doing that.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amanda changes bite me again.

[Gene Heskett]

On Sunday, September 26, 2010 05:23:52 pm Dustin J. Mitchell did opine:

> On Sun, Sep 26, 2010 at 6:05 AM, Gene Heskett  
wrote:
> > At some point in the last roughly a month, amanda stopped using the
> > link named 'data' to point at the correct slot in a vtape directory.
> 
> I think you figured out, in a previous thread, that you switched to
> the new chg-disk around the beginning of August.
> 
Yes I did, but that didn't give me a clue that the 'data' link to whatever 
had been deprecated and that for cleanliness, I should go around an nuke 
it.  No mention of it in the ChangeLog, I read it again early this morning 
from about the middle of July.

> > I have now patched my script for new means of assuring my data files
> > go into the correct subdir of a vtape setup, but it will take a month
> > or so to get my database all in step again.
> > 
> > Is anyone else actually using GenesAmandaHelper-0.6?  I can send you
> > the two scripts that are changed privately, just yelp.
> 
> There's a copy of the tarball on the wiki, so perhaps you can upload a
> new copy?

If I can figure out how to make tar replace those 2 outdated files, that 
would be the best way.  But I need to do an increment of the version too, 
so I may require the user to make a link so the version number can be 
updated just by updating the link, not by my having to edit 20 files that 
reference it.  Stay tuned.

> 
> Dustin


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The greatest disloyalty one can offer to great pioneers is to refuse to
move an inch from where they stood.

Re: Amanda changes bite me again.

[Dustin J. Mitchell]

On Sun, Sep 26, 2010 at 6:05 AM, Gene Heskett  wrote:
> At some point in the last roughly a month, amanda stopped using the link
> named 'data' to point at the correct slot in a vtape directory.

I think you figured out, in a previous thread, that you switched to
the new chg-disk around the beginning of August.

> I have now patched my script for new means of assuring my data files go into
> the correct subdir of a vtape setup, but it will take a month or so to get
> my database all in step again.
>
> Is anyone else actually using GenesAmandaHelper-0.6?  I can send you the
> two scripts that are changed privately, just yelp.

There's a copy of the tarball on the wiki, so perhaps you can upload a new copy?

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Amanda changes bite me again.

[Gene Heskett]

Greetings;

At some point in the last roughly a month, amanda stopped using the link 
named 'data' to point at the correct slot in a vtape directory.

I have now patched my script for new means of assuring my data files go into 
the correct subdir of a vtape setup, but it will take a month or so to get 
my database all in step again.

Is anyone else actually using GenesAmandaHelper-0.6?  I can send you the 
two scripts that are changed privately, just yelp.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Mathematics is the only science where one never knows what 
one is talking about nor whether what is said is true.
-- Russell

RE: Me again, still getting WARNING: host: selfcheck request time d out. Host down?

[Frank Smith]

You can forget about .amandahosts for now, it's not getting that
far.  If it were an .amandahosts problem the error would be 
similar to [warning, access as backup not allowed from amanda@yourhost].
   You seem to be having a connection problem.  Check the following:
Is there anything in /tmp/amanda?
Can your amanda user create /tmp/amanda?
Is the line for amanda in /etc/services is correct
Is the line for amanda in inetd.conf correct (if running inetd) or do
you have a correct amanda file in xinetd.d (if running xinetd).
Did you restart (x)inetd (some systems seem to need a stop/start instead
of just a signal)?
Can you run the command line specified in (x)inetd as your amanda user
without error (it should sit and do nothing until it times out or you
type something)?
Do you have iptables, hosts.allow/deny, or something else installed
that might prevent packets getting to/from amandad?
Can you see requests to and from the amandad port using snoop/tcpdump
or whatever packet sniffing tool you have?

Frank

--On Wednesday, May 22, 2002 13:40:28 -0400 Cory Visi <[EMAIL PROTECTED]> wrote:

> 
> As stated in my email, my client and server are the same machine.
> Here are the permissions on .amandahosts:
> 
> -rw---1 backup   disk  174 May 22 13:14
> /root/amanda-data/.amandahosts
> 
> Adding root entries, like this to .amandahosts:
> 
> 10.1.0.2   backup
> 10.1.0.3   backup
> server02.ctbackup
> server01.ctbackup
> broadcast backup
> 10.1.0.2   root
> 10.1.0.3   root
> server02.ctroot
> server01.ctroot
> broadcast root
> 
> did not change any behavior. The debug/log output is identical.
> amcheck still returns:
> 
> WARNING: server02.ct: selfcheck request timed out.  Host down?
> Client check: 1 host checked in 30.036 seconds, 1 problem found
> 
> Thank you,
> Cory Visi
> 
> 
> 
>  
>  
> "Martinez, Michael - 
>  
> CSREES/ISTM"  To: 'Cory Visi' 
><[EMAIL PROTECTED]>,
> <[EMAIL PROTECTED][EMAIL PROTECTED]
>  
>     eusda.gov>cc:
>  
>   Subject: RE: Me again, still 
>getting 
> 05/22/2002 12:29 PM   WARNING: host: selfcheck request 
>time d out. 
>   Host down? 
>  
>  
>  
> 
> 
> 
> 
> You're .amandahosts on your tape server needs to include a line for "root"
> for all your tape clients (including itself) ; and .amandahosts on your
> clients needs to be chmod 400
> 
> -Original Message-
> From: Cory Visi [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 22, 2002 11:36 AM
> To: [EMAIL PROTECTED]
> Subject: Me again, still getting WARNING: host: selfcheck request timed
> out. Host down?
> 
> 
> Ok, I have looked into my issues further. Many replies on the list have
> helped me, although I am still having problems and I do not understand what
> Amanda is doing.
> 
> Firstly, this error:
> 
> amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Invalid argument
> 
> Is clearly not indicative of an error. Amanda uses broadcasts to find
> clients/servers regardless of the configuration. Some people get this error
> but have a perfectly working system.
> 
> This error, however:
> 
> Amanda Backup Client Hosts Check
> 
> WARNING: server02.ct: selfcheck request timed out.  Host down?
> Client check: 1 host checked in 30.028 seconds, 1 problem found
> 
> IS indicative of a problem.
> So, starting from scratch I will explain all the details of my setup:
> 
> I am using Amanda 2.4.2p2 on Linux 2.4.13 with glibc 2.2.2 compiled by
> myself.
> I am running amandad, amindexd, amidxtaped from xinetd. All these protocols
> are listed in my /etc/services.
> Currently, I am only trying to backup the data on the same machine as the
> server, so the server and client are the _same machine_. I am using the
> eth0 interface IPs to communicate, although, clearly the packets will go
> through the loopback. The local firewall is configured to _allow all
> packets_ through on the loopback and the eth0 interface (since it's local
> only).
> 
> The following are relevant files concern

RE: Me again, still getting WARNING: host: selfcheck request time d out. Hostdown?

[Cory Visi]

As stated in my email, my client and server are the same machine.
Here are the permissions on .amandahosts:

-rw---1 backup   disk  174 May 22 13:14
/root/amanda-data/.amandahosts

Adding root entries, like this to .amandahosts:

10.1.0.2   backup
10.1.0.3   backup
server02.ctbackup
server01.ctbackup
broadcast backup
10.1.0.2   root
10.1.0.3   root
server02.ctroot
server01.ctroot
broadcast root

did not change any behavior. The debug/log output is identical.
amcheck still returns:

WARNING: server02.ct: selfcheck request timed out.  Host down?
Client check: 1 host checked in 30.036 seconds, 1 problem found

Thank you,
Cory Visi



   

"Martinez, Michael -   

CSREES/ISTM"  To: 'Cory Visi' 
<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED][EMAIL PROTECTED]  

eusda.gov>cc:  

          Subject: RE: Me again, still 
getting 
05/22/2002 12:29 PM   WARNING: host: selfcheck request 
time d out. 
  Host down?   

   





You're .amandahosts on your tape server needs to include a line for "root"
for all your tape clients (including itself) ; and .amandahosts on your
clients needs to be chmod 400

-Original Message-
From: Cory Visi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 22, 2002 11:36 AM
To: [EMAIL PROTECTED]
Subject: Me again, still getting WARNING: host: selfcheck request timed
out. Host down?


Ok, I have looked into my issues further. Many replies on the list have
helped me, although I am still having problems and I do not understand what
Amanda is doing.

Firstly, this error:

amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Invalid argument

Is clearly not indicative of an error. Amanda uses broadcasts to find
clients/servers regardless of the configuration. Some people get this error
but have a perfectly working system.

This error, however:

Amanda Backup Client Hosts Check

WARNING: server02.ct: selfcheck request timed out.  Host down?
Client check: 1 host checked in 30.028 seconds, 1 problem found

IS indicative of a problem.
So, starting from scratch I will explain all the details of my setup:

I am using Amanda 2.4.2p2 on Linux 2.4.13 with glibc 2.2.2 compiled by
myself.
I am running amandad, amindexd, amidxtaped from xinetd. All these protocols
are listed in my /etc/services.
Currently, I am only trying to backup the data on the same machine as the
server, so the server and client are the _same machine_. I am using the
eth0 interface IPs to communicate, although, clearly the packets will go
through the loopback. The local firewall is configured to _allow all
packets_ through on the loopback and the eth0 interface (since it's local
only).

The following are relevant files concerning my setup. Some of my setup may
seem redundant and superfluous, however, in my efforts to make things work,
I have tried a number of things.

/etc/passwd entry for amanda user:
backup:x:417:6:Amanda Backup:/root/amanda-data:/bin/bash

/root/amanda-data/.amandahosts:
10.1.0.3   backup
server02.ctbackup
broadcast backup

/etc/hosts:
127.0.0.1 localhost.localdomain   localhost
10.1.0.3   server02.ct.internaldomain.com   server02.ct
0.0.0.0broadcast broadcast

some of amanda.conf:

dumpuser "backup"
inparallel 4
netusage  51200 Kbps
dumpcycle 3 weeks
runspercycle 15
tapecycle 20 tapes
runtapes 1
tpchanger "chg-manual"
tapedev "/dev/nst0"
changerfile "/root/amanda-data/changer-status"
changerdev "/dev/null"
tapetype DAT
infofile "/root/amanda-data/daily"
logdir   "/var/log/amanda/daily"
indexdir "/root/amanda-data/daily"
tapelist "/root/amanda-data/daily/tapelist"

define tapetype DAT {
comment "Archive Python 04687-XXX"
length 4000 mbytes
filemark 100 kbytes
speed 800 kbytes
}

disklist:
server02.ct sda1comp-root
server02.ct sda2comp-user
server02.ct sdb1comp-user

xinetd entries:

service amanda
{
 disable= no
 bind   = 10.1.0.3
 log_on_success += USERID
 log_on_failure += USERID
 socket_type = dgram
 protocol   = udp
 wait   = yes
 user   = 

RE: Me again, still getting WARNING: host: selfcheck request timed out. Host down?

[Martinez, Michael - CSREES/ISTM]

You're .amandahosts on your tape server needs to include a line for "root"
for all your tape clients (including itself) ; and .amandahosts on your
clients needs to be chmod 400

-Original Message-
From: Cory Visi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 22, 2002 11:36 AM
To: [EMAIL PROTECTED]
Subject: Me again, still getting WARNING: host: selfcheck request timed
out. Host down?


Ok, I have looked into my issues further. Many replies on the list have
helped me, although I am still having problems and I do not understand what
Amanda is doing.

Firstly, this error:

amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Invalid argument

Is clearly not indicative of an error. Amanda uses broadcasts to find
clients/servers regardless of the configuration. Some people get this error
but have a perfectly working system.

This error, however:

Amanda Backup Client Hosts Check

WARNING: server02.ct: selfcheck request timed out.  Host down?
Client check: 1 host checked in 30.028 seconds, 1 problem found

IS indicative of a problem.
So, starting from scratch I will explain all the details of my setup:

I am using Amanda 2.4.2p2 on Linux 2.4.13 with glibc 2.2.2 compiled by
myself.
I am running amandad, amindexd, amidxtaped from xinetd. All these protocols
are listed in my /etc/services.
Currently, I am only trying to backup the data on the same machine as the
server, so the server and client are the _same machine_. I am using the
eth0 interface IPs to communicate, although, clearly the packets will go
through the loopback. The local firewall is configured to _allow all
packets_ through on the loopback and the eth0 interface (since it's local
only).

The following are relevant files concerning my setup. Some of my setup may
seem redundant and superfluous, however, in my efforts to make things work,
I have tried a number of things.

/etc/passwd entry for amanda user:
backup:x:417:6:Amanda Backup:/root/amanda-data:/bin/bash

/root/amanda-data/.amandahosts:
10.1.0.3   backup
server02.ctbackup
broadcast backup

/etc/hosts:
127.0.0.1 localhost.localdomain   localhost
10.1.0.3   server02.ct.internaldomain.com   server02.ct
0.0.0.0broadcast broadcast

some of amanda.conf:

dumpuser "backup"
inparallel 4
netusage  51200 Kbps
dumpcycle 3 weeks
runspercycle 15
tapecycle 20 tapes
runtapes 1
tpchanger "chg-manual"
tapedev "/dev/nst0"
changerfile "/root/amanda-data/changer-status"
changerdev "/dev/null"
tapetype DAT
infofile "/root/amanda-data/daily"
logdir   "/var/log/amanda/daily"
indexdir "/root/amanda-data/daily"
tapelist "/root/amanda-data/daily/tapelist"

define tapetype DAT {
comment "Archive Python 04687-XXX"
length 4000 mbytes
filemark 100 kbytes
speed 800 kbytes
}

disklist:
server02.ct sda1comp-root
server02.ct sda2comp-user
server02.ct sdb1comp-user

xinetd entries:

service amanda
{
 disable= no
 bind   = 10.1.0.3
 log_on_success += USERID
 log_on_failure += USERID
 socket_type = dgram
 protocol   = udp
 wait   = yes
 user   = root
 server = /usr/local/libexec/amandad
}

service amandaidx
{
 disable= no
 bind   = 10.1.0.3
 log_on_success += USERID
 log_on_failure += USERID
 socket_type = stream
 protocol   = tcp
 wait   = no
 user   = backup
 server = /usr/local/libexec/amindexd
}

service amidxtape
{
 disable= no
 bind   = 10.1.0.3
 log_on_success += USERID
 log_on_failure += USERID
 socket_type = stream
 protocol   = tcp
 wait   = no
 user   = backup
 server = /usr/local/libexec/amidxtaped
}

Following are my debug files for amcheck.

amcheck.debug:

amcheck: debug 1 pid 24151 ruid 417 euid 0 start time Wed May 22 10:29:30
2002
amcheck: dgram_bind: socket bound to 0.0.0.0.929
amcheck: pid 24151 finish time Wed May 22 10:30:00 2002

selfcheck.debug:

selfcheck: checking disk sdb1
selfcheck: device /dev/sdb1
selfcheck: OK
selfcheck: checking disk sda2
selfcheck: device /dev/sda2
selfcheck: OK
selfcheck: checking disk sda1
selfcheck: device /dev/sda1
selfcheck: OK
selfcheck: pid 8251 finish time Wed May 22 10:29:30 2002

amandad.debug:

got packet:

Amanda 2.4 REQ HANDLE 000-48C30708 SEQ 102200
SECURITY USER backup
SERVICE selfcheck
OPTIONS ;
DUMP sdb1 0 OPTIONS |;bsd-auth;compress-fast;
DUMP sda2 0 OPTIONS |;bsd-auth;compress-fast;
DUMP sda1 0 OPTIONS |;bsd-auth;compress-fast;


sending ack:

Amanda 2.4 ACK HANDLE 000-48C30708 SEQ 102200


amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Inva

Me again, still getting WARNING: host: selfcheck request timed out. Hostdown?

[Cory Visi]

Ok, I have looked into my issues further. Many replies on the list have
helped me, although I am still having problems and I do not understand what
Amanda is doing.

Firstly, this error:

amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Invalid argument

Is clearly not indicative of an error. Amanda uses broadcasts to find
clients/servers regardless of the configuration. Some people get this error
but have a perfectly working system.

This error, however:

Amanda Backup Client Hosts Check

WARNING: server02.ct: selfcheck request timed out.  Host down?
Client check: 1 host checked in 30.028 seconds, 1 problem found

IS indicative of a problem.
So, starting from scratch I will explain all the details of my setup:

I am using Amanda 2.4.2p2 on Linux 2.4.13 with glibc 2.2.2 compiled by
myself.
I am running amandad, amindexd, amidxtaped from xinetd. All these protocols
are listed in my /etc/services.
Currently, I am only trying to backup the data on the same machine as the
server, so the server and client are the _same machine_. I am using the
eth0 interface IPs to communicate, although, clearly the packets will go
through the loopback. The local firewall is configured to _allow all
packets_ through on the loopback and the eth0 interface (since it's local
only).

The following are relevant files concerning my setup. Some of my setup may
seem redundant and superfluous, however, in my efforts to make things work,
I have tried a number of things.

/etc/passwd entry for amanda user:
backup:x:417:6:Amanda Backup:/root/amanda-data:/bin/bash

/root/amanda-data/.amandahosts:
10.1.0.3   backup
server02.ctbackup
broadcast backup

/etc/hosts:
127.0.0.1 localhost.localdomain   localhost
10.1.0.3   server02.ct.internaldomain.com   server02.ct
0.0.0.0broadcast broadcast

some of amanda.conf:

dumpuser "backup"
inparallel 4
netusage  51200 Kbps
dumpcycle 3 weeks
runspercycle 15
tapecycle 20 tapes
runtapes 1
tpchanger "chg-manual"
tapedev "/dev/nst0"
changerfile "/root/amanda-data/changer-status"
changerdev "/dev/null"
tapetype DAT
infofile "/root/amanda-data/daily"
logdir   "/var/log/amanda/daily"
indexdir "/root/amanda-data/daily"
tapelist "/root/amanda-data/daily/tapelist"

define tapetype DAT {
comment "Archive Python 04687-XXX"
length 4000 mbytes
filemark 100 kbytes
speed 800 kbytes
}

disklist:
server02.ct sda1comp-root
server02.ct sda2comp-user
server02.ct sdb1comp-user

xinetd entries:

service amanda
{
 disable= no
 bind   = 10.1.0.3
 log_on_success += USERID
 log_on_failure += USERID
 socket_type = dgram
 protocol   = udp
 wait   = yes
 user   = root
 server = /usr/local/libexec/amandad
}

service amandaidx
{
 disable= no
 bind   = 10.1.0.3
 log_on_success += USERID
 log_on_failure += USERID
 socket_type = stream
 protocol   = tcp
 wait   = no
 user   = backup
 server = /usr/local/libexec/amindexd
}

service amidxtape
{
 disable= no
 bind   = 10.1.0.3
 log_on_success += USERID
 log_on_failure += USERID
 socket_type = stream
 protocol   = tcp
 wait   = no
 user   = backup
 server = /usr/local/libexec/amidxtaped
}

Following are my debug files for amcheck.

amcheck.debug:

amcheck: debug 1 pid 24151 ruid 417 euid 0 start time Wed May 22 10:29:30
2002
amcheck: dgram_bind: socket bound to 0.0.0.0.929
amcheck: pid 24151 finish time Wed May 22 10:30:00 2002

selfcheck.debug:

selfcheck: checking disk sdb1
selfcheck: device /dev/sdb1
selfcheck: OK
selfcheck: checking disk sda2
selfcheck: device /dev/sda2
selfcheck: OK
selfcheck: checking disk sda1
selfcheck: device /dev/sda1
selfcheck: OK
selfcheck: pid 8251 finish time Wed May 22 10:29:30 2002

amandad.debug:

got packet:

Amanda 2.4 REQ HANDLE 000-48C30708 SEQ 102200
SECURITY USER backup
SERVICE selfcheck
OPTIONS ;
DUMP sdb1 0 OPTIONS |;bsd-auth;compress-fast;
DUMP sda2 0 OPTIONS |;bsd-auth;compress-fast;
DUMP sda1 0 OPTIONS |;bsd-auth;compress-fast;


sending ack:

Amanda 2.4 ACK HANDLE 000-48C30708 SEQ 102200


amandad: dgram_send_addr: sendto(0.0.0.0.929) failed: Invalid argument
bsd security: remote host broadcast user backup local user backup
amandahosts security check passed
amandad: running service "/usr/local/libexec/selfcheck"
amandad: sending REP packet:

Amanda 2.4 REP HANDLE 000-48C30708 SEQ 102200
OPTIONS ;
OK /dev/sdb1
OK /dev/sda2
OK /dev/sda1
OK /sbin/dump executable
OK /bin/gzip executable
OK /etc/dumpdates read/writable
OK /dev/null read/writable
OK /tmp/amanda has more than 64 KB available.
OK /tmp/amanda has more than 64 KB available.
OK /etc has more than 64 

Re: me again...

[Alexandre Oliva]

On Feb 23, 2001, "isaac flemming" <[EMAIL PROTECTED]> wrote:

> "how to install amanda on a linux box walk through's?"

docs/INSTALL

The book chapter linked to from www.amanda.org

The FAQ

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: me again...

[John R. Jackson]

>ERROR: /dev/nst0: Permission denied

Did you run amcheck as the Amanda user?  What is the Amanda user?
What groups is it a member of?

What are the modes and ownership on /dev/nst0?

>ERROR: localhost: [access as amanda not allowed from amanda@localhost]

Are you using .rhosts or .amandahosts (amadmin xx version | grep HOSTS)?

What is the home directory for "amanda"?  Does it have access to it
(some RH installations put it under another directory without world
search access -- sigh).

Do you have a file in ~amanda named .amandahosts (or .rhosts)?  Does
it contain this line:

  localhost amanda

>ERROR: plath.knox.net: [can not access /dev/sda1 (/): Permission denied]

Same questions as the tape drive.

>isaac

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

me again...

[isaac flemming]

 im starting to feel like im chaising my tail here? anyone know of any good
"how to install amanda on a linux box walk through's?" if so maybe you can
point me in that direction. if not maybe you can help me with this?

Amanda Tape Server Host Check
-
/usr/local/amanda/holdingdisk: 1421316 KB disk space available, using
1411076 KB.
ERROR: /dev/nst0: Permission denied
   (expecting a new tape)
NOTE: skipping tape-writable test.
Server check took 0.003 seconds.

Amanda Backup Client Hosts Check

ERROR: localhost: [access as amanda not allowed from amanda@localhost]
ERROR: plath.knox.net: [can not access /dev/sda1 (/): Permission denied]
Client check: 2 hosts checked in 1.131 seconds, 2 problems found.

(brought to you by Amanda 2.4.1p1)

any sugestions?

thanks again for any help!
isaac