Fedora Account System
Red Hat Associate
Red Hat Customer
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050109 Fedora/1.7.5-3 Description of problem: When starting up the network service on my server or when booting up, I get this logged: [root@tornado init.d]# /etc/init.d/network restart Shutting down interface eth0: [ OK ] Shutting down interface gre0: [ OK ] Shutting down loopback interface: [ OK ] Disabling IPv4 packet forwarding: net.ipv4.ip_forward = 0 [ OK ] error: unknown error 22 reading key 'net.ipv6.route.flush' error: unknown error 22 reading key 'net.ipv4.route.flush' error: unknown error 22 reading key 'fs.binfmt_misc.register' error: unknown error 22 reading key 'net.ipv6.route.flush' error: unknown error 22 reading key 'net.ipv4.route.flush' error: unknown error 22 reading key 'fs.binfmt_misc.register' Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Bringing up interface gre0: [ OK ] [root@tornado init.d]# I've traced this to a problem with the output of sysctl -a. In /etc/sysconfig/network-scripts/init.ipv6-global, sysctl -a is called and the output parsed. This output includes the errors as above. Version-Release number of selected component (if applicable): procps-3.2.4-3 How reproducible: Always Steps to Reproduce: You can reproduce this error by simply viewing the output of sysctl -a on the command line ie: .. net.ipv6.conf.all.accept_ra = 1 net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.all.hop_limit = 64 net.ipv6.conf.all.forwarding = 0 error: unknown error 22 reading key 'net.ipv4.route.flush' error: unknown error 22 reading key 'fs.binfmt_misc.register' [root@tornado ~]# Actual Results: Errors :( Expected Results: The output should have been returned without error. Additional info: This bug has been present for a period of time, it is not a very recent regression. [root@tornado ~]# rpm -q kernel-smp kernel-smp-2.6.10-1.1115_FC4 [root@tornado ~]# Also occurs when running non-Fedora kernels.
See bug #144459.
*** This bug has been marked as a duplicate of 144459 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.