[Bug 1520225] Re: lxc-stop powered off a server
Hi, container config : http://paste.ubuntu.com/13524088/ /etc/apt/sources.list.d just contains a repo for some homemade backports "dpkg -l | grep lxc" was given in the initial comment, but here it is again : $ dpkg -l|grep lxc ii liblxc1 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools (library) ii lxc 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools ii lxc-templates 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools (templates) ii python3-lxc 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools (Python 3.x bindings) I understand that "--share-net 1" can make the container connect to the host's upstart socket. I still don't think "lxc-stop" should stop the host, ever. Cheers -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525785/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] lxc.default.txt
apport information ** Attachment added: "lxc.default.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525789/+files/lxc.default.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] lxcsyslog.txt
apport information ** Attachment added: "lxcsyslog.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525790/+files/lxcsyslog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] [NEW] lxc-stop powered off a server
Public bug reported: Hi, Earlier today, a server got powered off and I'm 99% sure it's because I ran the following command as root : # lxc-stop -n The container was started manually with : # lxc-start -n -F --share-net 1 and it wasn't fully booted (ie I didn't have the console yet). syslog just showed : Nov 26 11:13:12 foo kernel: [30192021.012313] init: tty4 main process (1298) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013083] init: tty5 main process (1301) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013750] init: jujud-unit-landscape-client-0 main process (1303) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.014412] init: jujud-unit-ksplice-0 main process (1306) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.015017] init: tty2 main process (1307) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.015592] init: tty3 main process (1309) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016160] init: tty6 main process (1312) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016810] init: jujud-machine-0 main process (1313) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.017423] init: jujud-unit-ubuntu-basenode-0 main process (1314) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.018583] init: tty1 main process (1784) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.019164] init: ttyS1 main process (1791) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.019738] init: cron main process (20196) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.020328] init: irqbalance main process (26014) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.020926] init: cgmanager main process (27367) killed by TERM signal and that's it. I don't have other relevant logs to offer I'm afraid. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty ~$ dpkg -l|grep lxc ii liblxc1 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools (library) ii lxc 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools ii lxc-templates 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools (templates) ii python3-lxc 1.0.7-0ubuntu0.10 amd64Linux Containers userspace tools (Python 3.x bindings) apport information below Thanks --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.10 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic root=UUID=17a1fdea-b0d0-4f6f-a664-ec532f379c64 ro console=tty0 console=ttyS1,38400 nosplash ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Tags: trusty third-party-packages apparmor Uname: Linux 3.13.0-68-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-collected third-party-packages trusty ** Tags added: apparmor apport-collected third-party-packages trusty ** Description changed: Hi, Earlier today, a server got powered off and I'm 99% sure it's because I ran the following command as root : # lxc-stop -n The container was started manually with : # lxc-start -n -F --share-net 1 and it wasn't fully booted (ie I didn't have the console yet). syslog just showed : Nov 26 11:13:12 foo kernel: [30192021.012313] init: tty4 main process (1298) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013083] init: tty5 main process (1301) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.013750] init: jujud-unit-landscape-client-0 main process (1303) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.014412] init: jujud-unit-ksplice-0 main process (1306) terminated with status 2 Nov 26 11:13:12 foo kernel: [30192021.015017] init: tty2 main process (1307) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.015592] init: tty3 main process (1309) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016160] init: tty6 main process (1312) killed by TERM signal Nov 26 11:13:12 foo kernel: [30192021.016810] init: jujud-machine-0 main process (1313) terminated with status 2 Nov 26 11:13:12 foo kernel:
[Bug 1520225] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525786/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525787/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1520225] lxc-net.default.txt
apport information ** Attachment added: "lxc-net.default.txt" https://bugs.launchpad.net/bugs/1520225/+attachment/4525788/+files/lxc-net.default.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1520225 Title: lxc-stop powered off a server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413388] Re: [SRU] upgrade of MAAS removes local config for bind and breaks DNS
Also : would running maas-region-admin edit_named_options --migrate- conflicting-options without forwarders in named.conf.options remove the forwarder setting from the MAAS database ? Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1413388 Title: [SRU] upgrade of MAAS removes local config for bind and breaks DNS To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1413388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1350947] Re: apparmor: no working rule to allow making a mount private
Hi Serge, Martin, As Serge mentioned in #4, this bug will cause breakage if using both ip netns and lxc. As I'm sure you're aware, the OpenStack neutron/quantum gateway makes heavy use of the ip netns feature, and it's valid to have LXC containers on the server hosting tje quantum gateway. Given this setup, adding a container to the server hosting the quantum gateway breaks the netns for the DHCP and L3 agents, which leads to all sorts of fun. So, does it make sense to backport this fix to trusty ? If not, then is manually applying https://github.com/lxc/lxc/pull/393/files a valid workaround ? Thanks ! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
