Hi Paul,
a 'amgetconf NewSetup etimeout' returns '900'. So, it seems to be
configured correctly.
I came to the conclusion that my server still waits for the estimate by
issuing the 'amstatus' command. It told me, that the server is still
'waiting for estimate' for one host, all other hosts were in 'estimate
done' state.
And last night I watched my backup running, and the timeout for that
host occured after exactly 1 hour, 15 minutes, and, be surprised, 4
seconds. Don't know, if theses 4 seconds are the same 4 seconds you can
see on your backup, I don't mind, but 1 hour and 15 minutes for sure is
more than 30 minutes, a.k.a. 900 sec times 2 DLEs.
For tonight I changed the etimeout value to -3600, so that the timeout
should occur after one hour. Just to see if this etimeout setting works
at all in my setup.
Thanks for your reply,
Ralf
Paul Bijnens schrieb:
> On 2007-09-04 01:16, Ralf Auer wrote:
>>
>> I have a little problem with the 'etimeout' setting in my
>> amanda.conf.
>> I have set 'etimeout' to 900. To my understanding this makes Amanda
>> wait for 15
>> minutes per DLE and client, then a timeout should occur.
>> For some reason this value seems to be ignored here, because for my buisy
>> clients Amanda still waits for the estimates after several hours! The
>> clients
>> have only two DLEs, so I would expect her to wait at max 30 Minutes,
>> not more.
>>
>> I'm using 2.5.2p1 version, everything else is doing fine, nothing
>> special to be
>> found in the log-files.
>>
>> Any ideas what I could have done wrong?
>
> I'm running 2.5.2p1 as well, and can assure that etimeout did work in
> my config. I had it set to 900 seconds, and last month had an etimeout
> occur on a host with 4 DLE's after 3600 seconds (irony was that the
> estimate took 3604 seconds -- 4 seconds too late!).
>
> How did you came to the conclusion that the server still waits for the
> estimates? amstatus? which output? of just the fact that amanda is
> still running? or...
>
> Another frequent "monday-morning-no-coffee-yet" problem encountered is
> that you're looking at the wrong config file, or etimeout appears twice
> in the config file. Verify with:
>
> amgetconf daily etimeout
>
> You can also set etimeout to a negative value, to avoid the
> multiplication of the number of DLE's by the etimeout value.
>
>
--
Ralf Auer
Physics Institute IV Office: 2.137
University of Erlangen-Nuremberg Phone: +49-9131-8527087
Erwin-Rommel-Str. 1 Fax: +49-9131-15249
D-91058 Erlangen, Germany Ralf.Auer AT physik.uni-erlangen DOT de
|
