Re: all estimate failed - problem

[Joshua Baker-LePain]

On Fri, 14 Oct 2005 at 4:38pm, Sylvia Gelman wrote

Is there a way how I could test the estimate time "dry" without making 
really a backup?


Yep.  sendsize*debug has the exact command it runs, which you could then 
run by hand.


I´m a little bit confused with the arguments ...
as user amanda, I did the following:
mailserver% sendsize /opt/gnu/bin/tar --create --file /dev/null --directory 
/var/mail --one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/mailserver_var_mail_5.new --sparse 
--ignore-failed-read --totals --exclude-from 
/tmp/amanda/sendsize._var_mail.20051013210554.exclude

il.20051013210554.exclude: Command not found
mailserver% sendsize /opt/gnu/bin/tar --create --file /dev/null --directory 
/var/mail --one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/mailserver_var_mail_5.new --sparse 
--ignore-failed-read --totals --exclude-from 
/tmp/amanda/sendsize._var_mail.20051013210554.exclude .

il.20051013210554.exclude: Command not found
mailserver% sendsize /opt/gnu/bin/tar --create --file /dev/null --directory 
/var/mail --one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/mailserver_var_mail_5.new --sparse 
--ignore-failed-read --totals


the last line is now working, but is it correct? Anyway there is no entry in 
the exclude file ...


Those files are created on the fly.  You don't need to be running the 
command through sendsize -- just do the tar command (which should need the 
'.' at the end.


* 
sendsize[5579]: time 349.922: Total bytes written: -1386622976


And there's your problem.  tar is returning a *negative* size for 
/var/mail.  You have to figure out why that's happening.  Personally, I 
have no idea.  :)


I had a similar problem, but the last time it was a wrong tar version, for 
that reason it didn´t succeeded on the whole server but now it is only one 
DLE, that is really strange!


Any ideas


First off, what version of tar is this?  I'd also have a look at 
/var/mail.  Anything odd -- sparse files, too many inodes in use, etc? 
How big should it be?  Do the estimate tar command in various parts of 
/var/mail and see if any in particular return negative sizes.


--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: all estimate failed - problem

[Sylvia Gelman]

Hi Joshua,
thanks for your answer!

Is there a way how I could test the estimate time "dry" without making 
really a backup?



Yep.  sendsize*debug has the exact command it runs, which you could then 
run by hand.

I´m a little bit confused with the arguments ...
as user amanda, I did the following:
mailserver% sendsize /opt/gnu/bin/tar --create --file /dev/null --directory /var/mail 
--one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/mailserver_var_mail_5.new --sparse 
--ignore-failed-read --totals --exclude-from 
/tmp/amanda/sendsize._var_mail.20051013210554.exclude

il.20051013210554.exclude: Command not found
mailserver% sendsize /opt/gnu/bin/tar --create --file /dev/null --directory /var/mail 
--one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/mailserver_var_mail_5.new --sparse 
--ignore-failed-read --totals --exclude-from 
/tmp/amanda/sendsize._var_mail.20051013210554.exclude .

il.20051013210554.exclude: Command not found
mailserver% sendsize /opt/gnu/bin/tar --create --file /dev/null --directory /var/mail 
--one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/mailserver_var_mail_5.new --sparse 
--ignore-failed-read --totals


the last line is now working, but is it correct? Anyway there is no entry in the exclude 
file ...


sendsize[5579]: argument list: /opt/gnu/bin/tar --create --file 
/dev/null --directory /var/mail --one-file-system --listed-incremental 
/usr/local/amanda/va
r/amanda/gnutar-lists/mailserver_var_mail_0.new --sparse 
--ignore-failed-read --totals --exclude-from 
/tmp/amanda/sendsize._var_mail.20051013210005.exclude .



There's the command (I'm assuming the odd line break is a mailer issue.


yes



* 


sendsize[5579]: time 349.922: Total bytes written: -1386622976



And there's your problem.  tar is returning a *negative* size for 
/var/mail.  You have to figure out why that's happening.  Personally, I 
have no idea.  :)


I had a similar problem, but the last time it was a wrong tar version, for that reason it 
didn´t succeeded on the whole server but now it is only one DLE, that is really strange!


Any ideas

Sylvia

Re: all estimate failed - problem

[Joshua Baker-LePain]

On Fri, 14 Oct 2005 at 2:44pm, Sylvia Gelman wrote


mailserver   /var/mail lev 0 FAILED [disk /var/mail, all estimate failed]

*snip*
Is there a way how I could test the estimate time "dry" without making really 
a backup?


Yep.  sendsize*debug has the exact command it runs, which you could then 
run by hand.


sendsize[5579]: time 0.332: calculating for amname '/var/mail', dirname 
'/var/mail', spindle -1

sendsize[5579]: time 0.335: getting size via gnutar for /var/mail level 0
sendsize[5577]: time 0.344: waiting for any estimate child: 1 running
sendsize[5579]: time 0.375: spawning /usr/local/amanda/libexec/runtar in 
pipeline
sendsize[5579]: argument list: /opt/gnu/bin/tar --create --file /dev/null 
--directory /var/mail --one-file-system --listed-incremental 
/usr/local/amanda/va
r/amanda/gnutar-lists/glia_var_mail_0.new --sparse --ignore-failed-read 
--totals --exclude-from /tmp/amanda/sendsize._var_mail.20051013210005.exclude 
.


There's the command (I'm assuming the odd line break is a mailer issue.


*
sendsize[5579]: time 349.922: Total bytes written: -1386622976


And there's your problem.  tar is returning a *negative* size for 
/var/mail.  You have to figure out why that's happening.  Personally, I 
have no idea.  :)


--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

RE: all estimate failed

[LaValley, Brian E]

I had AMANDA installed as an RPM through synaptic, so I'm sure it had all
kinds of default options. I tried to just change the dump user wherever I
could find it.  I noticed that some apps were still running as "amanda" so I
uninstalled the RPM and manually compiled  instead with the user=backup.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon LaBadie
Sent: Tuesday, July 19, 2005 11:31 AM
To: amanda-users@amanda.org
Subject: Re: all estimate failed


On Tue, Jul 19, 2005 at 11:04:57AM -0400, LaValley, Brian E wrote:
> I am all set now. Thanks for all the ideas. It turned out to be one of the
> helper programs running as "amanda" instead of "backup" as a username.
> "amanda" is a regular user on my systems.  I just completed my first
AMANDA
> backup.
> 

Was that due to a manual install rather than the "make install"
done as root with programs built by you from the amanda sources?
If the latter, some part of the install procedure needs to be
checked.  But I suspect that is not the case.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: all estimate failed

[Jon LaBadie]

On Tue, Jul 19, 2005 at 11:04:57AM -0400, LaValley, Brian E wrote:
> I am all set now. Thanks for all the ideas. It turned out to be one of the
> helper programs running as "amanda" instead of "backup" as a username.
> "amanda" is a regular user on my systems.  I just completed my first AMANDA
> backup.
> 

Was that due to a manual install rather than the "make install"
done as root with programs built by you from the amanda sources?
If the latter, some part of the install procedure needs to be
checked.  But I suspect that is not the case.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

RE: all estimate failed

[LaValley, Brian E]

I am all set now. Thanks for all the ideas. It turned out to be one of the
helper programs running as "amanda" instead of "backup" as a username.
"amanda" is a regular user on my systems.  I just completed my first AMANDA
backup.

My etimeout was set at 300 seconds, and the amdump would fail immediately,
so I knew that wasn't the issue.

-Original Message-
From: Brian Cuttler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 19, 2005 10:02 AM
To: Gene Heskett; [EMAIL PROTECTED]
Cc: amanda-users@amanda.org
Subject: Re: all estimate failed



Brian,
Gene,

couple of things, 1st, I'm thinking that if there is a jukebox
involved (tape loaded from slot 3) then perhaps a 5 minute delay
to load the tape isn't necessarilly a problem. 2nd, I'm stupid
and should have seen it yesterday - estimate failed, suggest
raising the etimeout value is amanda.conf.

If the partition(s) are large and etimeout is low or the client is
slow for any reasons...

