Hey people --
    When I add more disks to the disklist of a working test configuration,
amdump stops listening to the sendsize results.

Amdump is still waiting,   with amstatus saying  "getting estimate"...
the client finishes the sendsize,  tries to return the data,  and
finds nobody is listening:

amandad: dgram_recv: timeout after 10 seconds
amandad: waiting for ack: timeout, retrying
amandad: dgram_recv: timeout after 10 seconds
amandad: waiting for ack: timeout, retrying
amandad: dgram_recv: timeout after 10 seconds
amandad: waiting for ack: timeout, retrying
amandad: dgram_recv: timeout after 10 seconds
amandad: waiting for ack: timeout, retrying
amandad: dgram_recv: timeout after 10 seconds
amandad: waiting for ack: timeout, giving up!
amandad: pid 10266 finish time Thu Jun 27 11:57:04 2002

So the client's  amandad  has given up.

Meanwhile,   on the server,   amdump thinks it is still waiting
and will take another hour or so to reach the "etimeout 150"
and actually quit.

There are 41 disk entries on remote client,
times 2.5 minutes (150 seconds)  == 1 hr 42 minutes.
(if I understand etimeout correctly)
It took the client about 30 minutes to return the estimate,
but nobody was listening by then.   *BUT*   amdump
is still waiting.....

Where do I look now,   please?  Anybody?
(Mind you,  this DID work,  with a smaller number of
disk entries.  But I needed to test the tape changer use of >1
tape ..... so I added more entries.   This is how I eventually want
to run it.    If it'll run.....)

Deb Baddorf

--------
the bottom of amdump  (which hasn't timed out yet,
though the client found nobody to ACK it):

.....  top snipped .....
GETTING ESTIMATES...
driver: pid 9552 executable /usr/local/libexec/amanda/driver version 2.4.2p2
driver: send-cmd time 0.002 to taper: START-TAPER 20020627
taper: pid 9553 executable taper version 2.4.2p2
changer: opening pipe to: /usr/local/libexec/amanda/chg-multi -info
dumper: dgram_bind: socket bound to 0.0.0.0.960
dumper: pid 9562 executable dumper version 2.4.2p2, using port 960
driver: started dumper0 pid 9562
driver: started dumper1 pid 9564
driver: started dumper2 pid 9565
driver: started dumper3 pid 9566
dumper: dgram_bind: socket bound to 0.0.0.0.962
dumper: pid 9564 executable dumper version 2.4.2p2, using port 962
dumper: dgram_bind: socket bound to 0.0.0.0.963
dumper: pid 9565 executable dumper version 2.4.2p2, using port 963
dumper: dgram_bind: socket bound to 0.0.0.0.964
dumper: pid 9566 executable dumper version 2.4.2p2, using port 964
changer: got exit: 0 str: 3 7 0
changer_query: changer return was 7 0
changer_query: searchable = 0
changer_find: looking for bdbkTEST5-002 changer is searchable = 0
changer: opening pipe to: /usr/local/libexec/amanda/chg-multi -slot current
changer: got exit: 0 str: 3 /dev/nsa0
taper: slot 3: date 20020627 label bdbkTEST5-001 (active tape)
changer: opening pipe to: /usr/local/libexec/amanda/chg-multi -slot next
got result for host bdback.fnal.gov disk /var: 0 -> 1492K, -1 -> -1K, -1 -> -1K
got result for host bdback.fnal.gov disk /usr: 0 -> 388289K, -1 -> -1K, -1 
-> -1
K
got result for host bdback.fnal.gov disk /: 0 -> 43240K, -1 -> -1K, -1 -> -1K
changer: got exit: 0 str: 4 /dev/nsa0
taper: slot 4: date 20020625 label bdbkTEST5-002 (exact label match)
taper: read label `bdbkTEST5-002' date `20020625'
taper: wrote label `bdbkTEST5-002' date `20020627'

-------------------
Deb Baddorf         [EMAIL PROTECTED]              840-2289
"You can't help getting older, but you don't have to get old."
- George Burns                                          <IXOYE><



Reply via email to