Ubuntu
network-manager package

network-manager logs very verbosely about errors while setting IPv6 routes

Bug #915827 reported by Martijn vdS
60
This bug affects 10 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have native IPv6 on my home network, and I've set network-manager to expect it ("require IPv6 on this network"). This works fine, but I end up with lots (and LOTS) of log lines that look like this:

Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <error> [1326437190.92540] [nm-system.c:602] nm_system_apply_ip6_config(): (eth0): failed to set IPv6 route: Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <error> [1326437190.92601] [nm-system.c:602] nm_system_apply_ip6_config(): (eth0): failed to set IPv6 route: Object not found

Every few seconds a burst of messages comes by. rsyslogd doesn't like it either:

Jan 13 07:41:06 martijn-desktop rsyslogd-2177: imuxsock begins to drop messages from pid 8051 due to rate-limiting
Jan 13 07:42:00 martijn-desktop rsyslogd-2177: imuxsock lost 10 messages from pid 8051 due to rate-limiting

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.2.0+git201201101813.0b30200-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Fri Jan 13 07:45:29 2012
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 tun0 no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 PATH=(custom, user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2011-12-03 (40 days ago)
modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-01-13T07:38:58.347888
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 XS4ALL VPN (openvpn) 16548840-3b2b-4086-920e-2d34a021e1ed vpn 1326436781 vr 13 jan 2012 07:39:41 CET yes no /org/freedesktop/NetworkManager/Settings/1
 Wired connection 1 56f95544-d904-47d7-a75c-11c5ce360c97 802-3-ethernet 1326436767 vr 13 jan 2012 07:39:27 CET yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.3.0 connected enabled enabled enabled enabled disabled

Revision history for this message
Martijn vdS (martijn) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Remco Brenninkmeijer (requist1) wrote :

Same problem here with native ipv6 and the addition that dnsmasq keeps on restarting after the errors from network-manager:

dnsmasq[15148]: exiting on receipt of SIGTERM
Feb 6 11:23:41 axe NetworkManager[1065]: <info> DNS: starting dnsmasq...
Feb 6 11:23:41 axe NetworkManager[1065]: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Feb 6 11:23:41 axe dnsmasq[15156]: started, version 2.59 cache disabled
Feb 6 11:23:41 axe dnsmasq[15156]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
Feb 6 11:23:41 axe dnsmasq[15156]: using nameserver 192.168.178.1#53
Feb 6 11:23:41 axe dnsmasq[15156]: read /etc/hosts - 4 addresses

Revision history for this message
Remco Brenninkmeijer (requist1) wrote :

disabling dnsmasq removes these errors but the errors above still appear. Looks like the error repeats every time the system tries to send packages over ipv6.

Revision history for this message
Remco Brenninkmeijer (requist1) wrote :

btw I have the errors above with 12.04, on my laptop running 11.10 the ipv6 connection runs fine, also previously on this system with 11.10 I never noticed these errors.

Revision history for this message
chevrel (alain-chevrel) wrote :

Hi everyone,
since I activated IPV6 on the freebox V6 ( french ADSL "triple play" box ), my syslog receives every minute :
...
Jun 11 09:08:07 M7721 dnsmasq[22904]: exiting on receipt of SIGTERM
Jun 11 09:08:07 M7721 NetworkManager[1384]: <info> DNS: starting dnsmasq...
Jun 11 09:08:07 M7721 NetworkManager[1384]: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Jun 11 09:08:07 M7721 dnsmasq[22913]: started, version 2.59 cache disabled
Jun 11 09:08:07 M7721 dnsmasq[22913]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
Jun 11 09:08:07 M7721 dnsmasq[22913]: using nameserver 192.168.0.254#53
Jun 11 09:08:14 M7721 dnsmasq[22913]: exiting on receipt of SIGTERM
Jun 11 09:08:14 M7721 NetworkManager[1384]: <info> DNS: starting dnsmasq...
Jun 11 09:08:14 M7721 dnsmasq[22921]: started, version 2.59 cache disabled
Jun 11 09:08:14 M7721 dnsmasq[22921]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
Jun 11 09:08:14 M7721 dnsmasq[22921]: using nameserver 2a01:e00::1#53
Jun 11 09:08:14 M7721 dnsmasq[22921]: using nameserver 2a01:e00::2#53
Jun 11 09:08:14 M7721 dnsmasq[22921]: using nameserver 192.168.0.254#53
Jun 11 09:08:14 M7721 NetworkManager[1384]: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Jun 11 09:08:14 M7721 NetworkManager[1384]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Jun 11 09:08:14 M7721 NetworkManager[1384]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS.
...

is that the same problem ?
thanks for any idea
alain chevrel

Revision history for this message
Thomas Hood (jdthood) wrote :

Compare bug #987858 and bug #1004775.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

As far as I know the issues with libnl3 have been fixed since; and should be fixed in the 12.04 release. Could you please confirm that it's the case?

As for the messages about dnsmasq, please see bug 1004775.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

What I mean by issues with libnl3 is obviously the "Failed to add route" errors :
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <error> [1326437190.92540] [nm-system.c:602] nm_system_apply_ip6_config(): (eth0): failed to set IPv6 route: Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <warn> Failed to add route Object not found
Jan 13 07:46:30 martijn-desktop NetworkManager[8051]: <error> [1326437190.92601] [nm-system.c:602] nm_system_apply_ip6_config(): (eth0): failed to set IPv6 route: Object not found

Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.