Actions
Bug #103
closedsysctl is called too early (or modules loaded too late)
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
System :: Base
Start date:
2010-06-14
Due date:
% Done:
0%
Estimated time:
Patch Available:
No
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
No
Help Needed:
No
Description
Sun Jun 13 00:38:57 2010: Setting kernel variables (/etc/sysctl.conf)...error: "net.ipv6.conf.all.forwarding" is an unknown key Sun Jun 13 00:38:57 2010: error: "net.ipv6.conf.all.autoconf" is an unknown key Sun Jun 13 00:38:57 2010: error: "net.ipv6.conf.all.accept_ra" is an unknown key Sun Jun 13 00:38:57 2010: error: "net.ipv6.conf.all.accept_redirects" is an unknown key Sun Jun 13 00:38:57 2010: error: "net.ipv6.conf.all.router_solicitations" is an unknown key Sun Jun 13 00:38:57 2010: ^[[31mfailed.^[[39;49m
Seems procs init script is not called at the right moment. We need to investigate.
This problem is present on Elwing, and perhaps on other hosts (not checked yet).
Updated by Arnaud Fontaine over 12 years ago
Could be related to #507788, isn't it? However, as stated by /usr/share/doc/procps/README.Debian, it should only affect custom kernels, was there a custom on elwing before?
Updated by Arnaud Fontaine over 12 years ago
- Status changed from New to In Progress
Updated by Marc Dequènes over 12 years ago
Elwing is using a standard Debian kernel. Maybe we should check the ordering choosen by insserv ?
Updated by Arnaud Fontaine over 12 years ago
Well, if it's using a Debian kernel, then ipv6 is compiled into the kernel, and not as a module, therefore this issue should not happen with or without insserv. Do you still have the issue? Is it reproducible somewhere else?
Updated by Marc Dequènes over 12 years ago
- Status changed from In Progress to Resolved
- Help Needed set to No
Recent reboot show no problems, so i assume i is fixed now.
Actions