udev unable to receive kernel netlink message

humbletech99 · 12-01-2006, 05:22 AM

I have the following error spewing all over my logs and causing big problems from the sheer number of logs (dozens if not hundreds per second!)

Code:

udevd[1019]: get_netlink_msg: unable to receive kernel netlink message: Socket operation on non-socket

I have tried recompiling my kernel with these compiled direcly into the kernel

Code:

General Settings --> 
  Export task/process statistics through netlink (EXPERIMENTAL)

and

Code:

Networking --> 
  Network Options --> 
    Network packet filtering (replaces ipchains) --> 
      Core Netfilter Configuration --> 
        Netfilter netlink interface
          Netfilter NFQUEUE over NFNETLINK interface
          Netfilter LOG over NFNETLINK interface

in order to try to make it stop, rebooted into new kernel but it still hasn't helped. I have only found one reference to this on the web which is where I got the idea to recompile the kernel with these settings (http://www.mail-archive.com/lfs-dev@...msg08651.html). I'm using udev-103.

This page http://www.ussg.iu.edu/hypermail/lin...11.3/0304.html says that I should have it enable with config_net by default but then why the heck is it complaining about this a million times a minute?

Any ideas on how to fix this?

pzYsTorM · 09-16-2008, 09:36 AM

Oh, yes, I have exactly the same problem - building a 2.6.26.3 Kernel.

But there is a 4th option which should be enabled. The CONFIG_CONNECTOR aka userspace <-> kernelspace linker, which is (perhaps) important for netlink stuff.

But after enabling all these options, I get still the errors:

Code:

udevd[1031]: get_netlink_msg: unable to receive kernel netlink message: Socket operation on non-socket

Each 10mins there is approx 1GB more in the syslog file.

Can anyone help what kernel options needs to be enabled?

humbletech99 · 09-16-2008, 10:16 AM

I figured out this was due to an incomplete clone from a live system, you didn't try that by any chance did you?

pzYsTorM · 09-16-2008, 11:00 AM

Oh, yes, I did change my hd one week ago.
With "cp -a oldhd newhd" I have copied everything (including /dev).
Is this the mistake?
What have you done to get rid of these errors?

Ehm... but... If I boot the original Debian Kernel 2.6.18-6, there are no errors and no messages in the syslog!