On Tue, Jul 19, 2005 at 08:57:57AM -0400, Gene Heskett wrote:
> On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
> >I do have some things in different places.  What files should be in
> >/tmp/amanda?
> >I already had a username of amanda at this location, so my AMANDA
> > username is "backup"
> >Here is my amcheck run:
> >
> >[EMAIL PROTECTED] [27]>amcheck DailySet1
> >Amanda Tape Server Host Check
> >-
> >Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
> > available, that's plenty
> >amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
> >NOTE: skipping tape-writable test
> >Tape DailySet1-A03 label ok
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does
> > not exist
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does
> > not exist
> >Server check took 312.817 seconds
> 
> Somethings definitely wrong here, but from this I've no idea what.  It 
> should not take a tape drive over 5 minutes to locate and load the 
> next correct tape.  My server check is usually a very small fraction 
> of a second, but I'm also using virtual tapes on a 200Gb drive.
> 
> >Amanda Backup Client Hosts Check
> >
> >Client check: 1 host checked in 0.025 seconds, 0 problems found
> >
> >(brought to you by Amanda 2.4.4p3)
> >[EMAIL PROTECTED] [28]>
> >
> The client check time is more realistic.  Heres a clip from mine:
> Server check took 0.579 seconds
> 
> Amanda Backup Client Hosts Check
> 
> Client check: 2 hosts checked in 0.523 seconds, 0 problems found
> 
> (brought to you by Amanda 2.4.5-20050711)
> 
> >
> >-Original Message-
> >From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >Sent: Monday, July 18, 2005 4:45 PM
> >To: LaValley, Brian E
> >Cc: 'amanda-users@amanda.org'
> >Subject: Re: all estimate failed
> >
> >
> >Brian,
> >
> >On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
> >> Yes, amcheck passed.
> >>
> >> /tmp/amanda doesn't exist.
> >> There isn't anything that seems to be related to amanda in the
> >> messages
> >
> >log.
> >
> >> amcheck didn't pass until I setup the xinetd files.  Can I assume
> >> they are setup correctly if amcheck is fine?
> >> How can I test the .amandahosts file?
> >
> >If amcheck said you where ok talking to the client then all of those
> >issues should be ok.
> >
> >I take that back, if amcheck said your client was ok you should have
> >had files in /tmp/amanda at that point. Both amcheck and amdump
> > should be causing files to be created on the client. You sure the
> > client passed the check ?
> >
> >
> >The rest of this email may not be relevant.
> >
> >Haven't a lot of experience in, er, xinetd ?, must be linux ?
> >Can comment but can tell you that in IRIX and Solaris if my
> >amanda user on the client wasn't in the correct group I needed
> >to fix the group and/or devices files /dev/dsk/* to allow RW for
> >the amanda user's group.
> >
> >Suspect you have some similar issue there.
> >
> >> -Original Message-
> >> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, July 18, 2005 4:31 PM
> >> To: LaValley, Brian E
> >> Cc: 'amanda-users@amanda.org'
> >> Subject: Re: all estimate failed
> >>
> >>
&g

Re: all estimate failed

[Gene Heskett]

On Tuesday 19 July 2005 10:02, Brian Cuttler wrote:
>Brian,
>Gene,
>
>couple of things, 1st, I'm thinking that if there is a jukebox
>involved (tape loaded from slot 3) then perhaps a 5 minute delay
>to load the tape isn't necessarilly a problem.

Maybe not a problem, but I recall my robots were generally only a 2 to 
3 minute lag, back when I was using them.  Seagate 4586n's, 
admittedly pretty cheap though.

>2nd, I'm stupid 
>and should have seen it yesterday - estimate failed, suggest
>raising the etimeout value is amanda.conf.

I saw that too, and figured somebody would catch it as the message was 
fairly old by the time I saw it.  And I agree.  Maybe its time the 
default etimeout was raised from 5 minutes to 10 or 15?

>If the partition(s) are large and etimeout is low or the client is
>slow for any reasons...
>
>On Tue, Jul 19, 2005 at 08:57:57AM -0400, Gene Heskett wrote:
>> On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
>> >I do have some things in different places.  What files should be
>> > in /tmp/amanda?
>> >I already had a username of amanda at this location, so my AMANDA
>> > username is "backup"
>> >Here is my amcheck run:
>> >
>> >[EMAIL PROTECTED] [27]>amcheck DailySet1
>> >Amanda Tape Server Host Check
>> >-
>> >Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
>> > available, that's plenty
>> >amcheck-server: slot 3: date Xlabel DailySet1-A03 (new
>> > tape) NOTE: skipping tape-writable test
>> >Tape DailySet1-A03 label ok
>> >WARNING: info file
>> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info:
>> > does not exist
>> >WARNING: info file
>> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info:
>> > does not exist
>> >Server check took 312.817 seconds
>>
>> Somethings definitely wrong here, but from this I've no idea what.
>>  It should not take a tape drive over 5 minutes to locate and load
>> the next correct tape.  My server check is usually a very small
>> fraction of a second, but I'm also using virtual tapes on a 200Gb
>> drive.
>>
>> >Amanda Backup Client Hosts Check
>> >
>> >Client check: 1 host checked in 0.025 seconds, 0 problems found
>> >
>> >(brought to you by Amanda 2.4.4p3)
>> >[EMAIL PROTECTED] [28]>
>>
>> The client check time is more realistic.  Heres a clip from mine:
>> Server check took 0.579 seconds
>>
>> Amanda Backup Client Hosts Check
>> 
>> Client check: 2 hosts checked in 0.523 seconds, 0 problems found
>>
>> (brought to you by Amanda 2.4.5-20050711)
>>
>> >-Original Message-
>> >From: Brian Cuttler [mailto:[EMAIL PROTECTED]
>> >Sent: Monday, July 18, 2005 4:45 PM
>> >To: LaValley, Brian E
>> >Cc: 'amanda-users@amanda.org'
>> >Subject: Re: all estimate failed
>> >
>> >
>> >Brian,
>> >
>> >On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
>> >> Yes, amcheck passed.
>> >>
>> >> /tmp/amanda doesn't exist.
>> >> There isn't anything that seems to be related to amanda in the
>> >> messages
>> >
>> >log.
>> >
>> >> amcheck didn't pass until I setup the xinetd files.  Can I
>> >> assume they are setup correctly if amcheck is fine?
>> >> How can I test the .amandahosts file?
>> >
>> >If amcheck said you where ok talking to the client then all of
>> > those issues should be ok.
>> >
>> >I take that back, if amcheck said your client was ok you should
>> > have had files in /tmp/amanda at that point. Both amcheck and
>> > amdump should be causing files to be created on the client. You
>> > sure the client passed the check ?
>> >
>> >
>> >The rest of this email may not be relevant.
>> >
>> >Haven't a lot of experience in, er, xinetd ?, must be linux ?
>> >Can comment but can tell you that in IRIX and Solaris if my
>> >amanda user on the client wasn't in the correct group I needed
>> >to fix the group and/or devices files /dev/dsk/* to allow RW for
>> >the amanda user's group.
>> >
>> >Suspect you have some similar issue there.
>> >
>> >> -Original Message-
>> >> From: Brian Cuttler [ma

Re: all estimate failed

[Brian Cuttler]

Brian,
Gene,

couple of things, 1st, I'm thinking that if there is a jukebox
involved (tape loaded from slot 3) then perhaps a 5 minute delay
to load the tape isn't necessarilly a problem. 2nd, I'm stupid
and should have seen it yesterday - estimate failed, suggest
raising the etimeout value is amanda.conf.

If the partition(s) are large and etimeout is low or the client is
slow for any reasons...

On Tue, Jul 19, 2005 at 08:57:57AM -0400, Gene Heskett wrote:
> On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
> >I do have some things in different places.  What files should be in
> >/tmp/amanda?
> >I already had a username of amanda at this location, so my AMANDA
> > username is "backup"
> >Here is my amcheck run:
> >
> >[EMAIL PROTECTED] [27]>amcheck DailySet1
> >Amanda Tape Server Host Check
> >-
> >Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
> > available, that's plenty
> >amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
> >NOTE: skipping tape-writable test
> >Tape DailySet1-A03 label ok
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does
> > not exist
> >WARNING: info file
> >/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does
> > not exist
> >Server check took 312.817 seconds
> 
> Somethings definitely wrong here, but from this I've no idea what.  It 
> should not take a tape drive over 5 minutes to locate and load the 
> next correct tape.  My server check is usually a very small fraction 
> of a second, but I'm also using virtual tapes on a 200Gb drive.
> 
> >Amanda Backup Client Hosts Check
> >
> >Client check: 1 host checked in 0.025 seconds, 0 problems found
> >
> >(brought to you by Amanda 2.4.4p3)
> >[EMAIL PROTECTED] [28]>
> >
> The client check time is more realistic.  Heres a clip from mine:
> Server check took 0.579 seconds
> 
> Amanda Backup Client Hosts Check
> 
> Client check: 2 hosts checked in 0.523 seconds, 0 problems found
> 
> (brought to you by Amanda 2.4.5-20050711)
> 
> >
> >-Original Message-
> >From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >Sent: Monday, July 18, 2005 4:45 PM
> >To: LaValley, Brian E
> >Cc: 'amanda-users@amanda.org'
> >Subject: Re: all estimate failed
> >
> >
> >Brian,
> >
> >On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
> >> Yes, amcheck passed.
> >>
> >> /tmp/amanda doesn't exist.
> >> There isn't anything that seems to be related to amanda in the
> >> messages
> >
> >log.
> >
> >> amcheck didn't pass until I setup the xinetd files.  Can I assume
> >> they are setup correctly if amcheck is fine?
> >> How can I test the .amandahosts file?
> >
> >If amcheck said you where ok talking to the client then all of those
> >issues should be ok.
> >
> >I take that back, if amcheck said your client was ok you should have
> >had files in /tmp/amanda at that point. Both amcheck and amdump
> > should be causing files to be created on the client. You sure the
> > client passed the check ?
> >
> >
> >The rest of this email may not be relevant.
> >
> >Haven't a lot of experience in, er, xinetd ?, must be linux ?
> >Can comment but can tell you that in IRIX and Solaris if my
> >amanda user on the client wasn't in the correct group I needed
> >to fix the group and/or devices files /dev/dsk/* to allow RW for
> >the amanda user's group.
> >
> >Suspect you have some similar issue there.
> >
> >> -Original Message-
> >> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, July 18, 2005 4:31 PM
> >> To: LaValley, Brian E
> >> Cc: 'amanda-users@amanda.org'
> >> Subject: Re: all estimate failed
> >>
> >>
> >>
> >> Brian,
> >>
> >> You said manual dump, the amcheck succeeded ?
> >>
> >> Did you find any files in the client's /tmp/amanda/ directory ?
> >> Do you see any errors in /var/adm/{messages|SYSLOG} ?
> >> The client's xinetd files are properly configured to activate
> >> the service ? The client's .amandahosts file is properly setup ?
> >>
> >> Even if the client == server this must be done.
> >>
> >> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaVall

Re: all estimate failed

[Gene Heskett]

On Tuesday 19 July 2005 07:49, LaValley, Brian E wrote:
>I do have some things in different places.  What files should be in
>/tmp/amanda?
>I already had a username of amanda at this location, so my AMANDA
> username is "backup"
>Here is my amcheck run:
>
>[EMAIL PROTECTED] [27]>amcheck DailySet1
>Amanda Tape Server Host Check
>-
>Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space
> available, that's plenty
>amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
>NOTE: skipping tape-writable test
>Tape DailySet1-A03 label ok
>WARNING: info file
>/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does
> not exist
>WARNING: info file
>/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does
> not exist
>Server check took 312.817 seconds

Somethings definitely wrong here, but from this I've no idea what.  It 
should not take a tape drive over 5 minutes to locate and load the 
next correct tape.  My server check is usually a very small fraction 
of a second, but I'm also using virtual tapes on a 200Gb drive.

>Amanda Backup Client Hosts Check
>
>Client check: 1 host checked in 0.025 seconds, 0 problems found
>
>(brought to you by Amanda 2.4.4p3)
>[EMAIL PROTECTED] [28]>
>
The client check time is more realistic.  Heres a clip from mine:
Server check took 0.579 seconds

Amanda Backup Client Hosts Check

Client check: 2 hosts checked in 0.523 seconds, 0 problems found

(brought to you by Amanda 2.4.5-20050711)

>
>-Original Message-
>From: Brian Cuttler [mailto:[EMAIL PROTECTED]
>Sent: Monday, July 18, 2005 4:45 PM
>To: LaValley, Brian E
>Cc: 'amanda-users@amanda.org'
>Subject: Re: all estimate failed
>
>
>Brian,
>
>On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
>> Yes, amcheck passed.
>>
>> /tmp/amanda doesn't exist.
>> There isn't anything that seems to be related to amanda in the
>> messages
>
>log.
>
>> amcheck didn't pass until I setup the xinetd files.  Can I assume
>> they are setup correctly if amcheck is fine?
>> How can I test the .amandahosts file?
>
>If amcheck said you where ok talking to the client then all of those
>issues should be ok.
>
>I take that back, if amcheck said your client was ok you should have
>had files in /tmp/amanda at that point. Both amcheck and amdump
> should be causing files to be created on the client. You sure the
> client passed the check ?
>
>
>The rest of this email may not be relevant.
>
>Haven't a lot of experience in, er, xinetd ?, must be linux ?
>Can comment but can tell you that in IRIX and Solaris if my
>amanda user on the client wasn't in the correct group I needed
>to fix the group and/or devices files /dev/dsk/* to allow RW for
>the amanda user's group.
>
>Suspect you have some similar issue there.
>
>> -Original Message-
>> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
>> Sent: Monday, July 18, 2005 4:31 PM
>> To: LaValley, Brian E
>> Cc: 'amanda-users@amanda.org'
>> Subject: Re: all estimate failed
>>
>>
>>
>> Brian,
>>
>> You said manual dump, the amcheck succeeded ?
>>
>> Did you find any files in the client's /tmp/amanda/ directory ?
>> Do you see any errors in /var/adm/{messages|SYSLOG} ?
>> The client's xinetd files are properly configured to activate
>> the service ? The client's .amandahosts file is properly setup ?
>>
>> Even if the client == server this must be done.
>>
>> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
>> > I have just decided to give AMANDA a try and am learning as I
>> > go. I have gotten as far as trying a manual amdump, but it seems
>> > the estimate is failing and nothing gets backed up. What could
>> > this be?
>> >
>> >
>> > The email report follows, and the amdump log is attached.
>
>
>
>
>
>
>
>
>> > --
>> >
>> > These dumps were to tape DailySet1-A02.
>> > The next tape Amanda expects to use is: a new tape.
>> > The next new tape already labelled is: DailySet1-A01.
>> >
>> > FAILURE AND STRANGE DUMP SUMMARY:
>> >   blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
>> >   blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate faile

Re: all estimate failed

[Paul Bijnens]

LaValley, Brian E wrote:

I do have some things in different places.  What files should be in
/tmp/amanda?
I already had a username of amanda at this location, so my AMANDA username
is "backup"



the command "amadmin XX version" will show you where the debug
files are in:
   ... AMANDA_DBGDIR="/tmp/amanda" ...

--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

RE: all estimate failed

[LaValley, Brian E]

I do have some things in different places.  What files should be in
/tmp/amanda?
I already had a username of amanda at this location, so my AMANDA username
is "backup"
Here is my amcheck run:

[EMAIL PROTECTED] [27]>amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /native/amanda-2.4.4p2/dumps: 89164984 KB disk space available,
that's plenty
amcheck-server: slot 3: date Xlabel DailySet1-A03 (new tape)
NOTE: skipping tape-writable test
Tape DailySet1-A03 label ok
WARNING: info file
/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc5/info: does not
exist
WARNING: info file
/native/amanda-2.4.4p2/DailySet1/curinfo/blavalley-l/hdc1/info: does not
exist
Server check took 312.817 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.025 seconds, 0 problems found

(brought to you by Amanda 2.4.4p3)
[EMAIL PROTECTED] [28]>



-Original Message-
From: Brian Cuttler [mailto:[EMAIL PROTECTED]
Sent: Monday, July 18, 2005 4:45 PM
To: LaValley, Brian E
Cc: 'amanda-users@amanda.org'
Subject: Re: all estimate failed


Brian,

On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
> Yes, amcheck passed.
> 
> /tmp/amanda doesn't exist.
> There isn't anything that seems to be related to amanda in the messages
log.
> amcheck didn't pass until I setup the xinetd files.  Can I assume they are
> setup correctly if amcheck is fine?
> How can I test the .amandahosts file?

If amcheck said you where ok talking to the client then all of those
issues should be ok.

I take that back, if amcheck said your client was ok you should have
had files in /tmp/amanda at that point. Both amcheck and amdump should
be causing files to be created on the client. You sure the client passed
the check ?


The rest of this email may not be relevant.

Haven't a lot of experience in, er, xinetd ?, must be linux ?
Can comment but can tell you that in IRIX and Solaris if my 
amanda user on the client wasn't in the correct group I needed
to fix the group and/or devices files /dev/dsk/* to allow RW for
the amanda user's group.

Suspect you have some similar issue there.


> -Original Message-
> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 18, 2005 4:31 PM
> To: LaValley, Brian E
> Cc: 'amanda-users@amanda.org'
> Subject: Re: all estimate failed
> 
> 
> 
> Brian,
> 
> You said manual dump, the amcheck succeeded ?
> 
> Did you find any files in the client's /tmp/amanda/ directory ?
> Do you see any errors in /var/adm/{messages|SYSLOG} ?
> The client's xinetd files are properly configured to activate
> the service ? The client's .amandahosts file is properly setup ?
> 
> Even if the client == server this must be done.
> 
> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> > I have just decided to give AMANDA a try and am learning as I go. I have
> > gotten as far as trying a manual amdump, but it seems the estimate is
> > failing and nothing gets backed up. What could this be?
> > 
> > 
> > The email report follows, and the amdump log is attached.
> >
>

> >
>

> > --
> > 
> > These dumps were to tape DailySet1-A02.
> > The next tape Amanda expects to use is: a new tape.
> > The next new tape already labelled is: DailySet1-A01.
> > 
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
> >   blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate failed]
> > 
> > 
> > STATISTICS:
> >   Total   Full  Daily
> >       
> > Estimate Time (hrs:min)0:00
> > Run Time (hrs:min) 0:03
> > Dump Time (hrs:min)0:00   0:00   0:00
> > Output Size (meg)   0.00.00.0
> > Original Size (meg) 0.00.00.0
> > Avg Compressed Size (%) -- -- -- 
> > Filesystems Dumped0  0  0
> > Avg Dump Rate (k/s) -- -- -- 
> > 
> > Tape Time (hrs:min)0:00   0:00   0:00
> > Tape Size (meg) 0.00.00.0
> > Tape Used (%)   0.00.00.0
> > Filesystems Taped 0  0  0
> > Avg Tp Write Rate (k/s) -- -- -- 
> > 
> > USAGE BY TAPE:
> >   Label   Time  Size  

Re: all estimate failed

[Brian Cuttler]

Brian,

On Mon, Jul 18, 2005 at 04:44:00PM -0400, LaValley, Brian E wrote:
> Yes, amcheck passed.
> 
> /tmp/amanda doesn't exist.
> There isn't anything that seems to be related to amanda in the messages log.
> amcheck didn't pass until I setup the xinetd files.  Can I assume they are
> setup correctly if amcheck is fine?
> How can I test the .amandahosts file?

If amcheck said you where ok talking to the client then all of those
issues should be ok.

I take that back, if amcheck said your client was ok you should have
had files in /tmp/amanda at that point. Both amcheck and amdump should
be causing files to be created on the client. You sure the client passed
the check ?


The rest of this email may not be relevant.

Haven't a lot of experience in, er, xinetd ?, must be linux ?
Can comment but can tell you that in IRIX and Solaris if my 
amanda user on the client wasn't in the correct group I needed
to fix the group and/or devices files /dev/dsk/* to allow RW for
the amanda user's group.

Suspect you have some similar issue there.


> -Original Message-
> From: Brian Cuttler [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 18, 2005 4:31 PM
> To: LaValley, Brian E
> Cc: 'amanda-users@amanda.org'
> Subject: Re: all estimate failed
> 
> 
> 
> Brian,
> 
> You said manual dump, the amcheck succeeded ?
> 
> Did you find any files in the client's /tmp/amanda/ directory ?
> Do you see any errors in /var/adm/{messages|SYSLOG} ?
> The client's xinetd files are properly configured to activate
> the service ? The client's .amandahosts file is properly setup ?
> 
> Even if the client == server this must be done.
> 
> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> > I have just decided to give AMANDA a try and am learning as I go. I have
> > gotten as far as trying a manual amdump, but it seems the estimate is
> > failing and nothing gets backed up. What could this be?
> > 
> > 
> > The email report follows, and the amdump log is attached.
> >
> 
> >
> 
> > --
> > 
> > These dumps were to tape DailySet1-A02.
> > The next tape Amanda expects to use is: a new tape.
> > The next new tape already labelled is: DailySet1-A01.
> > 
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
> >   blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate failed]
> > 
> > 
> > STATISTICS:
> >   Total   Full  Daily
> >       
> > Estimate Time (hrs:min)0:00
> > Run Time (hrs:min) 0:03
> > Dump Time (hrs:min)0:00   0:00   0:00
> > Output Size (meg)   0.00.00.0
> > Original Size (meg) 0.00.00.0
> > Avg Compressed Size (%) -- -- -- 
> > Filesystems Dumped0  0  0
> > Avg Dump Rate (k/s) -- -- -- 
> > 
> > Tape Time (hrs:min)0:00   0:00   0:00
> > Tape Size (meg) 0.00.00.0
> > Tape Used (%)   0.00.00.0
> > Filesystems Taped 0  0  0
> > Avg Tp Write Rate (k/s) -- -- -- 
> > 
> > USAGE BY TAPE:
> >   Label   Time  Size  %Nb
> >   DailySet1-A02   0:00   0.00.0 0
> > 
> > 
> > NOTES:
> >   planner: Adding new disk blavalley-l:hdc1.
> >   planner: Adding new disk blavalley-l:hdc5.
> >   driver: WARNING: got empty schedule from planner
> >   taper: tape DailySet1-A02 kb 0 fm 0 [OK]
> > 
> > 
> > DUMP SUMMARY:
> >  DUMPER STATSTAPER STATS 
> > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
> > -- - 
> > blavalley-l  hdc10 FAILED ---
> > blavalley-l  hdc50 FAILED ---
> > 
> > (brought to you by Amanda version 2.4.4p3)
> >  <> 
> > 
> 
> 
> ---
>Brian R Cuttler [EMAIL PROTECTED]
>Computer Systems Support(v) 518 486-1697
>Wadsworth Center(f) 518 473-6384
>NYS Department of HealthHelp Desk 518 473-0773
---
   Brian R Cuttler [EMAIL PROTECTED]
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773

Re: all estimate failed

[Brian Cuttler]

Brian,

You said manual dump, the amcheck succeeded ?

Did you find any files in the client's /tmp/amanda/ directory ?
Do you see any errors in /var/adm/{messages|SYSLOG} ?
The client's xinetd files are properly configured to activate
the service ? The client's .amandahosts file is properly setup ?

Even if the client == server this must be done.

On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> I have just decided to give AMANDA a try and am learning as I go. I have
> gotten as far as trying a manual amdump, but it seems the estimate is
> failing and nothing gets backed up. What could this be?
> 
> 
> The email report follows, and the amdump log is attached.
> 
> 
> --
> 
> These dumps were to tape DailySet1-A02.
> The next tape Amanda expects to use is: a new tape.
> The next new tape already labelled is: DailySet1-A01.
> 
> FAILURE AND STRANGE DUMP SUMMARY:
>   blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
>   blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate failed]
> 
> 
> STATISTICS:
>   Total   Full  Daily
>       
> Estimate Time (hrs:min)0:00
> Run Time (hrs:min) 0:03
> Dump Time (hrs:min)0:00   0:00   0:00
> Output Size (meg)   0.00.00.0
> Original Size (meg) 0.00.00.0
> Avg Compressed Size (%) -- -- -- 
> Filesystems Dumped0  0  0
> Avg Dump Rate (k/s) -- -- -- 
> 
> Tape Time (hrs:min)0:00   0:00   0:00
> Tape Size (meg) 0.00.00.0
> Tape Used (%)   0.00.00.0
> Filesystems Taped 0  0  0
> Avg Tp Write Rate (k/s) -- -- -- 
> 
> USAGE BY TAPE:
>   Label   Time  Size  %Nb
>   DailySet1-A02   0:00   0.00.0 0
> 
> 
> NOTES:
>   planner: Adding new disk blavalley-l:hdc1.
>   planner: Adding new disk blavalley-l:hdc5.
>   driver: WARNING: got empty schedule from planner
>   taper: tape DailySet1-A02 kb 0 fm 0 [OK]
> 
> 
> DUMP SUMMARY:
>  DUMPER STATSTAPER STATS 
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
> -- - 
> blavalley-l  hdc10 FAILED ---
> blavalley-l  hdc50 FAILED ---
> 
> (brought to you by Amanda version 2.4.4p3)
>  <> 
> 


---
   Brian R Cuttler [EMAIL PROTECTED]
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773

RE: all estimate failed

[LaValley, Brian E]

Yes, amcheck passed.

/tmp/amanda doesn't exist.
There isn't anything that seems to be related to amanda in the messages log.
amcheck didn't pass until I setup the xinetd files.  Can I assume they are
setup correctly if amcheck is fine?
How can I test the .amandahosts file?


-Original Message-
From: Brian Cuttler [mailto:[EMAIL PROTECTED]
Sent: Monday, July 18, 2005 4:31 PM
To: LaValley, Brian E
Cc: 'amanda-users@amanda.org'
Subject: Re: all estimate failed



Brian,

You said manual dump, the amcheck succeeded ?

Did you find any files in the client's /tmp/amanda/ directory ?
Do you see any errors in /var/adm/{messages|SYSLOG} ?
The client's xinetd files are properly configured to activate
the service ? The client's .amandahosts file is properly setup ?

Even if the client == server this must be done.

On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> I have just decided to give AMANDA a try and am learning as I go. I have
> gotten as far as trying a manual amdump, but it seems the estimate is
> failing and nothing gets backed up. What could this be?
> 
> 
> The email report follows, and the amdump log is attached.
>

>

> --
> 
> These dumps were to tape DailySet1-A02.
> The next tape Amanda expects to use is: a new tape.
> The next new tape already labelled is: DailySet1-A01.
> 
> FAILURE AND STRANGE DUMP SUMMARY:
>   blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
>   blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate failed]
> 
> 
> STATISTICS:
>   Total   Full  Daily
>       
> Estimate Time (hrs:min)0:00
> Run Time (hrs:min) 0:03
> Dump Time (hrs:min)0:00   0:00   0:00
> Output Size (meg)   0.00.00.0
> Original Size (meg) 0.00.00.0
> Avg Compressed Size (%) -- -- -- 
> Filesystems Dumped0  0  0
> Avg Dump Rate (k/s) -- -- -- 
> 
> Tape Time (hrs:min)0:00   0:00   0:00
> Tape Size (meg) 0.00.00.0
> Tape Used (%)   0.00.00.0
> Filesystems Taped 0  0  0
> Avg Tp Write Rate (k/s) -- -- -- 
> 
> USAGE BY TAPE:
>   Label   Time  Size  %Nb
>   DailySet1-A02   0:00   0.00.0 0
> 
> 
> NOTES:
>   planner: Adding new disk blavalley-l:hdc1.
>   planner: Adding new disk blavalley-l:hdc5.
>   driver: WARNING: got empty schedule from planner
>   taper: tape DailySet1-A02 kb 0 fm 0 [OK]
> 
> 
> DUMP SUMMARY:
>  DUMPER STATSTAPER STATS 
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
> -- - 
> blavalley-l  hdc10 FAILED ---
> blavalley-l  hdc50 FAILED ---
> 
> (brought to you by Amanda version 2.4.4p3)
>  <> 
> 


---
   Brian R Cuttler [EMAIL PROTECTED]
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773

Re: all estimate failed

[khalid maqsudi]

can you send an output of your planner?


# khalid/
- Original Message - 
From: "Brian Cuttler" <[EMAIL PROTECTED]>
To: "LaValley, Brian E" <[EMAIL PROTECTED]>
Cc: 
Sent: Monday, July 18, 2005 4:31 PM
Subject: Re: all estimate failed


>
> Brian,
>
> You said manual dump, the amcheck succeeded ?
>
> Did you find any files in the client's /tmp/amanda/ directory ?
> Do you see any errors in /var/adm/{messages|SYSLOG} ?
> The client's xinetd files are properly configured to activate
> the service ? The client's .amandahosts file is properly setup ?
>
> Even if the client == server this must be done.
>
> On Mon, Jul 18, 2005 at 04:28:00PM -0400, LaValley, Brian E wrote:
> > I have just decided to give AMANDA a try and am learning as I go. I have
> > gotten as far as trying a manual amdump, but it seems the estimate is
> > failing and nothing gets backed up. What could this be?
> >
> >
> > The email report follows, and the amdump log is attached.
>
> --
--
>
> --
--
> > --
> >
> > These dumps were to tape DailySet1-A02.
> > The next tape Amanda expects to use is: a new tape.
> > The next new tape already labelled is: DailySet1-A01.
> >
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   blavalley- hdc5 lev 0 FAILED [disk hdc5, all estimate failed]
> >   blavalley- hdc1 lev 0 FAILED [disk hdc1, all estimate failed]
> >
> >
> > STATISTICS:
> >   Total   Full  Daily
> >       
> > Estimate Time (hrs:min)0:00
> > Run Time (hrs:min) 0:03
> > Dump Time (hrs:min)0:00   0:00   0:00
> > Output Size (meg)   0.00.00.0
> > Original Size (meg) 0.00.00.0
> > Avg Compressed Size (%) -- -- -- 
> > Filesystems Dumped0  0  0
> > Avg Dump Rate (k/s) -- -- -- 
> >
> > Tape Time (hrs:min)0:00   0:00   0:00
> > Tape Size (meg) 0.00.00.0
> > Tape Used (%)   0.00.00.0
> > Filesystems Taped 0  0  0
> > Avg Tp Write Rate (k/s) -- -- -- 
> >
> > USAGE BY TAPE:
> >   Label   Time  Size  %Nb
> >   DailySet1-A02   0:00   0.00.0 0
> >
> >
> > NOTES:
> >   planner: Adding new disk blavalley-l:hdc1.
> >   planner: Adding new disk blavalley-l:hdc5.
> >   driver: WARNING: got empty schedule from planner
> >   taper: tape DailySet1-A02 kb 0 fm 0 [OK]
> >
> >
> > DUMP SUMMARY:
> >  DUMPER STATSTAPER STATS
> > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS
KB/s
>
> -- - 
> > blavalley-l  hdc10
FAILED ---
> > blavalley-l  hdc50
FAILED ---
> >
> > (brought to you by Amanda version 2.4.4p3)
> >  <>
> >
>
>
> ---
>Brian R Cuttler [EMAIL PROTECTED]
>Computer Systems Support(v) 518 486-1697
>Wadsworth Center(f) 518 473-6384
>NYS Department of HealthHelp Desk 518 473-0773
>
>

Re: all estimate failed

[Gene Heskett]

On Monday 18 July 2005 16:28, LaValley, Brian E wrote:
>I have just decided to give AMANDA a try and am learning as I go. I
> have gotten as far as trying a manual amdump, but it seems the
> estimate is failing and nothing gets backed up. What could this be?
>
Did you first run, as amanda, the "amcheck /nameofconfig/" program.
I would not expect it to return without errors in this case.

And don't forget that amdump itself will not run as the user root 
either.

All this is in the FAQ.

-- 
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)
99.35% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: "all estimate failed" on some partitions but not others

[Joshua Baker-LePain]

On Thu, 20 Jan 2005 at 11:39pm, David Newman wrote

> An amanda server on Box A backs up partitions from amanda clients on Box A 
> and Box B. The dumptype is gnutar for both boxes. Backups on Box B work 
> fine. Backups on Box A fail with an "all estimate failed" error.
> 
> Both boxes run GNU tar 1.13.25. The disklist calls both boxes' partitions 
> the same way. And amanda did back up Box A's partition when I used dump 
> as the dumptype. (I'm only trying tar to see if there's a speed increase.)
> 
> Where should I be looking to determine why this is failing?

/tmp/amanda/sendsize*debug and /tmp/amanda/amandad*debug on Box A, as well 
as the relevant amdump.N file(s).

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: all estimate failed error on amanda client

[David Newman]

I'm new to amanda but I've been administering UNIX servers for a while.
Dump is for dumping whole filesystems not directories. Tar is more
versatile. I believe in the amanda.conf you can specify DUMP or GNUTAR as
the dump mechanism. If you used GNUTAR you'll be able to dump only
directories.
Thanks, this is good info.
Is tar also faster than dump?
dn

Building Amanda from FreeBSD ports (was: Re: all estimate failed error on amanda client)

[Toomas Aas]

David Newman wrote:
Note to those installing from the BSD ports collection: You'll need to 
modify the amanda-server Makefile to list "amanda" (or whomever) as your 
tape operator.
It is not necessary to modify the Makefile. Many configuration 
parameters that you'd want to specify when building Amanda directly from 
source tarball can be passed to port on the command line. You'd use 
something like:

cd /usr/ports/misc/amanda-server && make AMANDA_USER=amanda install

Re: all estimate failed error on amanda client

[rray]

On Sat, 8 Jan 2005, David Newman wrote:

>
>
>
> On 1/8/05 3:14 PM, "Gene Heskett" <[EMAIL PROTECTED]> wrote:
>
> > On Saturday 08 January 2005 17:19, David Newman wrote:
> >> On Fri, 7 Jan 2005, Gene Heskett wrote:
> >>> On Thursday 06 January 2005 21:25, David Newman wrote:
>   Greetings. I have installed Amanda on two FreeBSD 5.2.1 boxes,
>  Host A and Host B. Host A is the Amanda server, and has the
>  amanda-server package installed from ports. Host B has the
>  amanda-client package. I've added a couple of Host B's partitions
>  in Host A's disklist.
> 
>  I'm getting this error in the nightly Amanda reports:
> 
>  hostb /usr/home lev 0 FAILED [disk /usr/home, all estimate
>  failed] hostb /var lev 0 FAILED [disk /var, all estimate failed]
> 
>  The backups on host A are working fine. On the client (host B)
>  I've followed the directions here:
> 
>  http://amanda.sourceforge.net/docs/install.html#id2539781
> 
>  There is no firewall or other external impediment between the two
>  boxes.
> 
>  Both boxes run amanda as user "operator" which by default in
>  FreeBSD has no home directory. I have placed identical
>  .amandahosts files in the root directory of both boxes.
> 
>  Any clues as to why backups of Host B are failing?
> 
>  thanks
> 
>  dn
> >>>
> >>> Are there any logs being generated on host B from amanda's
> >>> activities?
> >>>
> >>> You may have to change the operator to a user with a valid home
> >>> dir. I've always, from day one, had a user amanda, who was a
> >>> member of group disk.
> >>
> >> Thanks, I think this was the problem.
>
> Sorry, spoke too soon. The new configuration with amanda users passed
> amcheck but attempts to dump the client machine ("Host B" from my first
> email) still result in the "all estimate failed" error.
>
> In disklist on the amanda server, I specify directories rather than
> partition names to be backed up:
>
> hostb.example.com /dir1 comp-user
> hostb.example.com /dir2 comp-user
>
> And on the client machine, the debug logs in /tmp/amanda are complaining
> that /dir1 is unknown:
>
> sendsize[5334]: time 0.015: calculating for device '/dir1' with
> ''
> sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 - /dir1"
> sendsize[5334]: time 0.017: running /usr/local/libexec/amanda/killpgrp
> sendsize[5334]: time 0.044: dump: /dir1: unknown file system
>
> Does amanda only back up entire partitions and not individual directories?
>
> Curtis Preston's backup book suggests (p. 164) that disklist can contain
> logical names like /usr (which in many Linux distros would be a directory
> and not a separate partition).  But the amanda manpage says it's gotta be a
> mount point.
>
> So -- does amanda work only on whole partitions, or is there some way I can
> use it to back up only selected directories?
>
> many thanks
>
> dn

I'm new to amanda but I've been administering UNIX servers for a while.
Dump is for dumping whole filesystems not directories. Tar is more
versatile. I believe in the amanda.conf you can specify DUMP or GNUTAR as
the dump mechanism. If you used GNUTAR you'll be able to dump only
directories.

Richard Ray

>
>
>
>
> from amandad.20050108140343000.debug:
>
> Amanda 2.4 REP HANDLE 001-005D0508 SEQ 1105221838
> OPTIONS features=feff9ffe0f;
> /dir1 0 SIZE -1
> /dir2 0 SIZE -1
> 
>
> from sendsize.20050108140343.debug:
>
> sendsize: debug 1 pid 5332 ruid 1021 euid 1021: start at Sat Jan  8 14:03:43
> 200
> 5
> sendsize: version 2.4.4p4
> sendsize[5332]: time 0.009: waiting for any estimate child: 1 running
> sendsize[5334]: time 0.010: calculating for amname '/dir1', dirname '/dir1',
> spindle -1
> sendsize[5334]: time 0.010: getting size via dump for /dir1 level 0
> sendsize[5334]: time 0.015: calculating for device '/dir1' with
> ''
> sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 - /dir1"
> sendsize[5334]: time 0.017: running /usr/local/libexec/amanda/killpgrp
> sendsize[5334]: time 0.044: dump: /dir1: unknown file system
> sendsize[5334]: time 0.046: .
> sendsize[5334]: estimate time for /dir1 level 0: 0.030
> sendsize[5334]: no size line match in /sbin/dump output for "/dir1"
> sendsize[5334]: .
> sendsize: debug 1 pid 5332 ruid 1021 euid 1021: start at Sat Jan  8 14:03:43
> 200
> 5
> sendsize: version 2.4.4p4
> sendsize[5332]: time 0.009: waiting for any estimate child: 1 running
> sendsize[5334]: time 0.010: calculating for amname '/dir1', dirname '/dir1',
> spindle -1
> sendsize[5334]: time 0.010: getting size via dump for /dir1 level 0
> sendsize[5334]: time 0.015: calculating for device '/dir1' with ''
> sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 - /dir1"
> sendsize[5334]: time 0.017: running /usr/local/libexec/amanda/killpgrp
> sendsize[5334]: time 0.044: dump: /var/named/etc/namedb: unknown file system
> sendsize[5334]: time 0.046: .
> sendsize[5334]: estima

Re: all estimate failed error on amanda client

[Gene Heskett]

On Sunday 09 January 2005 00:09, David Newman wrote:
>On 1/8/05 3:14 PM, "Gene Heskett" <[EMAIL PROTECTED]> wrote:
>> On Saturday 08 January 2005 17:19, David Newman wrote:
>>> On Fri, 7 Jan 2005, Gene Heskett wrote:
 On Thursday 06 January 2005 21:25, David Newman wrote:
>  Greetings. I have installed Amanda on two FreeBSD 5.2.1 boxes,
>
> Host A and Host B. Host A is the Amanda server, and has the
> amanda-server package installed from ports. Host B has the
> amanda-client package. I've added a couple of Host B's
> partitions in Host A's disklist.
>
> I'm getting this error in the nightly Amanda reports:
>
> hostb /usr/home lev 0 FAILED [disk /usr/home, all estimate
> failed] hostb /var lev 0 FAILED [disk /var, all estimate
> failed]
>
> The backups on host A are working fine. On the client (host B)
> I've followed the directions here:
>
> http://amanda.sourceforge.net/docs/install.html#id2539781
>
> There is no firewall or other external impediment between the
> two boxes.
>
> Both boxes run amanda as user "operator" which by default in
> FreeBSD has no home directory. I have placed identical
> .amandahosts files in the root directory of both boxes.
>
> Any clues as to why backups of Host B are failing?
>
> thanks
>
> dn

 Are there any logs being generated on host B from amanda's
 activities?

 You may have to change the operator to a user with a valid home
 dir. I've always, from day one, had a user amanda, who was a
 member of group disk.
>>>
>>> Thanks, I think this was the problem.
>
>Sorry, spoke too soon. The new configuration with amanda users
> passed amcheck but attempts to dump the client machine ("Host B"
> from my first email) still result in the "all estimate failed"
> error.
>
>In disklist on the amanda server, I specify directories rather than
>partition names to be backed up:
>
>hostb.example.com /dir1 comp-user
>hostb.example.com /dir2 comp-user
>
>And on the client machine, the debug logs in /tmp/amanda are
> complaining that /dir1 is unknown:
>
>sendsize[5334]: time 0.015: calculating for device '/dir1' with
>''
>sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 -
> /dir1" sendsize[5334]: time 0.017: running
> /usr/local/libexec/amanda/killpgrp sendsize[5334]: time 0.044:
> dump: /dir1: unknown file system
>
>Does amanda only back up entire partitions and not individual
> directories?

dump can only backup entire filesystems.  If /dir1 is just a 
directory, then you must use gnutar.

>Curtis Preston's backup book suggests (p. 164) that disklist can
> contain logical names like /usr (which in many Linux distros would
> be a directory and not a separate partition).  But the amanda
> manpage says it's gotta be a mount point.
>
>So -- does amanda work only on whole partitions, or is there some
> way I can use it to back up only selected directories?

As above, dump works only on whole filesystems from the mountpoint, 
tar can reach into subdirs and do most anything you want.  The tar 
version should be either 1.13-19 or 1.13-25, its known that the new 
1.14 is broken.
>
>many thanks
>
>dn
>
>
>
>
>from amandad.20050108140343000.debug:
>
>Amanda 2.4 REP HANDLE 001-005D0508 SEQ 1105221838
>OPTIONS features=feff9ffe0f;
>/dir1 0 SIZE -1
>/dir2 0 SIZE -1
>
>
>from sendsize.20050108140343.debug:
>
>sendsize: debug 1 pid 5332 ruid 1021 euid 1021: start at Sat Jan  8
> 14:03:43 200
>5
>sendsize: version 2.4.4p4
>sendsize[5332]: time 0.009: waiting for any estimate child: 1
> running sendsize[5334]: time 0.010: calculating for amname '/dir1',
> dirname '/dir1', spindle -1
>sendsize[5334]: time 0.010: getting size via dump for /dir1 level 0
>sendsize[5334]: time 0.015: calculating for device '/dir1' with
>''
>sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 -
> /dir1" sendsize[5334]: time 0.017: running
> /usr/local/libexec/amanda/killpgrp sendsize[5334]: time 0.044:
> dump: /dir1: unknown file system sendsize[5334]: time 0.046: .
>sendsize[5334]: estimate time for /dir1 level 0: 0.030
>sendsize[5334]: no size line match in /sbin/dump output for "/dir1"
>sendsize[5334]: .
>sendsize: debug 1 pid 5332 ruid 1021 euid 1021: start at Sat Jan  8
> 14:03:43 200
>5
>sendsize: version 2.4.4p4
>sendsize[5332]: time 0.009: waiting for any estimate child: 1
> running sendsize[5334]: time 0.010: calculating for amname '/dir1',
> dirname '/dir1', spindle -1
>sendsize[5334]: time 0.010: getting size via dump for /dir1 level 0
>sendsize[5334]: time 0.015: calculating for device '/dir1' with ''
>sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 -
> /dir1" sendsize[5334]: time 0.017: running
> /usr/local/libexec/amanda/killpgrp sendsize[5334]: time 0.044:
> dump: /var/named/etc/namedb: unknown file system sendsize[5334]:
> time 0.046: .
>sendsize[5334]: estimate time for /dir1 level 0: 0.030
>sendsize[53

Re: all estimate failed error on amanda client

[David Newman]

On 1/8/05 3:14 PM, "Gene Heskett" <[EMAIL PROTECTED]> wrote:

> On Saturday 08 January 2005 17:19, David Newman wrote:
>> On Fri, 7 Jan 2005, Gene Heskett wrote:
>>> On Thursday 06 January 2005 21:25, David Newman wrote:
  Greetings. I have installed Amanda on two FreeBSD 5.2.1 boxes,
 Host A and Host B. Host A is the Amanda server, and has the
 amanda-server package installed from ports. Host B has the
 amanda-client package. I've added a couple of Host B's partitions
 in Host A's disklist.
 
 I'm getting this error in the nightly Amanda reports:
 
 hostb /usr/home lev 0 FAILED [disk /usr/home, all estimate
 failed] hostb /var lev 0 FAILED [disk /var, all estimate failed]
 
 The backups on host A are working fine. On the client (host B)
 I've followed the directions here:
 
 http://amanda.sourceforge.net/docs/install.html#id2539781
 
 There is no firewall or other external impediment between the two
 boxes.
 
 Both boxes run amanda as user "operator" which by default in
 FreeBSD has no home directory. I have placed identical
 .amandahosts files in the root directory of both boxes.
 
 Any clues as to why backups of Host B are failing?
 
 thanks
 
 dn
>>> 
>>> Are there any logs being generated on host B from amanda's
>>> activities?
>>> 
>>> You may have to change the operator to a user with a valid home
>>> dir. I've always, from day one, had a user amanda, who was a
>>> member of group disk.
>> 
>> Thanks, I think this was the problem.

Sorry, spoke too soon. The new configuration with amanda users passed
amcheck but attempts to dump the client machine ("Host B" from my first
email) still result in the "all estimate failed" error.

In disklist on the amanda server, I specify directories rather than
partition names to be backed up:

hostb.example.com /dir1 comp-user
hostb.example.com /dir2 comp-user

And on the client machine, the debug logs in /tmp/amanda are complaining
that /dir1 is unknown:

sendsize[5334]: time 0.015: calculating for device '/dir1' with
''
sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 - /dir1"
sendsize[5334]: time 0.017: running /usr/local/libexec/amanda/killpgrp
sendsize[5334]: time 0.044: dump: /dir1: unknown file system

Does amanda only back up entire partitions and not individual directories?

Curtis Preston's backup book suggests (p. 164) that disklist can contain
logical names like /usr (which in many Linux distros would be a directory
and not a separate partition).  But the amanda manpage says it's gotta be a
mount point.

So -- does amanda work only on whole partitions, or is there some way I can
use it to back up only selected directories?

many thanks

dn




from amandad.20050108140343000.debug:

Amanda 2.4 REP HANDLE 001-005D0508 SEQ 1105221838
OPTIONS features=feff9ffe0f;
/dir1 0 SIZE -1
/dir2 0 SIZE -1


from sendsize.20050108140343.debug:

sendsize: debug 1 pid 5332 ruid 1021 euid 1021: start at Sat Jan  8 14:03:43
200
5
sendsize: version 2.4.4p4
sendsize[5332]: time 0.009: waiting for any estimate child: 1 running
sendsize[5334]: time 0.010: calculating for amname '/dir1', dirname '/dir1',
spindle -1
sendsize[5334]: time 0.010: getting size via dump for /dir1 level 0
sendsize[5334]: time 0.015: calculating for device '/dir1' with
''
sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 - /dir1"
sendsize[5334]: time 0.017: running /usr/local/libexec/amanda/killpgrp
sendsize[5334]: time 0.044: dump: /dir1: unknown file system
sendsize[5334]: time 0.046: .
sendsize[5334]: estimate time for /dir1 level 0: 0.030
sendsize[5334]: no size line match in /sbin/dump output for "/dir1"
sendsize[5334]: .
sendsize: debug 1 pid 5332 ruid 1021 euid 1021: start at Sat Jan  8 14:03:43
200
5
sendsize: version 2.4.4p4
sendsize[5332]: time 0.009: waiting for any estimate child: 1 running
sendsize[5334]: time 0.010: calculating for amname '/dir1', dirname '/dir1',
spindle -1
sendsize[5334]: time 0.010: getting size via dump for /dir1 level 0
sendsize[5334]: time 0.015: calculating for device '/dir1' with ''
sendsize[5334]: time 0.015: running "/sbin/dump 0Shsf 0 1048576 - /dir1"
sendsize[5334]: time 0.017: running /usr/local/libexec/amanda/killpgrp
sendsize[5334]: time 0.044: dump: /var/named/etc/namedb: unknown file system
sendsize[5334]: time 0.046: .
sendsize[5334]: estimate time for /dir1 level 0: 0.030
sendsize[5334]: no size line match in /sbin/dump output for "/dir1"
sendsize[5334]: .
sendsize[5334]: estimate size for /var/named/etc/namedb level 0: -1 KB
sendsize[5334]: time 0.046: asking killpgrp to terminate
sendsize[5334]: time 1.051: done with amname '/dir1', dirname '/dir1',
spindle -1
sendsize[5332]: time 1.052: child 5334 terminated normally

...and then the same thing again for /dir2.

What's going on? The tape operator has read permissions on both /dir1 and
/dir2. And  

Re: all estimate failed error on amanda client

[Gene Heskett]

On Saturday 08 January 2005 17:19, David Newman wrote:
>On Fri, 7 Jan 2005, Gene Heskett wrote:
>> On Thursday 06 January 2005 21:25, David Newman wrote:
>>> Greetings. I have installed Amanda on two FreeBSD 5.2.1 boxes,
>>> Host A and Host B. Host A is the Amanda server, and has the
>>> amanda-server package installed from ports. Host B has the
>>> amanda-client package. I've added a couple of Host B's partitions
>>> in Host A's disklist.
>>>
>>> I'm getting this error in the nightly Amanda reports:
>>>
>>> hostb /usr/home lev 0 FAILED [disk /usr/home, all estimate
>>> failed] hostb /var lev 0 FAILED [disk /var, all estimate failed]
>>>
>>> The backups on host A are working fine. On the client (host B)
>>> I've followed the directions here:
>>>
>>> http://amanda.sourceforge.net/docs/install.html#id2539781
>>>
>>> There is no firewall or other external impediment between the two
>>> boxes.
>>>
>>> Both boxes run amanda as user "operator" which by default in
>>> FreeBSD has no home directory. I have placed identical
>>> .amandahosts files in the root directory of both boxes.
>>>
>>> Any clues as to why backups of Host B are failing?
>>>
>>> thanks
>>>
>>> dn
>>
>> Are there any logs being generated on host B from amanda's
>> activities?
>>
>> You may have to change the operator to a user with a valid home
>> dir. I've always, from day one, had a user amanda, who was a
>> member of group disk.
>
>Thanks, I think this was the problem. I've created "amanda" accounts
> on both machines and they now communicate.
>
>Note to those installing from the BSD ports collection: You'll need
> to modify the amanda-server Makefile to list "amanda" (or whomever)
> as your tape operator.

Unforch, I'm not familiar with the 'ports' of BSD.  However, all this 
is normally specified when the configuration script is run from a 
tarball install.  Here is mine:

#!/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 user amanda,"
 echo "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-tapedev="FILE:/amandatapes" \
 --with-debugging=/tmp/amanda-dbg/ \
 --with-tape-server=coyote.coyote.den \
 --with-amandahosts \
 --with-configdir=/usr/local/etc/amanda

make
-
I run this on any new snapshot Jean-Louis puts up, and when this is 
done, I become root again and do the make install, and an ldconfig to 
bring the library linkages up to date.

I can install a new tarball in about 5 minutes on this linux box.

>
>However, the problem may also have been that I was using a CNAME
> rather than the canonical hostname for the client in .amandahosts.
> I don't know which of these two fixed the comm problem.
>
>By the way, I set up the same password for the amanda accounts on
> both machines. Is this required? I don't see anything in the
> commands about passwords being used at all.
>
>dn

The ~/amanda/.amandahosts file only needs the FQDN of the machine, and 
the user in it.  Or at least thats all there is in mine:


-- 
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)
99.31% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: all estimate failed error on amanda client

[David Newman]

On Fri, 7 Jan 2005, Gene Heskett wrote:
On Thursday 06 January 2005 21:25, David Newman wrote:
Greetings. I have installed Amanda on two FreeBSD 5.2.1 boxes, Host
A and Host B. Host A is the Amanda server, and has the
amanda-server package installed from ports. Host B has the
amanda-client package. I've added a couple of Host B's partitions
in Host A's disklist.
I'm getting this error in the nightly Amanda reports:
hostb /usr/home lev 0 FAILED [disk /usr/home, all estimate failed]
hostb /var lev 0 FAILED [disk /var, all estimate failed]
The backups on host A are working fine. On the client (host B) I've
followed the directions here:
http://amanda.sourceforge.net/docs/install.html#id2539781
There is no firewall or other external impediment between the two
boxes.
Both boxes run amanda as user "operator" which by default in FreeBSD
has no home directory. I have placed identical .amandahosts files
in the root directory of both boxes.
Any clues as to why backups of Host B are failing?
thanks
dn
Are there any logs being generated on host B from amanda's activities?
You may have to change the operator to a user with a valid home dir.
I've always, from day one, had a user amanda, who was a member of
group disk.
Thanks, I think this was the problem. I've created "amanda" accounts on 
both machines and they now communicate.

Note to those installing from the BSD ports collection: You'll need to 
modify the amanda-server Makefile to list "amanda" (or whomever) as your 
tape operator.

However, the problem may also have been that I was using a CNAME rather 
than the canonical hostname for the client in .amandahosts. I don't know 
which of these two fixed the comm problem.

By the way, I set up the same password for the amanda accounts on both 
machines. Is this required? I don't see anything in the commands about 
passwords being used at all.

dn
And is host B using inetd or xinetd?
--
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)
99.31% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

Re: all estimate failed error on amanda client

[Gene Heskett]

On Thursday 06 January 2005 21:25, David Newman wrote:
>Greetings. I have installed Amanda on two FreeBSD 5.2.1 boxes, Host
> A and Host B. Host A is the Amanda server, and has the
> amanda-server package installed from ports. Host B has the
> amanda-client package. I've added a couple of Host B's partitions
> in Host A's disklist.
>
>I'm getting this error in the nightly Amanda reports:
>
>hostb /usr/home lev 0 FAILED [disk /usr/home, all estimate failed]
>hostb /var lev 0 FAILED [disk /var, all estimate failed]
>
>The backups on host A are working fine. On the client (host B) I've
>followed the directions here:
>
>http://amanda.sourceforge.net/docs/install.html#id2539781
>
>There is no firewall or other external impediment between the two
> boxes.
>
>Both boxes run amanda as user "operator" which by default in FreeBSD
> has no home directory. I have placed identical .amandahosts files
> in the root directory of both boxes.
>
>Any clues as to why backups of Host B are failing?
>
>thanks
>
>dn

Are there any logs being generated on host B from amanda's activities?

You may have to change the operator to a user with a valid home dir.  
I've always, from day one, had a user amanda, who was a member of 
group disk.

And is host B using inetd or xinetd?

-- 
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)
99.31% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

Re: "all estimate failed"

[Gene Heskett]

On Monday 12 July 2004 18:21, [EMAIL PROTECTED] wrote:
>Gene, thanks for your help.  I finally seem to be on the track of
> fixing the problem.  I completely nuked amanda and let Gentoo
> rebuild it from scratch, after providing the ebuild with the proper
> env vars.  This didn't help, but it gave me a clean slate.
>
>After that, I rewrote my amanda.conf and disklist files for the
> affected configs using the templates provided with the current
> version of amanda (my old configs have been in use for about 5
> years, through several versions of amanda, and were somewhat hacked
> and outdated).  I'm not sure exactly which parameter(s) made the
> difference, but a backup of the main local system seems to be
> proceeding well.
>
>I note that the Gentoo build defaults to 'localhost' for the server
> address, which should _always_ be 127.0.0.1, and hence unambiguous.
>  I trust the Gentoo devs implicitly.  IMHO, they're right up there
> with the Debian package maintainers in knowledge and experience.  I
> did, however, use the FQDN for the server in the ebuild, which I
> prefer in any event.

The huge majority of the amanda users here, and even Jean-Louis, will 
re-iterate about not using localhost because its not a unique name.  
The problem being that the data can be taken to any machine that is 
also localhost and installed.  This is, among other things, a huge 
security hole.

I'm not sure how the ebuilder works, but from the tarballs unpacking, 
to a fully installed update here is not more than 5 to 6 minutes 
unless you use the checkinstall utility to install it on an rpm based 
system.  Checkinstall can be handy in that you do the standard 
routine of unpack, cd to the unpacked directory, ./configure; make, 
doing this as the user amanda, then revert to root or become root, 
and do the make install or the checkinstall.  Checkinstall takes the 
packages built directory, makes a binary rpm out of it, and then 
installs the rpm.  One can then remove an errant package with the rpm 
-e command should it become required.

Configureing the tarball to make it can be confusing, and error prone 
if you don't have a photographic memory, so I only do these steps to 
build and install it:

(1) tar xzvf name_of_tarball
(2) cp gh.cf name_of_tarball/
(3) chown -R amanda:disk name_of_tarball
(4) become the user 'amanda'
(5) cd name_of_tarball(minus the tar.gz of course)
(6) ./gh.cf (which configures it with my std config options, then 
'make's it)
(7) become root
(8) cd name_of_tarball
(9) make install
(10) become user amanda
(11) amcheck configname (to error check the install)

Steps 1-9 take about 5 minutes here.

Here is that gh.cf file:

#!/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 user amanda,"
echo "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-tape-device=/dev/nst0 \
--with-changer-device=/dev/sg1 \
--with-gnu-ld --prefix=/usr/local \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=coyote.coyote.den \
--with-amandahosts \
--with-configdir=/usr/local/etc/amanda

make
--- 
I didn't sanitize it any, that hostname won't resolve more than 100 
feet away in my woodshop, as my firewall is bulletproof in practice.
Adjust your changer device if required.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: "all estimate failed"

[Matt Hyclak]

On Mon, Jul 12, 2004 at 05:21:40PM -0500, [EMAIL PROTECTED] enlightened us:
> I note that the Gentoo build defaults to 'localhost' for the server address,
> which should _always_ be 127.0.0.1, and hence unambiguous.  I trust the
> Gentoo devs implicitly.  IMHO, they're right up there with the Debian
> package maintainers in knowledge and experience.  I did, however, use the
> FQDN for the server in the ebuild, which I prefer in any event.

It is not unambiguous since *every* machine is localhost with an address of
127.0.0.1. Unfortunately that's a problem with binary packages and amanda in
that yes, backing up with localhost/127.0.0.1 will always work, but it can
fail at restore time and can cause other crazy problems occasionally. It is
the same situation in the redhat packages, which is why I always grab the
source rpm and rebuild with the right options for my server. Sounds like
that's what you did and is IMHO the best way to do it if you want to keep
the tracking of packages while using amanda in the best manner.

Matt

-- 
Matt Hyclak
Department of Mathematics 
Department of Social Work
Ohio University
(740) 593-1263

Re: "all estimate failed"

[fmouse-amanda]

Gene, thanks for your help.  I finally seem to be on the track of fixing the
problem.  I completely nuked amanda and let Gentoo rebuild it from scratch,
after providing the ebuild with the proper env vars.  This didn't help, but
it gave me a clean slate.

After that, I rewrote my amanda.conf and disklist files for the affected
configs using the templates provided with the current version of amanda (my
old configs have been in use for about 5 years, through several versions of
amanda, and were somewhat hacked and outdated).  I'm not sure exactly which
parameter(s) made the difference, but a backup of the main local system
seems to be proceeding well.

I note that the Gentoo build defaults to 'localhost' for the server address,
which should _always_ be 127.0.0.1, and hence unambiguous.  I trust the
Gentoo devs implicitly.  IMHO, they're right up there with the Debian
package maintainers in knowledge and experience.  I did, however, use the
FQDN for the server in the ebuild, which I prefer in any event.

-- 
Lindsay Haisley   | "Everything works| PGP public key
FMP Computer Services |   if you let it" |  available at
512-259-1190  |(The Roadie)  | 
http://www.fmp.com|  |

Re: "all estimate failed"

[Gene Heskett]

On Sunday 11 July 2004 21:02, Jon LaBadie wrote:
>On Sun, Jul 11, 2004 at 05:21:55PM -0500, [EMAIL PROTECTED] 
wrote:
>> > BTW there are logfiles being kept, fairly verbose ones at that,
>> > whereever you have it set to in your amanda.conf, or in the
>> > default dir, probably in /var/amanda-dbg or similar.  They will
>> > tell you a lot more precisely what is going on.
>> > gentoo.
>>
>> I know about the amanda logfiles, and they're uninformative.  For
>> instance,
>>
>> /var/log/amanda/Fmouse# cat log.20040711.2
>> DISK planner vishnu /dev/fasttrak/fmouse_gen
>
>...
>
>> FINISH driver date 20040711 time 30.142
>>
>> "all estimate failed", which is where I started with this.
>> I'm looking for a reason _why_ "all estimate failed" and this
>> doesn't help, nor are there any other logfiles which help.
>
>Do you have the /var/amanda-dbg directory that Gene mentioned
>and you overlooked.  In my case it is /tmp/amanda.  In that
>directory is where debuging logfiles are placed by amanda.
>Gene was not refering to the "logs", but the debug logs.

I didn't make myself clear enough on that I guess. :(

That said, I've dug as deep as I feel comfortable with, so jump right 
in Jon and see if you can help out.

There is also an env var that can be set which will multiply the 
verbosity of the debugging logs considerably.  But I haven't used it 
in ages, so I don't know the name or the exact syntax to use it.  
There could be a reference to it in the docs dir of the archive.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: "all estimate failed"

[Jon LaBadie]

On Sun, Jul 11, 2004 at 05:21:55PM -0500, [EMAIL PROTECTED] wrote:
>  
> > BTW there are logfiles being kept, fairly verbose ones at that, 
> > whereever you have it set to in your amanda.conf, or in the default 
> > dir, probably in /var/amanda-dbg or similar.  They will tell you a 
> > lot more precisely what is going on.
> > gentoo.
> > 
> 
> I know about the amanda logfiles, and they're uninformative.  For instance, 
> 
> /var/log/amanda/Fmouse# cat log.20040711.2
> DISK planner vishnu /dev/fasttrak/fmouse_gen
...
> FINISH driver date 20040711 time 30.142
> 
> "all estimate failed", which is where I started with this.
> I'm looking for a reason _why_ "all estimate failed" and this
> doesn't help, nor are there any other logfiles which help.
> 

Do you have the /var/amanda-dbg directory that Gene mentioned
and you overlooked.  In my case it is /tmp/amanda.  In that
directory is where debuging logfiles are placed by amanda.
Gene was not refering to the "logs", but the debug logs.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: "all estimate failed"

[fmouse-amanda]

Thus spake Gene Heskett on Sun, Jul 11, 2004 at 04:49:03PM CDT
> On Sunday 11 July 2004 17:04, [EMAIL PROTECTED] wrote:
> >Thus spake Gene Heskett on Sun, Jul 11, 2004 at 03:10:06PM CDT
> 
> BTW, I've been Cc: in the list as this really should be a public 
> exchange.  Thats what the list is for, and its searchable I believe.

Sorry.  Dealing with Majordomo lists is a PITA, and I didn't notice the CC
either.  THis one's cc'd.
 
> BTW there are logfiles being kept, fairly verbose ones at that, 
> whereever you have it set to in your amanda.conf, or in the default 
> dir, probably in /var/amanda-dbg or similar.  They will tell you a 
> lot more precisely what is going on.  I'd start there rather than on 
> gentoo.
> 
> 
> >I'll check with the Gentoo devs and see if any of them have any
> > experience with this sort of thing.

I know about the amanda logfiles, and they're uninformative.  For instance, 

/var/log/amanda/Fmouse# cat log.20040711.2
DISK planner vishnu /dev/fasttrak/fmouse_gen
DISK planner vishnu hda1
START planner date 20040711
WARNING planner tapecycle (5) <= runspercycle (28)
START driver date 20040711
INFO planner Adding new disk vishnu:hda1.
FAIL planner vishnu hda1 20040711 0 [disk hda1, all estimate failed]
FAIL planner vishnu /dev/fasttrak/fmouse_gen 20040711 0 [disk
/dev/fasttrak/fmouse_gen, all estimate failed]
FINISH planner date 20040711
WARNING driver WARNING: got empty schedule from planner
STATS driver startup time 17.290
ERROR taper no-tape [rewinding tape: No medium found]
FINISH driver date 20040711 time 30.142

"all estimate failed", which is where I started with this.  I'm looking for
a reason _why_ "all estimate failed" and this doesn't help, nor are there
any other logfiles which help.

Believe me, Gene, I didn't fall off the turnip truck yesterday on this
stuff.  I've been doing professional system administration for many years
and I've been to all the obvious places on this looking for clues.  I know
how to segregate a problem on the basis of clues, and set up test situations
and deduce something about what the problem is _not_, which I've done here,
but I'm up against a stone wall and am looking for information on were I
might go that I haven't already gone.

-- 
Lindsay Haisley   | "Everything works| PGP public key
FMP Computer Services |   if you let it" |  available at
512-259-1190  |(The Roadie)  | 
http://www.fmp.com|  |

Re: "all estimate failed"

[Gene Heskett]

On Sunday 11 July 2004 17:04, [EMAIL PROTECTED] wrote:
>Thus spake Gene Heskett on Sun, Jul 11, 2004 at 03:10:06PM CDT

BTW, I've been Cc: in the list as this really should be a public 
exchange.  Thats what the list is for, and its searchable I believe.

>> The clues point to  serious slowdown someplace.
>>
>> >I'll take a look for the TOP-TEN-QUESTIONS FAQ and see if it
>> > helps, but I'm guessing that it probably won't.  I'm wondering
>> > if this is some kind of kernel issue or something equally weird.
>>
>> The only other item that comes to mind is the etimeout value in
>> your amanda.conf.  Just for testing, multiply it by 10 for
>> tonight, that big a filesystem may be too slow for the default 5
>> minutes.  Its in seconds BTW.  If that fixes the estimates, you
>> may have to expand the dtimeout value also.
>
>The time to failure is about 50 seconds, with etimeout set to 600
> seconds, so it's not a slowdown or timeout issue unless there's
> some other timeing factor involved.  I really wish there were
> better logging for this kind of thing.  Running it under strace
> _might_ help.

BTW there are logfiles being kept, fairly verbose ones at that, 
whereever you have it set to in your amanda.conf, or in the default 
dir, probably in /var/amanda-dbg or similar.  They will tell you a 
lot more precisely what is going on.  I'd start there rather than on 
gentoo.


>I'll check with the Gentoo devs and see if any of them have any
> experience with this sort of thing.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: "all estimate failed"

[Gene Heskett]

On Sunday 11 July 2004 15:49, [EMAIL PROTECTED] wrote:
>Thus spake Gene Heskett on Sun, Jul 11, 2004 at 04:29:31AM CDT
>
>> On Sunday 11 July 2004 03:11, [EMAIL PROTECTED] wrote:
>> >I use amanda successfully to back up a number of systems
>> > remotely, one via VPN across the Internet.  I'm having trouble,
>> > however, with my local system (also the amanda server host)
>> > where it seems to be difficult to get any backups to work.  The
>> > box is running Gentoo Linux, xinetd, Amanda version 2.4.4p2,
>> > Linux kernel 2.4.20.  A typical report shows:
>> >
>> >FAILURE AND STRANGE DUMP SUMMARY:
>> >  vishnu hdb2 lev 0 FAILED [disk hdb2, all estimate failed]
>> >  vishnu hdb1 lev 0 FAILED [disk hdb1, all estimate failed]
>> >
>> >... and the backup fails.
>> >
>> >This particular notice is from a test backup on a drive with 2
>> >partitions, one ext2 and the other reiserfs.  The dumptype on
>> > both is comp-user or comp-user-tar.  All files and directories
>> > on both partitions are mode ugo+r.  The amanda xinetd config
>> > contains 'only-from' entries for both the private IP address of
>> > the box and 'localhost'.  /etc/amandahosts likewise contains
>> > entries for both the hostname of the box and 'localhost:
>> >
>> >$ cat /etc/amandahosts
>> >localhost amanda
>> >localhost root
>> >[snip snap!]
>> >vishnu.fmp.com amanda
>> >vishnu.fmp.com root
>> >
>> >Does anyone have any ideas what I might try to solve this
>> > problem?
>>
>> First, one should never use localhost, it is not a unique name,
>> and amanda must have unique, no mistaking which machine, names,
>> resolvable in the approriate /etc/hosts file (or by a local dns
>> server),
>
>It's unique on this box.
>
>$ dig +short localhost
>127.0.0.1

It _will_ bite you at some point.  Amanda is very very network aware.
Please use the FQDN of the machine even though that might resolve to a 
192.168.xx.xx address.

>No ambiguity there.
>
>> and likewise, the ~/.amandahosts file must be similarly
>> treated.  I note above that you didn't have the leading dot in the
>> filename you catted above.
>
>/etc/amandahosts doesn't use a leading dot.  ~amanda/.amandahosts
> does, and is a symlink to /etc/amandahosts.

Amanda was built as user:

and make install was done as user:

And its perms (~/.amandahosts) are?

>> This may not be your whole problem, but it will remove another
>> often encountered source of recovery time failures.  Please read
>> the TOP-TEN-QUESTIONS and FAQ in the tarball.
>
>This isn't a recovery-time issue, it's a backup-time issue.  I have
> no problem with either backup or recovery on any of the other
> systems I have for which I use amanda.
>
>The problem is more complex than this.  There is _one_ filesystem on
> this box with which amanda has no problems.  That's my boot
> partition, which is a small (c.a. 15 megs) ext2 boot partition
> which I _can_ back up.  It's both the smallest and least important
> partition on the box, but the fact that I can back it up tells me
> that the problem isn't one of access permissions or name
> resolution.  Amanda doesn't care about file permissions,
> apparently, since I can remove read permissions from all files on
> this partition and still back it up.
>
>Amstatus shows:
>
>vishnu:hda2 1 7810k dump done (14:35:22), wait for writing to
> tape vishnu:hda4 0 planner: [disk hda4, all estimate failed]
>
>hda2 succeeds, hda4 fails.  Both are set to a dumptype of
> 'nocomp-boot-tar' (not appropriate for hda4, but temporarily
> changing this eliminates a variable).  The only thing which
> distinguishes hda2 from any other filesystem on the box is it's
> small size.  I tried a test backup on a spare drive, mounted
> temporarily with two nearly identical sets of files on nearly
> identically sized partitions (c.a. 1.5G), one ext2 and one
> reiserfs, and both failed, which eliminates the filesystem type,
> apparently.  Amanda has no problem getting estimates on and backup
> up filesystems many times this size on other boxes.

The clues point to  serious slowdown someplace.

>I'll take a look for the TOP-TEN-QUESTIONS FAQ and see if it helps,
> but I'm guessing that it probably won't.  I'm wondering if this is
> some kind of kernel issue or something equally weird.

The only other item that comes to mind is the etimeout value in your 
amanda.conf.  Just for testing, multiply it by 10 for tonight, that 
big a filesystem may be too slow for the default 5 minutes.  Its in 
seconds BTW.  If that fixes the estimates, you may have to expand the 
dtimeout value also.

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.