[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Frieder Bürzele, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
** Tags removed: natty
** Tags added: precise
** Changed in: linux (Ubuntu Oneiric)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Title:
kernel bug at
I'm probably never gonna get around to this.
** Changed in: linux (Ubuntu Oneiric)
Status: In Progress = Confirmed
** Changed in: linux (Ubuntu Oneiric)
Assignee: Tim Gardner (timg-tpi) = (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress = Confirmed
** Changed
it is still an issue with precise see
'precise_3.2.0-17-generic_xt_recent.c:610.log'
** Attachment added: precise_3.2.0-17-generic_xt_recent.c:610.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869068/+attachment/2833925/+files/precise_3.2.0-17-generic_xt_recent.c%3A610.log
--
You
Just to be sure, I presume that executing 'iptables -F INPUT' within the
container before lxc-stop avoids the problem ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Title:
kernel bug at
yes, flushing avoids 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/869068
Title:
kernel bug at xt_recent.c:610 stopping lxc guest (lxc-stop)
To manage notifications about this bug go
Is this still an issue with Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Title:
kernel bug at xt_recent.c:610 stopping lxc guest (lxc-stop)
To manage notifications about this bug
anything ongoing here? Or should I report this bug to the lxc-project?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Title:
kernel bug at xt_recent.c:610 stopping lxc guest (lxc-stop)
To
** Tags added: iptables
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Title:
kernel bug at xt_recent.c:610 stopping lxc guest (lxc-stop)
To manage notifications about this bug go to:
** Attachment added: Kernel error message
https://bugs.launchpad.net/bugs/869068/+attachment/2517133/+files/xt_recent_610_bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Title:
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869068
Title:
kernel bug at xt_recent.c:610 stopping lxc guest (lxc-stop)
To manage
Frieder - please attach the relevant config files. I'm unable to
reproduce this problem, but I'm also kind of an lxc novice. I've got
libvirt-bin and lxc installed, and have the virbr0 interface up, but
can't seem to get the container to run after creating
/etc/lxc/centos_test.conf.
** Also
I looked into the lxc container again and after a while I finally stumbled over
its iptables setup.
The bug already pointed to this place but I totally forgot about that.
Here are the iptables settings:
iptables -A INPUT -i eth0 -p tcp -m tcp --dport 21 -m state --state NEW -m
recent --set
14 matches
Mail list logo
