Could not find a way to edit comments but I'd like to retract comment
#14. In my case it was first touching any iptables related stuff in
rc.local which seems to be executed later then procps. I am now force
loading the related module 'nf_conntrack_ipv4' in /etc/modules which
makes the sysctl.d
I'd like to second that, still having this on Ubuntu server 12.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690433
Title:
procps starts too early to correctly set
i still have a problem that net.ipv4.netfilter.ip_conntrack_max are not
applying
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690433
Title:
procps starts too early to correctly set
Marking as fix released as the -updates package fixes the issue on
Lucid.
** Changed in: procps (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@James, since the latest packages uploaded to lucid-proposed for bug
771372, the problem is fixed. Many thanks.
** Changed in: procps (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue is related to bug 771372.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690433
Title:
procps starts too early to correctly set
net.netfilter.nf_conntrack_acct
To manage notifications
This is an issue with the procps package, not Upstart.
** Package changed: upstart (Ubuntu) = procps (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690433
Title:
procps starts too early to
I confirm, I have the same problem and the following setting is not applied:
net.ipv4.netfilter.ip_conntrack_max=1548576
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690433
Title:
procps starts
@Arkadiy
As a workaround you you install the /etc/init/procps.conf and /etc/init
/procps-net.conf from comments #3 and #4.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've hit a similar problem, though it's net.bridge.bridge-nf-call-
iptables that I care about.
It's not because it's running too early though, it's not running at all.
I confirmed this by adding some echos to a log file to the script in
/etc/init/procps.conf. It appears to be broken in both
@David,
I just found a workaround for the net.bridge.bridge-nf-call-*tables
values. You need to add the bridge module to /etc/modules and run
update-initramfs :
echo bridge /etc/modules
update-initramfs -k all -u
This works because the bridge module is responsible to create the sysctl
keys
Instead of using the previous workaround I modified
/etc/init/procps.conf and added /etc/init/procps-net.conf. With the
modified and the new files everything is working (including
net.netfilter.nf_conntrack_acct) without needing to add modules to the
initrd.
** Attachment added: procps upstart
** Attachment added: procps upstart conf file that set network related sysctls
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/690433/+attachment/1836235/+files/procps-net.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, looks like we're hitting different bugs. For me, on karmic at least
the procps.conf script is not being run *at all*.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690433
Title:
procps starts
@David,
Maybe adding a post-up command to your bridge configuration in
/etc/network/interfaces would help. Here is an example :
# The primary network interface
auto br0
iface br0 inet static
address 172.16.20.1
netmask 255.255.255.0
gateway 172.16.20.2
# Workaround for upstart
15 matches
Mail list logo
