Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#27281 - [networkmanager] IPv6 default route log errors

Attached to Project: Arch Linux
Opened by jon (emphire) - Sunday, 27 November 2011, 23:40 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 28 March 2012, 19:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


After upgrading network-manager ( ->, my /var/log/error.log files filled-up with over 34,000 of these messages (several every second):

Nov 27 15:27:19 localhost NetworkManager[736]: <error> [1322436439.499469] [nm-system.c:1061] nm_system_replace_default_ip6_route(): (eth0): failed to set IPv6 default route: -1

Downgrading to stopped the error messages from appearing.

This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 28 March 2012, 19:39 GMT
Reason for closing:  Fixed
Additional comments about closing:  networkmanager
Comment by Ionut Biru (wonder) - Monday, 28 November 2011, 07:09 GMT
giving that only line from the log is making the debuging very very hard.
Comment by jon (emphire) - Tuesday, 29 November 2011, 18:28 GMT
I would attach my log files but they're several gigs in size with all the error messages from NetworkManager. Here is a grep from the first 1000 lines of them. If there is any additional info I can offer please let me know.

Attached is the output of the following:
head -n 1000 daemon.log.1 | grep -i networkmanager > daemon.grep.log
head -n 1000 errors.log.1 | grep -i networkmanager > errors.grep.log
head -n 1000 messages.log.1 | grep -i networkmanager > messages.grep.log
Comment by Ionut Biru (wonder) - Tuesday, 29 November 2011, 18:37 GMT
continuing in this bugtracker doesn't help anyone. please report this issue to networkmanager bugtracker
Comment by Mihai Coman (z0id) - Thursday, 19 January 2012, 16:59 GMT
I also have this issue and I filed the bug here: