Bug 139664

Summary: Sysctl error messages from /etc/init.d/network when using IPv6
Product: [Fedora] Fedora Reporter: Troels Arvin <troels>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: medium    
Version: 3CC: pcmoore, pfrields, rhbugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-07-16 21:08:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
My sysctl.conf none

Description Troels Arvin 2004-11-17 10:33:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
When booting/shutting down/changing runlevel, I get this error message:
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'

The same error messages appear if I do
sysctl -a >/dev/null

I don't know if the error messages really indicate something bad. But
the messages are not "pretty" during boot/shutdown.

I've narrowed the problem down to the /etc/init.d/network script and
the related /etc/sysconfig/networking file. If I put the following
line into /etc/sysconfig/networking, the problem exists:
NETWORKING_IPV6=yes

If the above value is set to "no", then the problem goes away (as well
as my IPv6 connectivity...).

I've tried going through the contents of the initscript package,
trying to find instances of "sysctl -a", changing them to "sysctl -e
-a", for a start. But that didn't help, or I missed something.

Apart from that, I'm wondering if the sysctl error messages is
something that I should worry about.

Version-Release number of selected component (if applicable):
initscripts-7.93.5-1

How reproducible:
Always

Steps to Reproduce:
1. Set NETWORKING_IPV6 to "yes" in /etc/sysconfig/network
2. "Run /etc/init.d/network restart"


Actual Results:  Shutting down interface eth1:                       
      [  OK  ]
Shutting down interface sit2:                              [  OK  ]
Shutting down loopback interface:                          [  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'
Setting network parameters:                                [  OK  ]
Bringing up loopback interface:                            [  OK  ]

Expected Results:  Shutting down interface eth1:                     
        [  OK  ]
Shutting down interface sit2:                              [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Setting network parameters:                                [  OK  ]
Bringing up loopback interface:                            [  OK  ]

Additional info:

Comment 1 Bill Nottingham 2004-11-17 21:02:54 UTC
Can you attach your /etc/sysctl.conf?

Comment 2 Troels Arvin 2004-11-17 21:13:05 UTC
Created attachment 106912 [details]
My sysctl.conf

As requested: My /etc/sysctl.conf. Should be as distributed, except for
kernel.sysrq = 1
and
dev.rtc.max-user-freq = 1024

Comment 3 Bill Nottingham 2004-11-17 21:35:08 UTC
The kernel is returning -EINVAL.

Comment 4 Paul 2004-11-30 03:53:44 UTC
I recently upgraded from RH9, with IPv6 enabled, and I am seeing the
same problem.

Comment 5 Dave Jones 2005-07-15 18:33:26 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 6 Troels Arvin 2005-07-16 21:06:53 UTC
With kernel 2.6.12-1.1372_FC3, I don't get error messages any more. Thanks.