Paul Bijnens wrote:

It seems ethereal store only the first few bytes of each packet.
There is probably an option to set that size; similar to "tcpdump -s 1500".
That means I don't have the full info, but I believe I've seen enough!

Following up on myself.
I've digged into the amanda source, and noticed there is only one
place where "bad CONNECT response" is actived.
That happens only for data or message tcp-connections.
But from the amdump.1 log file, it seems not always consistent, now
and then it is "bad CONNECT response", other times it is the index
that fails.
So it is not always the index that fails, as I concluded earlier.

Therefore I really would like to have a complete trace,
not cut off, together with the accompying amamdad.XXXX.debug
files + amdump.1, all from the same run.


--
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          *
***********************************************************************