Hi, Paul, on Dienstag, 15. Juni 2004 at 16:49 you wrote to amanda-users:
PB> And amanda cleans up the other two connections. PB> Amanda tries again with another set of ports a few times PB> but always trying to connect to 65535 for the index. PB> Then she gives up completely. I also noticed the strange usage of 65535 ... PB> Can you verify in the amandad.XXXX.log that the index connection PB> was indeed asked to port 50003? PB> The debug file looks like (search for string CONNECT): PB> ==== PB> Amanda 2.4 REP HANDLE 000-C8DC0608 SEQ 1087282569 PB> CONNECT DATA 32771 MESG 32772 INDEX 32773 PB> OPTIONS features=fffffeff9ffe0f; PB> ---- PB> Next thing to find out is who/why/when decided to connect to port PB> 65535 instead. Also note that number: all 1-bits 16-bit wide. PB> A kernel bug is indeed one of the possibilities. Where could that one reside? A faulty network-module? Remember that these things work fine here with each 2.6 .. Andreas, you could give me your .config, I will take a look ... Just to update me: You also tried this with 2.6.6? Have you tried to really start over with your kernel-tree? Did you get to 2.6.6 via patching or via downloading the whole tree? If patched, did you look for .rej-files? Did you use "make clean" or "make distclean"? Also the modules could be faulty ... any fancy network-hardware used? I would suggest a complete re-install of a vanilla 2.6.6-kernel and testing with this one. Doesn't make much sense to look for bugs in that rc in my opinion. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]