Amanda-Users

Re: UPDATE: Still getting timeout: Long entry

2003-05-21 08:48:47
Subject: Re: UPDATE: Still getting timeout: Long entry
From: Paul Bijnens <paul.bijnens AT xplanation DOT com>
To: Rebecca Pakish Crum <rebecca AT unterlaw DOT com>
Date: Wed, 21 May 2003 14:44:11 +0200
Rebecca Pakish Crum wrote:
...
# more sendbackup.20030520043455.debug

sendbackup: debug 1 pid 8409 ruid 1003 euid 1003 start time Tue May 20
04:34:55 2003

Is it normal that the "sendbackup" starts more than 1 hour later then
the sendsize?   The estimate time is only a few minutes according to
your report below.

...[snip]... sendbackup: index created successfully

Normally I would expect after that line a line with the fishish datestamp. I'm not sure if amanda 2.4.2p2 generated that line too.
But you can find the finish time by looking at the mtime of the file
itself.

These dumps were to tape icleardaily01.
The next tape Amanda expects to use is: icleardaily01.

FAILURE AND STRANGE DUMP SUMMARY:
  www.iclear / lev 0 STRANGE


STATISTICS:
                          Total       Full      Daily
                        --------   --------   --------
Estimate Time (hrs:min)    0:01
Run Time (hrs:min)         3:35
Dump Time (hrs:min)        2:10       2:10       0:00

> ...[snip]...

These dumps were to tape isymmdaily07.
The next tape Amanda expects to use is: isymmdaily08.

FAILURE AND STRANGE DUMP SUMMARY:
  www.iclear / lev 0 FAILED [mesg read: Connection timed out]


STATISTICS:
                          Total       Full      Daily
                        --------   --------   --------
Estimate Time (hrs:min)    0:02
Run Time (hrs:min)         3:19
> ...[snip]...



And then something completely different.
Just a problem to investigate... (because it really strange!)
How big is your holding disk?
Is it big enough to hold all your images at once?
The failing system generates a backup of almost 5.5 GB.
I know amanda tries to avoid the following situation, but it could
run into (and I'm not sure how amanda 2.4.2p2 reacts) the situation
that it is dumping a DLE to disk, and the holdingdisk gets full.
In that case the dumps temporarily stop, amanda waits for taper to
finish some more DLE's, before the dumpers can continue with
transferring their data.  Could it be there is a timeout (in the
firewall) that closes idle connections after some time?
You should see some indication in the amdump.0 file (or amdump.1 for
previous runs etc) about holdingdisk contention.

--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* 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, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************



<Prev in Thread] Current Thread [Next in Thread>