[Bug 50093] Re: Some sysctl's are ignored on boot
bumping another year -- now 11 years old and still a real problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
** This bug is no longer a duplicate of bug 771372 procps runs too early in the boot process -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
*** This bug is a duplicate of bug 771372 *** https://bugs.launchpad.net/bugs/771372 This is still a problem in 16.04 LTS/xenial. I lost a whole workday chasing this down after an upgrade. I don't think it's a duplicate of 771372, as the above discussion indicates there is no "right" place to run procps, and 771372 works on that presumption. Instead, the start-up process needs to be reworked, or at least the network-related settings need to be reassigned to the network start-up process instead of living in procps. With the increased use of bridges (KVM, LXC, etc.), we should have a smooth start-up process for bridges and bridge-related settings. I confess I don't understand all the complexities others apparently see. We need someone that really understands the relevant start-up processes to architect a good solution. What can we do to get a little attention on this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
*** This bug is a duplicate of bug 771372 *** https://bugs.launchpad.net/bugs/771372 This is still happening.. Debian7.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
*** This bug is a duplicate of bug 771372 *** https://bugs.launchpad.net/bugs/771372 bumping +3 years , still no good solution -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
*** This bug is a duplicate of bug 771372 *** https://bugs.launchpad.net/bugs/771372 ** This bug has been marked a duplicate of bug 771372 procps runs too early in the boot process -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
It seems to me it is a Debian Squeeze bug, see for example here, also for a workaround: http://wiki.debian.org/BridgeNetworkConnections Strange enough... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
We've had this issue for ages. Thought we would investigate it more now since it recently caused us a bunch of pain due to some sysctl settings not being loaded. It's madness that no one has looked at this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
This will probably be a bug in Ubuntu 20.04 aaron aardvark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
Just ran into this issue myself and was _quite_ surprised to see how long this bug has been reported yet unresolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
A possible workaround is putting sysctl -p /etc/sysctl.conf in /etc/rc.local, which is ridiculous and doesn't even solve the problem that networking and bridges are started *before* the sysctl settings are applied. It is even more ridiculous that this bug hasn't had any attention from anyone except affected users in over five years. *Every* piece of documentation regarding any kind of sysctl setting refers to /etc/sysctl.conf as the place to put everything. And for over five years there has been a really good chance that most of /etc/sysctl.conf gets ignored because Ubuntu's boot process apparently doesn't know how when and often to read and apply the settings in there. This isn't just an upstart problem since upstart wasn't even around in 2006. Bugs like this make it really difficult to recommend Ubuntu as a server operating system and I wonder if Canonical really use Ubuntu as their server OS. If they did it seems this bug would have been fixed years ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
All documentation on the net referring to changing certain settings in /etc/sysctl.conf such as net.ipv4.netfilter.ip_conntrack_max is wrong for Ubuntu. In addition, workarounds suggesting that ordering of module load vs. sysctl.conf execution can be helped by i.e. putting ip_conntrack into /etc/modules also do not work. I'm sure on some level this is Low priority - aka bury for 5 years and never look at it again - and I can appreciate that this is not a simple problem to properly solve. But left as is, this is just another mine laid in the field for sysadmins foolish enough to use Ubuntu Server. I respectfully suggest that it might be useful to make multiple attempts to run sysctl -p at various milestones during the boot process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
Ah, so this is why my vm.laptop_mode=5, vm.dirty_writeback_centisecs=6000 and vm.dirty_expire_centisecs=7000 lines are totally ignored. Workaround, anyone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
Guys somebody really should take care about this as this is not fixed and still a problem with natty. At least please assign to the maintainer of procps service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
I didn't realize this was assigned to me. I don't have a recent Ubuntu system available so I can't help with this. Sorry. ** Changed in: procps (Ubuntu) Assignee: Yves Junqueira (yves.junqueira) = (unassigned) -- Some sysctl's are ignored on boot https://bugs.launchpad.net/bugs/50093 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
I'm having the exact same problem as jollyroger and Daniel, and it was maddening to debug. This bug's been filed since 2006 and it's still not fixed? Anyone who uses KVM in a bridged configuration is probably affected by it. At least make a note of it in the procps or upstart documentation so that users don't pull their hair out trying to figure out why sysctl.d conf files are being (silently) ignored. -- Some sysctl's are ignored on boot https://bugs.launchpad.net/bugs/50093 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
This seems pretty old and I'm not sure against which version of Ubuntu
it was filed against (Sorry kinda new to this bug system) however to
appears that the problem is two fold. I'm using karmic right now which
uses upstart. I've had trouble getting the following settings to work:
=={/etc/sysctl.conf}==
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-ip6tables = 0
kernel.shmmax = 68719476736
kernel.shmall = 4294967296
===
The upstart system had the procps starting after the event virtual-
filesystems which is triggered by /etc/init/mountall.conf. It appears
that due to the fact that many kernel modules are not yet loaded the,
for example bridge.ko, the entries above do not exist yet in
sysctl/procfs, so I changed /etc/init/procps.conf start line to read
start on starting network-interface This allows the bridge modules to
be loaded and and available when procps is allowed to run. Additionally
I modified the procps.conf script line to include the -e option so
that if there are entries that do not exist yet at least the entries
that do exist are executed and the incorrect entries are ignored. Seems
like that would be good practice anyway, I've attached a copy of the
procps.conf file that I've modifed. I didn't think to keep the originals
for diff's and don't want to make incorrect diffs so I just uploaded the
file as it is now.
** Attachment added: Modified /etc/init/procps.conf to run later in upstart
process
http://launchpadlibrarian.net/36631737/procps.conf
--
Some sysctl's are ignored on boot
https://bugs.launchpad.net/bugs/50093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
I'm having this as an issue trying to create network bridge for KVM virtualization. Following instructions here, http://wiki.libvirt.org/page/Networking#Debian.2FUbuntu_Bridging Libvirt is standard in ubuntu now, and these instructions are referenced elsewhere. Makes the whole thing a bit problematic. -- Some sysctl's are ignored on boot https://bugs.launchpad.net/bugs/50093 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
Hi. After giving some thought on this, I don't think the complex approach you described would work. Entries in /proc/sys may not exist even if the module was loaded. Take this case: yv:~# lsmod|grep 1394 eth139418212 0 ohci1394 30800 0 ieee1394 86904 3 sbp2,eth1394,ohci1394 yv:~# dmesg|grep 1394 ieee1394: Initialized config rom entry `ip1394' ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[209] MMIO=[e2004000-e20047ff] Max Packet=[2048] IR/IT contexts=[4/8] ieee1394: Host added: ID:BUS[0-00:1023] GUID[000fea27c5c2] eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1) ieee1394: sbp2: Try serialize_io=0 for better performance yv:~# ls /proc/sys/net/ipv4/conf/ all default eth1 lo Notice there is no eth0 entry. So processing sysctl parameters after loading a module is not enough, at least for network related issues. Can you describe cases when you believe processing some later sysctl directives are needed? I believe that using post-up parameters for /etc/network/interfaces is the current supported method. Maybe you could agree that this works for you? In that case, we should reject this bug, I guess. Thank you -- Some sysctl's are ignored on boot https://bugs.launchpad.net/bugs/50093 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
** Changed in: procps (Ubuntu) Assignee: (unassigned) = Yves Junqueira -- Some sysctl's are ignored on boot https://bugs.launchpad.net/bugs/50093 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctl's are ignored on boot
** Changed in: procps (Ubuntu) Importance: Untriaged = Low Status: Unconfirmed = Confirmed -- Some sysctl's are ignored on boot https://launchpad.net/bugs/50093 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
