Re: "netlink_lookup: write failed: Connection refused"
On 2006-07-05, Jim Seymour <[EMAIL PROTECTED]> wrote: > I added tcp_diag to the list of modules getting loaded at boot time. > That is the module it is looking for. I added it with modprobe and that seems to have fixed the problem. I'll add it to the boot configuration too. Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "netlink_lookup: write failed: Connection refused"
On 2006-07-05, Jim Seymour <[EMAIL PROTECTED]> wrote: >> identd[12299]: netlink_lookup: write failed: Connection refused > I added tcp_diag to the list of modules getting loaded at boot time. > That is the module it is looking for. Thanks, I'll try that and see if goes away. Having googled a bit more about this, I get the impression [1] that the bug was in pidentd version 3.0.18-2.Softlab-2 rather than in the kernel, but I've got 3.0.18-3, which should be fixed according to the bug-closing in [1]. Should I add this experience to bug #305926 to re-open it? (I'm reluctant to complain about things I don't really understand unless I get corroboration.) [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305926 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "netlink_lookup: write failed: Connection refused"
On Wed, 2006-07-05 at 15:21 +0100, Adam Funk wrote: > Since I upgraded to a 2.6 kernel a few months ago, I've been getting > this message from logcheck (from syslog) > > identd[12299]: netlink_lookup: write failed: Connection refused > > at irregular intervals (sometimes several times in an hours, sometimes > not for a few days). I've googled for it but haven't been able to > find an explanation of it. It doesn't seem to correlate with any > network problems and upgrading to a higher 2.6 kernel hasn't changed > it. > > Is it significant? Do I need to fix anything or should I just add it > to logcheck's ignore-rules? > Hi Alan, I added tcp_diag to the list of modules getting loaded at boot time. That is the module it is looking for. HTH, -- Jim Seymour <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
"netlink_lookup: write failed: Connection refused"
Since I upgraded to a 2.6 kernel a few months ago, I've been getting this message from logcheck (from syslog) identd[12299]: netlink_lookup: write failed: Connection refused at irregular intervals (sometimes several times in an hours, sometimes not for a few days). I've googled for it but haven't been able to find an explanation of it. It doesn't seem to correlate with any network problems and upgrading to a higher 2.6 kernel hasn't changed it. Is it significant? Do I need to fix anything or should I just add it to logcheck's ignore-rules? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
