Re: parse of reply message failed

2004-11-05 Thread foo
On Fri, Nov 05, 2004 at 10:12:25AM +0100, Paul Bijnens wrote: [EMAIL PROTECTED] wrote: On Thu, Nov 04, 2004 at 04:11:18AM -0500, foo wrote: I was wrong, it turns out to be ip_conntrack_amanda from netfilter that's the culprit. I haven't tested yet, but others have confirmed it. I

Re: parse of reply message failed

2004-11-04 Thread foo
On Thu, Nov 04, 2004 at 09:48:23AM +0100, Paul Bijnens wrote: [EMAIL PROTECTED] wrote: On further inspection, it's a kernel problem - bad UDP checksums. I'll go bug them now. :) To avoid falling in the same trap, what kernel version was that? 2.6.9. I have a dozen other machines

Re: parse of reply message failed

2004-11-04 Thread foo
On Thu, Nov 04, 2004 at 04:11:18AM -0500, foo wrote: On Thu, Nov 04, 2004 at 09:48:23AM +0100, Paul Bijnens wrote: To avoid falling in the same trap, what kernel version was that? 2.6.9. I have a dozen other machines running 2.6.9 without this problem, though. I'm not 100% sure

parse of reply message failed

2004-11-03 Thread foo
I have a client that's been working fine for many months, and after I recently rebooted it to boot a newer version of the Linux kernel, I started getting this for all of its filesystems: FAILURE AND STRANGE DUMP SUMMARY: albarino / lev 2 FAILED [[parse of reply message failed]] No

Re: parse of reply message failed

2004-11-03 Thread foo
On Wed, Nov 03, 2004 at 10:49:37AM +0100, Paul Bijnens wrote: First, I don't find that errormessage in the sources of 2.4.4p3, the current stable version. So there are some changes since 2.4.2p2 that would change/solve that behaviour... (or at least produce a better error message). Also

Re: parse of reply message failed

2004-11-03 Thread foo
On further inspection, it's a kernel problem - bad UDP checksums. I'll go bug them now. :) Thanks, -ryan