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.
Sure, here's a new run this time with "-s 1500" so all packets will hopefully be intact. All files are in: ftp://zappa.cx/pub/amanda-zappa.cx-2.tar.gz
Notice that amdump.1 and log.20040615.6 resides in var/lib/amanda/dflt in my configuration.
/Andreas
