Re: NetwokManager fails to start with core dumped
- From: Dan Williams <dcbw redhat com>
- To: Uldis Jansons <uldis jansons tele2 com>
- Cc: networkmanager-list gnome org
- Subject: Re: NetwokManager fails to start with core dumped
- Date: Tue, 17 Dec 2013 09:51:58 -0600
On Tue, 2013-12-17 at 13:34 +0200, Uldis Jansons wrote:
Hi!
Try to launch NetworkManager but it fails to start in ugly way.
Which libnl version do you have? There were some versions in 3.x that
did work, and some that didn't, due to bugs in libnl. v3.2.21 should
work, as should 3.2.23. I believe 3.2.22 had a crashing bug, and some
earlier versions like 3.2.7 had bugs too.
Dan
~# NetworkManager --config=/etc/NetworkManager/NetworkManager.conf --no-daemon
NetworkManager: /lib/libnl-genl-3.so.200: no version information available (required by NetworkManager)
NetworkManager: /lib/libnl-3.so.200: no version information available (required by NetworkManager)
NetworkManager: /lib/libnl-3.so.200: no version information available (required by
/usr/lib/libnl-route-3.so.200)
NetworkManager[2033]: <info> NetworkManager (version 0.9.8.8) is starting...
NetworkManager[2033]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
NetworkManager[2033]: <info> WEXT support is enabled
NetworkManager[2033]: <warn> Failed to connect to netlink: (4) unable to allocate netlink link cache for
monitoring link status: Operation not supported
NetworkManager[2033]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please
use the NetworkManager mailing list.
NetworkManager[2033]: <info> monitoring kernel firmware directory '/lib/firmware'.
NetworkManager[2033]: <info> WiFi hardware radio set enabled
NetworkManager[2033]: <info> WiFi enabled by radio killswitch; enabled by state file
NetworkManager[2033]: <info> WWAN enabled by radio killswitch; enabled by state file
NetworkManager[2033]: <info> WiMAX enabled by radio killswitch; enabled by state file
NetworkManager[2033]: <info> Networking is enabled by state file
NetworkManager[2033]: <warn> failed to allocate link cache: (-10) Operation not supported
NetworkManager[2033]: <warn> Failed to connect to netlink: (4) unable to allocate netlink link cache for
monitoring link status: Operation not supported
(NetworkManager:2033): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL
&& instance->g_class != NULL' failed
Segmentation fault (core dumped)
In syslog along with this output there is one extra line (dumped core):
Dec 17 12:43:32 lte kernel: [ 8225.410376] NetworkManager[2033]: segfault at 18 ip 000000000046d106 sp
00007fff7ebfa2a0 error 4 in NetworkManager[400000+101000]
From logfile output I assume the problem is somehow releated with Netlink. Netlink lib is installed and as
far as I found is linked correctly.
~# ldd /usr/sbin/NetworkManager
/usr/sbin/NetworkManager: /lib/libnl-genl-3.so.200: no version information available (required by
/usr/sbin/NetworkManager)
/usr/sbin/NetworkManager: /lib/libnl-3.so.200: no version information available (required by
/usr/sbin/NetworkManager)
/usr/sbin/NetworkManager: /lib/libnl-3.so.200: no version information available (required by
/usr/lib/libnl-route-3.so.200)
linux-vdso.so.1 => (0x00007fffeb7ff000)
libmm-glib.so.0 => /usr/lib/libmm-glib.so.0 (0x00007feea2662000)
libnm-util.so.2 => /usr/lib/libnm-util.so.2 (0x00007feea23ff000)
libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 (0x00007feea21d8000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007feea1f94000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007feea1c45000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007feea1a40000)
libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x00007feea1836000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007feea15e7000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007feea12f1000)
libnl-route-3.so.200 => /usr/lib/libnl-route-3.so.200 (0x00007feea109e000)
libnl-genl-3.so.200 => /lib/libnl-genl-3.so.200 (0x00007feea0e99000)
libnl-3.so.200 => /lib/libnl-3.so.200 (0x00007feea0c80000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007feea0a63000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007feea0767000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007feea03a6000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007feea01a1000)
libnss3.so => /usr/lib/x86_64-linux-gnu/libnss3.so (0x00007fee9fe99000)
libsmime3.so => /usr/lib/x86_64-linux-gnu/libsmime3.so (0x00007fee9fc71000)
libnspr4.so => /usr/lib/x86_64-linux-gnu/libnspr4.so (0x00007fee9fa32000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fee9f82a000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fee9f612000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fee9f3f3000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fee9f1d7000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fee9efd2000)
libudev.so.0 => /lib/x86_64-linux-gnu/libudev.so.0 (0x00007fee9edc5000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007fee9ebbd000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fee9e97f000)
/lib64/ld-linux-x86-64.so.2 (0x00007feea291c000)
libnssutil3.so => /usr/lib/x86_64-linux-gnu/libnssutil3.so (0x00007fee9e758000)
libplc4.so => /usr/lib/x86_64-linux-gnu/libplc4.so (0x00007fee9e552000)
libplds4.so => /usr/lib/x86_64-linux-gnu/libplds4.so (0x00007fee9e34e000)
Environment info:
Ubuntu 12.04.3 LTS
Linux 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Any ideas where the problem might be?
Thanks in advance for any help!
Best regards,
Uldis
_______________________________________________
networkmanager-list mailing list
networkmanager-list gnome org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]