[Bug 1556967] Re: Support 'multipath -a'
** Package changed: ubuntu => multipath-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1556967 Title: Support 'multipath -a' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1556967/+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 1554098] Re: Rebase libseccomp from (2.2.3-3) -> 2.3.0
** Package changed: ubuntu => libseccomp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1554098 Title: Rebase libseccomp from (2.2.3-3) -> 2.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1554098/+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 1503305] Re: iLab: power kvm client after svc node reboot error inject test, multipath output show missing path and missing storage name
** Package changed: ubuntu => multipath-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1503305 Title: iLab: power kvm client after svc node reboot error inject test, multipath output show missing path and missing storage name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1503305/+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
Re: [Bug 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer
:) ... In the IT world it takes time to analyze a problem well !! Congrats ... Happy Easter !! On 4 April 2015 at 13:06, Mike smart...@gmail.com wrote: Thank you for the suggestions Gary. I realized that my problem is caused by the router firmware. Basically, they introduced loopback blocking and I couldn't connect from the same network even using the external IP. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/708493 Title: Can't login anymore: Read from socket failed: Connection reset by peer Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: After todays update to 1:5.7p1-1ubuntu1 I cannot login to SOME (!) of my servers. Example of a server failing: ~$ ssh -v root@mail OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to mail [141.42.202.200] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Read from socket failed: Connection reset by peer There is NOTHING in daemon.log, auth.log or syslog on the server I'm trying to connect to. Example of a server NOT failing: $ ssh -v root@netsight OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to netsight [10.47.2.222] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 18:ce:76:c7:7c:f4:98:94:28:8f:62:4a:31:e8:5b:c9 debug1: Host 'netsight' is known and matches the RSA host key. debug1: Found key in /home/hildeb/.ssh/known_hosts:56 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/hildeb/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to netsight ([10.47.2.222]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LC_MESSAGES = en_US.utf8 debug1: Sending env LANG = de_DE.UTF-8 ProblemType: Bug DistroRelease: Ubuntu 11.04
Re: [Bug 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer
Use dbclient ... On 20 February 2015 at 19:07, Mike smart...@gmail.com wrote: Hello, Not sure it is the same problem here, but I cannot connect to my machine if go through NAT. If I connect directly from LAN everything works, but if I use the external IP, then I get connection reset after debug1: SSH2_MSG_KEXINIT sent. Client and server is the same machine. I tried to set MTU to 1400 and 400 with no effect, also changed the net.ipv4.tcp_rmem setting and tried different cipher algorithms with no luck. Linux 3.16.0-31-generic #41-Ubuntu Ubuntu 14.10 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/708493 Title: Can't login anymore: Read from socket failed: Connection reset by peer Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: After todays update to 1:5.7p1-1ubuntu1 I cannot login to SOME (!) of my servers. Example of a server failing: ~$ ssh -v root@mail OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to mail [141.42.202.200] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Read from socket failed: Connection reset by peer There is NOTHING in daemon.log, auth.log or syslog on the server I'm trying to connect to. Example of a server NOT failing: $ ssh -v root@netsight OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to netsight [10.47.2.222] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 18:ce:76:c7:7c:f4:98:94:28:8f:62:4a:31:e8:5b:c9 debug1: Host 'netsight' is known and matches the RSA host key. debug1: Found key in /home/hildeb/.ssh/known_hosts:56 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/hildeb/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to netsight ([10.47.2.222]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering
Re: [Bug 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer
Did this used to work ? This bug is due to a ssh version change ... Sounds like you may have a firewall issue, if you are trying to connect via a nated connection for the 1st time. Use tcpdump on your server ... and analyze the traffic on port 22 Compare the traffic, when you connect locally and then via the nated connection. Use the verbose settings of ssh to get more information before posting again .. On 20 February 2015 at 20:25, Mike smart...@gmail.com wrote: Thanks, but a specific client is not an option. I need to connect with any client from different systems. The flow I described is for problem isolation only. Putty cannot connect either. On Fri Feb 20 2015 at 18:31:15 Gary Salisbury 708...@bugs.launchpad.net wrote: Use dbclient ... On 20 February 2015 at 19:07, Mike smart...@gmail.com wrote: Hello, Not sure it is the same problem here, but I cannot connect to my machine if go through NAT. ... -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/708493 Title: Can't login anymore: Read from socket failed: Connection reset by peer Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: After todays update to 1:5.7p1-1ubuntu1 I cannot login to SOME (!) of my servers. Example of a server failing: ~$ ssh -v root@mail OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to mail [141.42.202.200] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Read from socket failed: Connection reset by peer There is NOTHING in daemon.log, auth.log or syslog on the server I'm trying to connect to. Example of a server NOT failing: $ ssh -v root@netsight OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to netsight [10.47.2.222] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 18:ce:76:c7:7c:f4:98:94:28:8f:62:4a:31:e8:5b:c9 debug1: Host 'netsight' is known and matches the RSA host key. debug1: Found key in /home/hildeb/.ssh/known_hosts:56 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey
Re: [Bug 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer
Why are you testing a NATED address from the same server ( client and server ) ? Do you get the same problem when connecting via the NATED address from the outside network ... using a different client machine from outside ? On 20 February 2015 at 20:43, Gary Salisbury gary.r.salisb...@gmail.com wrote: Did this used to work ? This bug is due to a ssh version change ... Sounds like you may have a firewall issue, if you are trying to connect via a nated connection for the 1st time. Use tcpdump on your server ... and analyze the traffic on port 22 Compare the traffic, when you connect locally and then via the nated connection. Use the verbose settings of ssh to get more information before posting again .. On 20 February 2015 at 20:25, Mike smart...@gmail.com wrote: Thanks, but a specific client is not an option. I need to connect with any client from different systems. The flow I described is for problem isolation only. Putty cannot connect either. On Fri Feb 20 2015 at 18:31:15 Gary Salisbury 708...@bugs.launchpad.net wrote: Use dbclient ... On 20 February 2015 at 19:07, Mike smart...@gmail.com wrote: Hello, Not sure it is the same problem here, but I cannot connect to my machine if go through NAT. ... -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/708493 Title: Can't login anymore: Read from socket failed: Connection reset by peer Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: After todays update to 1:5.7p1-1ubuntu1 I cannot login to SOME (!) of my servers. Example of a server failing: ~$ ssh -v root@mail OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to mail [141.42.202.200] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Read from socket failed: Connection reset by peer There is NOTHING in daemon.log, auth.log or syslog on the server I'm trying to connect to. Example of a server NOT failing: $ ssh -v root@netsight OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to netsight [10.47.2.222] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 18:ce:76:c7:7c:f4:98:94:28:8f:62:4a:31:e8:5b:c9 debug1: Host 'netsight' is known and matches the RSA host key. debug1: Found key in /home/hildeb/.ssh/known_hosts:56 debug1
[Bug 1387510] [NEW] openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build
Public bug reported: Description:Ubuntu 14.04.1 LTS Release:14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-39-generic Date: Wed Oct 29 21:30:12 2014 DuplicateSignature: dkms:openvswitch-datapath-dkms:2.0.2-0ubuntu0.14.04.1:configure: error: Linux kernel in /lib/modules/3.13.0-39-generic/build is version 3.13.11, but version newer than 3.12.x is not supported InstallationDate: Installed on 2014-04-20 (193 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all PackageVersion: 2.0.2-0ubuntu0.14.04.1 SourcePackage: openvswitch Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1387510 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1387510/+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 1325099] Re: Index.html is not correctly created when using startpanel command
Looks like a simple change to the appropriate html template under horizon/conf ** Changed in: horizon Importance: Undecided = Low ** Tags added: low-hanging-fruit -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1325099 Title: Index.html is not correctly created when using startpanel command To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1325099/+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 834930] Re: Need a way to manage SSH keys in a juju environment.
+1 on adding to GUI. Priority-wise I think it goes after a decent chunk of other goals, but it definitely fits into what we've said we want the GUI to accomplish, and if we see a way to fit it in quickly hopefully we can. ** Changed in: juju-gui Status: New = Triaged ** Changed in: juju-gui Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/834930 Title: Need a way to manage SSH keys in a juju environment. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/834930/+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 1149410] Re: Stuck on Trying to connect to the Juju environment
For anyone looking at this bug, the Juju GUI fix mentioned has been released for several months now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1149410 Title: Stuck on Trying to connect to the Juju environment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-gui/+bug/1149410/+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
Re: [Bug 1149410] Re: Stuck on Trying to connect to the Juju environment
Hi Marius. I take it that you encountered this problem again? Under what circumstances–what versions of the charm and GUI? ~juju-gui's trunk of the charm + juju GUI trunk should do what you need but everything else will not at the moment. We are blocked by ~charmers in getting the charm published, but we will make another release of the GUI no later than next week. The rapi error you gave probably is unrelated, unless you are encountering a behavior we've never seen (possible). Gary On Mar 14, 2013, at 6:10 AM, Marius B. Kotsbak 1149...@bugs.launchpad.net wrote: I found this in /var/log/juju/api-agent.log: KeyError: 'result' 2013-03-12 16:30:31,763: juju.rapi.delta@ERROR: An error occurred 'result' Traceback (most recent call last): File /var/lib/juju/units/juju-gui-4/charm/juju/juju/rapi/delta.py, line 59, in pump current = (yield self.context.status())['result'] where line 59 is: current = (yield self.context.status())['result'] ** Also affects: juju (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Juju GUI Hackers, which is subscribed to juju-gui. https://bugs.launchpad.net/bugs/1149410 Title: Stuck on Trying to connect to the Juju environment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-gui/+bug/1149410/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1149410 Title: Stuck on Trying to connect to the Juju environment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-gui/+bug/1149410/+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
Re: [Bug 1149410] Re: Stuck on Trying to connect to the Juju environment
On 03/14/2013 08:17 AM, Marius B. Kotsbak wrote: Yes, I encountered it again, using juju-gui-source: trunk. and cs:precise/juju-gui. Maybe this was a slightly different problem, but still at loading the main page and failing to connect to the API. I also saw this in the log: Starting or restarting Juju API agent. and Failed to perform start on service juju-api-agent This is new to me. I'll pass it along to a pyjuju dev in case anyone else has seen it. A pastebin of a longer bit of log output might be helpful. I changed back to stable and deployed again, and then it worked fine. What other combo is recommended for a newer version? ATM, for what I believe to be the specific issue you are encountering: charm: cs:~juju-gui/precise/juju-gui juju-gui-source: lp:juju-gui That's bleeding edge. Using the GUI release (the charm default behavior) means it has been better tested. Moreover, on the charm trunk, using a GUI release is also about eight minutes faster to deploy on ec2 than a branch. Once we make a release with this fix (version number 0.2.2) we suggest you go back to using releases. Gary -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1149410 Title: Stuck on Trying to connect to the Juju environment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-gui/+bug/1149410/+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
Re: [Bug 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer
/known_hosts:56 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/hildeb/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to netsight ([10.47.2.222]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LC_MESSAGES = en_US.utf8 debug1: Sending env LANG = de_DE.UTF-8 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: openssh-client 1:5.7p1-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37 Uname: Linux 2.6.37-12-generic x86_64 Architecture: amd64 Date: Thu Jan 27 09:13:15 2011 ProcEnviron: LANGUAGE=en_US:en LANG=de_DE.UTF-8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-ssh N/A keychain N/A ssh-askpass-gnome 1:5.7p1-1ubuntu1 SSHClientVersion: OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 SourcePackage: openssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+subscriptions -- Regards Gary Cell 083-391-4914 Fax 086-655-3146 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/708493 Title: Can't login anymore: Read from socket failed: Connection reset by peer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+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
Re: [Bug 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer
. debug1: Sending environment. debug1: Sending env LC_MESSAGES = en_US.utf8 debug1: Sending env LANG = de_DE.UTF-8 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: openssh-client 1:5.7p1-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37 Uname: Linux 2.6.37-12-generic x86_64 Architecture: amd64 Date: Thu Jan 27 09:13:15 2011 ProcEnviron: LANGUAGE=en_US:en LANG=de_DE.UTF-8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-ssh N/A keychain N/A ssh-askpass-gnome 1:5.7p1-1ubuntu1 SSHClientVersion: OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 SourcePackage: openssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+subscriptions -- Regards Gary Cell 083-391-4914 Fax 086-655-3146 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/708493 Title: Can't login anymore: Read from socket failed: Connection reset by peer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493/+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 1003656] Re: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot
Gah, ignore my comment, perhaps the new version is working. The issue I see now seems to be that on the last reboot the MAC address of the bond has obtained the MAC of the other ethernet interface in the bond rather than the MAC address of eth0 (which is the one hard wired in my dhcpd config), meaning it's unable to obtain an IP address to to my dhcp server not knowing what address to give it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+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 1003656] Re: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot
OK... if I force the MAC address of my bridge to be the one expected by my dhcp server then 1.5-2ubuntu7 works. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+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
Re: [Bug 997978] Re: KVM images lose connectivity with bridged network
I don't believe just rebooting a guest will cause a new KVM instance to load. As a test, I just rebooted a guest VM on a system here and the pid of the kvm process did not change. I think it may be possible that you are still running on the old software. Also, to update my data point... On my server which was experiencing issues, I rebooted the host just to make sure everything was fresh. It's been about a month and I have not experienced the failure again. I was typically going a few weeks between issues. gary - Original Message - From: Matt Hilt mjh...@gmail.com To: g...@isgsoftware.net Sent: Tuesday, September 25, 2012 12:07:44 PM Subject: [Bug 997978] Re: KVM images lose connectivity with bridged network Soren, We have a 12.04 based OpenStack cluster with 4 host nodes running about 30 VMs currently. We performed the steps to add the kvm-network-hang repo and updated to the latest version on the host machines, then rebooted the instances. My understanding is that this should catch the update, since a new KVM command is run on reboot. I caught the first failure ~12 hours after the upgrade. It had the usual symptoms: networking loss, but the VM is still up and an active VNC session was possible. I thought I just might have missed a reboot on one of the VMs, so I didn't report anything. The second failure happened yesterday, but someone else caught it and rebooted the VM. As best we can tell after the fact, it looks like the usual failure (no full harddrive, or kernel panic, or anything that got logged). As I mentioned before, we used to see at least one failure per day, usually much more. This patch has at least reduced the occurence to a minimal amount. These non-deterministic bugs are hard to track down. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network Status in OpenStack Compute (Nova): Invalid Status in “qemu-kvm” package in Ubuntu: Fix Released Status in “qemu-kvm” source package in Precise: In Progress Bug description: = SRU Justification: 1. Impact: networking breaks after awhile in kvm guests using virtio networking 2. Development fix: The bug was fixed upstream and the fix picked up in a new merge. 3. Stable fix: 3 virtio patches are cherrypicked from upstream: a821ce5 virtio: order index/descriptor reads 92045d8 virtio: add missing mb() on enable notification a281ebc virtio: add missing mb() on notification 4. Test case: Create a bridge enslaving the real NIC, and use that as the bridge for a kvm instance with virtio networking. See comment #44 for specific test case. 5. Regression potential: Should be low as several people have tested the fixed package under heavy load. = System: --- Dell R410 Dual processor 2.4Ghz w/16G RAM Distributor ID: Ubuntu Description:Ubuntu 12.04 LTS Release:12.04 Codename: precise Setup: - We're running 3 KVM guests, all Ubuntu 12.04 LTS using bridged networking. From the host: # cat /etc/network/interfaces auto br0 iface br0 inet static address 212.XX.239.98 netmask 255.255.255.240 gateway 212.XX.239.97 bridge_ports eth0 bridge_fd 9 bridge_hello 2 bridge_maxage 12 bridge_stp off # ifconfig eth0 eth0 Link encap:Ethernet HWaddr d4:ae:52:84:2d:5a UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11278363 errors:0 dropped:3128 overruns:0 frame:0 TX packets:14437384 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4115980743 (4.1 GB) TX bytes:5451961979 (5.4 GB) Interrupt:36 Memory:da00-da012800 # ifconfig br0 br0 Link encap:Ethernet HWaddr d4:ae:52:84:2d:5a inet addr:212.XX.239.98 Bcast:212.XX.239.111 Mask:255.255.255.240 inet6 addr: fe80::d6ae:52ff:fe84:2d5a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1720861 errors:0 dropped:0 overruns:0 frame:0 TX packets:1708622 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:210152198 (210.1 MB) TX bytes:300858508 (300.8 MB) # brctl show bridge name bridge id STP enabled interfaces br0 8000.d4ae52842d5a no eth0 I have no default network configured to autostart in libvirt as we're using bridged networking: # virsh net-list --all Name State Autostart - default inactive no # arp Address HWtype HWaddress Flags Mask Iface
[Bug 1045444] Re: amavisd-new tries to load perl modules that don't exist
James stated indeed I was unable to reproduce this issue on a clean 12.04 server install. That is odd. I also did a clean install of 12.04 Server 64-bit and when running 'amavisd-new debug' I also see: Sep 9 04:48:00.011 sfa.example.com /usr/sbin/amavisd-new[9607]: Perl version 5.014002 Sep 9 04:48:00.033 sfa.example.com /usr/sbin/amavisd-new[9607]: INFO: no optional modules: unicore::Canonical.pl unicore::Exact.pl unicore::PVA.pl # spamassassin -V SpamAssassin version 3.3.2 running on Perl version 5.14.2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1045444 Title: amavisd-new tries to load perl modules that don't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1045444/+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 997978] Re: KVM images lose connectivity with bridged network
I installed the new packages on Monday and have not had any issues. That said, I was only experiencing failures once every 3-4 weeks. So I don't think my data point will be valid for at least a few weeks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+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 997978] Re: KVM images lose connectivity with bridged network
Regarding comment #55: I don't believe this is a guest OS issue. In my comment #51 I also indicate that I have had non-precise vm's (specifically 11.10) experience the same issue. I have only experienced this issue when using 12.04 precise as the host OS. On a customer server which I back-dated by reinstalling 11.10 as the host OS, the issue went away. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+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 997978] Re: KVM images lose connectivity with bridged network
Hi Serge, I would be willing to install your ppa packages. The only issue on my end is that this problem only occurs every 3-4 weeks for me. So I don't think I would be able to give any sort of concrete feedback for whether it addresses the issue or not. My customer's server was having the issue several times per week, but I had to take action pretty quickly to keep them happy and chose to backdate to 11.10. After 9 days, they have not had the issue, which lends more evidence that it is not a guest-based issue but host-based. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+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 997978] Re: KVM images lose connectivity with bridged network
I have seen this issue on 2 different servers which use bridging but not bonding. One server was a customer system and we were forced to back-date the OS to an earlier release. They were experiencing the issue up to once/day and quickly got impatient to have it resolved. The other server is an internal system which runs multiple vm's. We have only seen the issue on one of the vm's and only once every 2-3 weeks. The vm which experiences the issue is our LTSP server. I have been testing a small cluster of 3 host machines which use both bonding and bridging. I have not seen this issue affect them, but the usage is quite light and the vm's come go since it's a testing environment right now. Due to this bug, we have halted any plans to upgrade vm hosts to Precise until we can verify it's fixed. We've seen the following when the issue has occurred: * Absolutely nothing in any logs, dmesg, etc. * Host machine cannot ping the guest * arp shows guest as incomplete * guest machine can ping its own IP, but nothing else (host, gw, etc) * restarting networking subsystem is successful (no errors) but has no effect on the problem * rebooting the guest fixes the problem until it happens again. The reboot does not actually kill the kvm session and get a new process ID, but somehow having the guest go through the init again fixes it (until it happens again some period later). * This issue has occurred on one 12.04 guest and one 11.10 guest * Both of the servers which this occured on are Dell 2950 series machines. I have not seen this issue on any of our HP Proliant (mostly DL360's) machines. If there is some sort of test I can run to help debug, I'm happy to do that. Thank you for trying to address this. This is a huge bug for us. Thanks, gary -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+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 924281] Re: cgroup-lite not installable inside 'lxc create -t ubuntu' container
If someone encounters these symptoms in Precise, the more detailed instructions to fix it is to adjust apparmor as described in http://www.stgraber.org/2012/05/04/lxc-in-ubuntu-12-04-lts/ , in the section labeled Container nesting. The apparmor change is part of Quantal, so the blog post's steps should no longer be necessary after Precise. -- 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/924281 Title: cgroup-lite not installable inside 'lxc create -t ubuntu' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924281/+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 1014916] Re: simultaneously started lucid containers pause while starting after the first seven
Note that the workaround helps significantly but is not always sufficient. If I do not apply it, I can reliably encounter the problem every single test run. Another team is working on moving us to run on Precise in production, which would let us use Precise containers. Precise containers do not appear to trigger the problem. Because of this, I will advise that we wait on pursuing the problem. -- 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/1014916 Title: simultaneously started lucid containers pause while starting after the first seven To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1014916/+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 1014916] Re: simultaneously started lucid containers pause while starting after the first seven
This was working very well for us, and the lxc-start-ephemeral TRIES=60 was working fine. Starting last week, we began seeing recurrence of this problem, even with the workarounds applied and TRIES hacked to 180. I intend to circle around with Serge and see if he has any other ideas. -- 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/1014916 Title: simultaneously started lucid containers pause while starting after the first seven To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1014916/+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 1020088] [NEW] package clamav-base 0.97.5+dfsg-1ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: clam nevarever load and say there is a problem in terminal and synaptic ProblemType: Package DistroRelease: Ubuntu 12.04 Package: clamav-base 0.97.5+dfsg-1ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 ApportVersion: 2.0.1-0ubuntu8 AptOrdering: clamav-base: Configure clamav-freshclam: Configure clamav: Configure clamtk: Configure Architecture: i386 Date: Mon Jul 2 06:02:39 2012 DuplicateSignature: Setting up clamav-base (0.97.5+dfsg-1ubuntu0.12.04.1) ... install: cannot stat `/usr/share/doc/clamav-base/examples/main.cvd': No such file or directory dpkg: error processing clamav-base (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) PackageArchitecture: all SourcePackage: clamav Title: package clamav-base 0.97.5+dfsg-1ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-06-14 (18 days ago) ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1020088 Title: package clamav-base 0.97.5+dfsg-1ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1020088/+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 1020088] Re: package clamav-base 0.97.5+dfsg-1ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1020088 Title: package clamav-base 0.97.5+dfsg-1ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1020088/+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 962393] Re: Installation loops in db-config-common when ran from software-center
** Changed in: software-center (Ubuntu) Status: New = Confirmed ** Changed in: software-center (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/962393 Title: Installation loops in db-config-common when ran from software-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/962393/+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 1014916] Re: simultaneously started lucid containers pause while starting after the first seven
Serge, thank you! The workaround appears to work very well for us. The containers started quickly, and it should not only give us more reliable starts but also seems to have taken at least three minutes off our average run time, as you might expect. -- 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/1014916 Title: simultaneously started lucid containers pause while starting after the first seven To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1014916/+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 1014916] [NEW] simultaneously started lucid containers pause while starting after the first seven
Public bug reported: We are gathering more data, but it feels like we have enough to start a bug report. On Precise, on a 16 core/32 thread EC2 machine (instance type cc2.8xlarge), when starting approximately eight or more Lucid containers simultaneously, after the first seven or so connect to dnsmasq within just a few seconds, the next group takes just under three minutes to connect. We will provide short steps to duplicate this. We also have past experience indicating that more grouping occurs, because simultaneously starting 32 containers occasionally (about once in 15 attempts) will result in one container that still has not connected to dnsmasq after ten minutes. We have not tried to duplicate this, because we hope that tackling the smaller issue will also address the larger one. I have not yet had enough disk space on this machine to duplicate this without lxc-start-ephemeral. I intend to do so. I have tried with a precise container. *Precise containers do not exhibit this bug* in the experiment I performed, at least up to 16 containers. I plan to duplicate this at least a couple more times to verify, but I'm comfortable saying initially that I believe this is specific to Lucid containers. I'll report back. To duplicate (again, I am doing this on a specific EC2 machine with a lot of cores, but I believe you can see something similar to this even on a 4 core/8 hyperthread machine): sudo apt-get install moreutils sudo lxc-create -t ubuntu -n lucid -- -r lucid -a i386 -b ubuntu parallel -j 16 bash -c lxc-start-ephemeral -d -o lucid -- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Now look at /var/log/syslog at the most recent dnsmasq entries. You will see about seven containers get DHCPACK from dnsmasq within about 20 seconds; then you will see a pause of about three minutes; then you will see more containers report to dnsmasq. Here's an excerpt (the approximate three minute jump happens between lines 5 and 6): ... Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPACK(lxcbr0) 10.0.3.161 00:16:3e:38:9f:e2 lptests-temp-5uKcEua Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPREQUEST(lxcbr0) 10.0.3.37 00:16:3e:9c:ae:16 Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPACK(lxcbr0) 10.0.3.37 00:16:3e:9c:ae:16 lptests-temp-1HxiwbU Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPREQUEST(lxcbr0) 10.0.3.62 00:16:3e:69:83:2b Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPACK(lxcbr0) 10.0.3.62 00:16:3e:69:83:2b lptests-temp-6o30rvH Jun 18 20:43:05 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:0d:7b:65 Jun 18 20:43:05 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.203 00:16:3e:0d:7b:65 Jun 18 20:43:08 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:32:5b:99 Jun 18 20:43:08 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.68 00:16:3e:32:5b:99 Jun 18 20:43:11 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:7c:21:38 Jun 18 20:43:11 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.35 00:16:3e:7c:21:38 Jun 18 20:43:14 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:72:0c:64 Jun 18 20:43:14 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.208 00:16:3e:72:0c:64 Jun 18 20:43:17 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:ed:b3:a0 Jun 18 20:43:17 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.82 00:16:3e:ed:b3:a0 Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:e3:8f:1a Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.247 00:16:3e:e3:8f:1a Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:5c:99:20 Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.225 00:16:3e:5c:99:20 Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:ed:b3:a0 Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.82 00:16:3e:ed:b3:a0 Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPREQUEST(lxcbr0) 10.0.3.203 00:16:3e:0d:7b:65 Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPACK(lxcbr0) 10.0.3.203 00:16:3e:0d:7b:65 lptests-temp-C5po26y ... What I expect to see is all of the containers reporting without a three minute break, so that all containers are ready for work much sooner. I looked in the syslogs of the started containers. The first one to connect to dnsmasq *after* the three minute pause showed a three minute pause in its own syslog. This is an excerpt from the syslog of that machine (notice the jump between 20:40 to 20:43). The udevtrigger post-stop process lines and following dhclient startup lines, down through the plymouth-splash line, are not found in the two fast machine syslogs that I looked at. Jun 18 20:40:10
[Bug 1014916] Re: simultaneously started lucid containers pause while starting after the first seven
** Description changed: We are gathering more data, but it feels like we have enough to start a bug report. On Precise, on a 16 core/32 thread EC2 machine (instance type cc2.8xlarge), when starting approximately eight or more Lucid containers - simultaneously, after the first seven or so connect to dnsmasq within - just a few seconds, the next group takes just under three minutes to - connect. We will provide short steps to duplicate this. + simultaneously: after the first seven or so connect to dnsmasq within + just a few seconds, the next group waits just under three minutes before + they start to connect. - We also have past experience indicating that more grouping occurs, - because simultaneously starting 32 containers occasionally (about once - in 15 attempts) will result in one container that still has not - connected to dnsmasq after ten minutes. We have not tried to duplicate - this, because we hope that tackling the smaller issue will also address - the larger one. + This affects our ability to ssh into the containers and do work. - I have not yet had enough disk space on this machine to duplicate this - without lxc-start-ephemeral. I intend to do so. - - I have tried with a precise container. *Precise containers do not - exhibit this bug* in the experiment I performed, at least up to 16 - containers. I plan to duplicate this at least a couple more times to - verify, but I'm comfortable saying initially that I believe this is - specific to Lucid containers. I'll report back. + We will provide short steps to duplicate this. Please note also the + extra data we include at the end of this report, showing experiments we + have run to rule out certain causes and scenarios. To duplicate (again, I am doing this on a specific EC2 machine with a lot of cores, but I believe you can see something similar to this even on a 4 core/8 hyperthread machine): sudo apt-get install moreutils sudo lxc-create -t ubuntu -n lucid -- -r lucid -a i386 -b ubuntu parallel -j 16 bash -c lxc-start-ephemeral -d -o lucid -- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Now look at /var/log/syslog at the most recent dnsmasq entries. You - will see about seven containers get DHCPACK from dnsmasq within about 20 - seconds; then you will see a pause of about three minutes; then you will - see more containers report to dnsmasq. Here's an excerpt (the - approximate three minute jump happens between lines 5 and 6): + will see that about seven containers get DHCPACK from dnsmasq within + about 20 seconds; then you will see a pause of about three minutes; then + you will see more containers report to dnsmasq. Here's an excerpt (the + approximate three minute jump happens between lines 5 and 6, and then I + include all lines up to the next ACK): ... Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPACK(lxcbr0) 10.0.3.161 00:16:3e:38:9f:e2 lptests-temp-5uKcEua - Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPREQUEST(lxcbr0) 10.0.3.37 00:16:3e:9c:ae:16 + Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPREQUEST(lxcbr0) 10.0.3.37 00:16:3e:9c:ae:16 Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPACK(lxcbr0) 10.0.3.37 00:16:3e:9c:ae:16 lptests-temp-1HxiwbU - Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPREQUEST(lxcbr0) 10.0.3.62 00:16:3e:69:83:2b + Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPREQUEST(lxcbr0) 10.0.3.62 00:16:3e:69:83:2b Jun 18 20:40:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPACK(lxcbr0) 10.0.3.62 00:16:3e:69:83:2b lptests-temp-6o30rvH - Jun 18 20:43:05 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:0d:7b:65 - Jun 18 20:43:05 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.203 00:16:3e:0d:7b:65 - Jun 18 20:43:08 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:32:5b:99 - Jun 18 20:43:08 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.68 00:16:3e:32:5b:99 - Jun 18 20:43:11 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:7c:21:38 - Jun 18 20:43:11 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.35 00:16:3e:7c:21:38 - Jun 18 20:43:14 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:72:0c:64 - Jun 18 20:43:14 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.208 00:16:3e:72:0c:64 - Jun 18 20:43:17 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:ed:b3:a0 - Jun 18 20:43:17 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.82 00:16:3e:ed:b3:a0 - Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:e3:8f:1a - Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPOFFER(lxcbr0) 10.0.3.247 00:16:3e:e3:8f:1a - Jun 18 20:43:20 ip-10-58-49-120 dnsmasq-dhcp[7546]: DHCPDISCOVER(lxcbr0) 10.0.3.123 00:16:3e:5c:99:20 - Jun 18 20:43:20 ip-10-58-49-120
[Bug 994752] Re: lxc-start-ephemeral's use of dhcp lease table is fragile
The improvement in the new version is significant, and there is no regression. The improvement is still insufficient for our use case, as I noted would be likely in the updated description. For our use case of 32 LXC containers running on a 32 core (16 hyperthreaded) EC2 box, 21 ephemeral containers were able to correctly complete, with 11 timing out. Previously, a maximum of 11 were able to correctly complete experimentally, and 20+ timed out. In sum, we will need something more--a configurable timeout, or a much larger timeout, like 300. However, the proposed package is good--a very nice improvement in many ways--and I don't see any reason not to release it. -- 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/994752 Title: lxc-start-ephemeral's use of dhcp lease table is fragile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994752/+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 994752] Re: lxc-start-ephemeral's use of dhcp lease table is fragile
** Description changed: [Impact] - fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + This affects anyone using lxc-start-ephemeral as part of an automated process for which intermittent failures are a problem. This includes the people who developed the initial version of the script, the Launchpad developers. Our automated test suite will fail, stopping our landing tools, whenever this failure is triggered. [Development Fix] - fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + 1. no longer look in the container's file system for a dhcp table to get the ip of the container; instead, look in the host's network information. This is more reliable and ready sooner. r101 of quantal lxc package has this change. + 2. increase the timeout waiting for the containers' network and sshd to be ready. + + Note that the current increase, from 30 retries @ 1/sec to 60 retries @ + 1/sec, is insufficient for the people who filed the bug, unfortunately. + Making the retry count configurable would be ideal. Increasing it to + 300 would be sufficient, based on our experience so far. stgraber + suggested using the `parallel -l maxload` construct to keep the starts + from being overwhelmed by load. Unfortunately, we believe that this is + insufficient for at least two reasons. First, the point of our effort + is to do a lot of work in parallel, with an lxc per core. The work we + have to do takes more than half an hour. Waiting for load to decrease + would miss the point of the effort. Second, it doesn't seem that cpu + contention is always the problem, from watching top. [Stable Fix] - fill me in by pointing out a minimal patch applicable to the stable version of the package. + [stgraber will need to specify] [Text Case] - fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. - 1. - 2. - 3. - Broken Behavior: - Fixed Behavior: + + 1. Create an lxc container (which has sshd running and your home directory mounter, as is the default). For the sake of these instructions, we will call it lxctest. + 2. Run something like this. Replace username with your user name. You might need to do this more or fewer times; we've seen it most easily on a 32 core (16 core hyperthreaded) machine trying to run 32 concurrent callsTo make this less annoying, you could create a temporary passphraseless ssh key. + + parallel -j 16 bash -c lxc-start-ephemeral -u gary -o lpdev -- 'cat + /etc/hostname' -- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 + + Do this a few times. + + Broken Behavior: At least one of the times, at least one of these fail (emitting an error message rather than the hostname) either because the code could not get the ip address in time, or because the container's sshd wasn't ready in time. + Fixed Behavior: You get all 16 hostnames. [Regression Potential] - fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + The increased timeout might cause some code to wait longer than before to discover that something is wrong. The improved ip code should have no negative effect. [Original Report]When lxc-start-ephemeral is given a command to run (-- do_something) it wants to use lxc-attach to run the command, but lxc- attach is not ready yet. Instead, it parses the dhcp leases to figure out the IP for the container, and then tries to use ssh to run the command. Twice today in tests involving lxc-start-ephemeral, the dhcp leases were unavailable and lxc-start-ephemeral failed. The machine was under fairly heavy load and was virtualized (EC2). I'd like to try and make this less fragile. As discussed on IRC, using lxcip (http://bazaar.launchpad.net/~launchpad/lpsetup/trunk/files/head:/lplxcip/) should make this more reliable. Perhaps increasing the timeout in that code might be useful as well. -- 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/994752 Title: lxc-start-ephemeral's use of dhcp lease table is fragile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994752/+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 994752] [NEW] lxc-start-ephemeral's use of dhcp lease table is fragile
Public bug reported: When lxc-start-ephemeral is given a command to run (-- do_something) it wants to use lxc-attach to run the command, but lxc-attach is not ready yet. Instead, it parses the dhcp leases to figure out the IP for the container, and then tries to use ssh to run the command. Twice today in tests involving lxc-start-ephemeral, the dhcp leases were unavailable and lxc-start-ephemeral failed. The machine was under fairly heavy load and was virtualized (EC2). I'd like to try and make this less fragile. As discussed on IRC, using lxcip (http://bazaar.launchpad.net/~launchpad/lpsetup/trunk/files/head:/lplxcip/) should make this more reliable. Perhaps increasing the timeout in that code might be useful as well. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/994752 Title: lxc-start-ephemeral's use of dhcp lease table is fragile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994752/+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 924337] Re: lxc on precise is not working with lucid containers (container does not reach runlevel 2)
Salgado, would you be able to do this verification? If not, let me know, and I'll do it. -- 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/924337 Title: lxc on precise is not working with lucid containers (container does not reach runlevel 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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 974584] Re: celery tests fail on parallel testing instances
This is easily and repeatably duplicatable on in my lxc lucid container.
The error for the last test (with the multiprocessing SemLock OSError
seems the most likely to be a shared root cause to me. Interestingly,
the OSError was slightly different for me, with a newer lxc: OSError:
[Errno 38] Function not implemented. I checked the syslog and some
random other log files, without really knowing where to look, and saw
nothing of interest.
As you'd expect from the traceback, you can repeat this error with a
single Python call to the standard library.
from multiprocessing import synchronize
synchronize.Lock()
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.6/multiprocessing/synchronize.py, line 117, in
__init__
SemLock.__init__(self, SEMAPHORE, 1, 1)
File /usr/lib/python2.6/multiprocessing/synchronize.py, line 49, in __init__
sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 38] Function not implemented
38 is ENOSYS
I talked with hallyn and this is an lxc issue. Adding this line to the
container's fstab will fix the problem:
none dev/shm tmpfs defaults 0 0
He is updating the ubuntu template with this change.
** Changed in: launchpad
Status: Triaged = Invalid
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- celery tests fail on parallel testing instances
+ Semaphores cannot be created in lxc container
** Description changed:
- The same three tests failed consistently over several runs:
+ from multiprocessing import synchronize
+ synchronize.Lock()
+ Traceback (most recent call last):
+ File stdin, line 1, in module
+ File /usr/lib/python2.6/multiprocessing/synchronize.py, line 117, in
__init__
+ SemLock.__init__(self, SEMAPHORE, 1, 1)
+ File /usr/lib/python2.6/multiprocessing/synchronize.py, line 49, in
__init__
+ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
+ OSError: [Errno 38] Function not implemented
+ Thanks to hallyn, there's a workaround and a fix: adding this line to the
container's fstab will fix the problem:
+ none dev/shm tmpfs defaults 0 0
- ==
- FAIL:
lp.code.model.tests.test_branch.TestBranchJobViaCelery.test_destroySelf_via_celery
- --
- Traceback (most recent call last):
- _StringException: librarian-log: {{{
- 2012-04-05 19:56:24+0530 [-] Log opened.
- 2012-04-05 19:56:24+0530 [-] twistd 11.1.0 (/usr/bin/python2.6 2.6.5)
starting up.
- 2012-04-05 19:56:24+0530 [-] reactor class:
twisted.internet.pollreactor.PollReactor.
- 2012-04-05 19:56:24+0530 [-] FileUploadFactory starting on 58125
- 2012-04-05 19:56:24+0530 [-] Starting factory
lp.services.librarianserver.libraryprotocol.FileUploadFactory instance at
0xa2e90ec
- 2012-04-05 19:56:24+0530 [-] Site starting on 51003
- 2012-04-05 19:56:24+0530 [-] Starting factory twisted.web.server.Site
instance at 0xa2e94ac
- 2012-04-05 19:56:24+0530 [-] FileUploadFactory starting on 51219
- 2012-04-05 19:56:24+0530 [-] Starting factory
lp.services.librarianserver.libraryprotocol.FileUploadFactory instance at
0xa2e978c
- 2012-04-05 19:56:24+0530 [-] Site starting on 35098
- 2012-04-05 19:56:24+0530 [-] Starting factory twisted.web.server.Site
instance at 0xa2e96ac
- 2012-04-05 19:56:24+0530 [-] Not using upstream librarian
- 2012-04-05 19:56:24+0530 [-] daemon ready!
- }}}
+ He is updating the ubuntu template with this change.
- Traceback (most recent call last):
- File
/var/lib/buildbot/slaves/slave/lucid-devel/build/lib/lp/code/model/tests/test_branch.py,
line 364, in test_destroySelf_via_celery
- self.assertThat(branch_path, Not(PathExists()))
- MismatchError: '/var/tmp/bazaar.launchpad.dev/mirrors/00/00/00/4d' matches
MatchesPredicate(function exists at 0xf73b5df4, '%s does not exist.')
- ==
- ERROR:
lp.code.model.tests.test_branch.TestBranchUpgrade.test_requestUpgradeUsesCelery
- --
- Traceback (most recent call last):
- _StringException: librarian-log: {{{
- 2012-04-05 19:55:15+0530 [-] Log opened.
- 2012-04-05 19:55:15+0530 [-] twistd 11.1.0 (/usr/bin/python2.6 2.6.5)
starting up.
- 2012-04-05 19:55:15+0530 [-] reactor class:
twisted.internet.pollreactor.PollReactor.
- 2012-04-05 19:55:15+0530 [-] FileUploadFactory starting on 39820
- 2012-04-05 19:55:15+0530 [-] Starting factory
lp.services.librarianserver.libraryprotocol.FileUploadFactory instance at
0xa6d10ec
- 2012-04-05 19:55:15+0530 [-] Site starting on 53904
- 2012-04-05 19:55:15+0530 [-] Starting factory twisted.web.server.Site
instance at 0xa6d14ac
- 2012-04-05 19:55:15+0530 [-] FileUploadFactory starting on 51169
- 2012-04-05 19:55:15+0530 [-] Starting factory
[Bug 969374] Re: package mysql-server-5.1 5.1.58-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 100
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/969374 Title: package mysql-server-5.1 5.1.58-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/969374/+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 969604] [NEW] lxc-stop should be able to handle ephemeral containers more robustly
Public bug reported: It is possible to have an ephemeral container remaining after lxc-start- ephemeral has been killed--trivially by calling kill -9 on lxc-start- ephemeral. At that point, the script does not get a chance to clean up after itself, and the system is left with a running ephemeral container as well as several mounts. lxc-stop can stop the container, but after an ephemeral container is stopped, it ought to be destroyed, and it is not. Moreover, if you then try to use lxc-destroy, it will fail, because the ephemeral container's directory is mounted, with another directory mounted inside (ephemeralbind). Moreover again, if you succeed in umounting those directories, and then destroying the container, there is still a tmpfs /tmp/lxc-lp-XXX directory (I suspect that lp segment of the name is no longer appropriate, btw) hidden away consuming undefined amounts amount of memory that would ideally have been removed for the user. We have a script to handle this possibility in an automated way. Beyond handling the above, it does one more thing that lxc-stop can't do now: it finds all of the ephemeral containers via a glob, to allow the automated script to not have to know what temporary name the ephemeral container has. An equivalent would be lxc-stop -n lptests-tmp-*. It would be nice if lxc-stop could handle properly destroying ephemeral containers when they are stopped. (Perhaps this could even be a step along the way to the non-COMMAND version of lxc-start-ephemeral ending simply with either lxc-start -n $NAME or lxc-start -d -n $NAME.) It would be even more nice if lxc-stop could handle globs, so we could do away with our script. The least obvious aspect of the implementation I see is how to know what /tmp/lxc-lp-* directory to remove. The best I can come up with is parsing the output of mount to find the tmp directory used as the upperdir for the primary overlayfs. This would be a bit more lines of code if you wanted to support aufs, but still doable. If it's not already clear, I personally consider this a low priority nice-to-have. Thank you ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/969604 Title: lxc-stop should be able to handle ephemeral containers more robustly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969604/+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 969604] Re: lxc-stop should be able to handle ephemeral containers more robustly
I agree. I was thinking as I wrote this that we would be awfully close to being able to get rid of the -- COMMAND stuff if this were implemented, for instance; and generally close to being able to make lxc-start-ephemeral behave very similarly to lxc-start in terms of interaction patterns. Unfortunately I won't be at UDS. -- 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/969604 Title: lxc-stop should be able to handle ephemeral containers more robustly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/969604/+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 959352] Re: Ephemeral containers have /rootfs prefix in /proc/self/maps entries
I have duped the problem Benji reported, and did the kernel test in order to let him work on other tasks. The given kernel (reported in /proc/version as Linux version 3.3.0-030300-generic (apw@gomeisa) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1) ) #201203182135 SMP Mon Mar 19 01:36:20 UTC 2012) does not appear to have overlayfs or aufs compiled in, so I was unable to test as requested (http://pastebin.ubuntu.com/905562/). I'm happy to try again if given updated instructions. ** Tags added: kernel-unable-to-test-upstream -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 968371] [NEW] lxc-create -b is broken
Public bug reported: The -b flag in current Precise lxc-create sets up an fstab that has $homedir $homedir none bind 0 0 instead of $homedir /var/lib/lxc/$container/rootfs/$homedir none bind 0 0. This doesn't seem to work, which is a regression. I created a container with this: $ sudo lxc-create -t ubuntu -n lptests -- -r lucid -a i386 -b gary This resulted in an fstab for that container that looked like this: $ cat /var/lib/lxc/lptests/fstab procproc procnodev,noexec,nosuid 0 0 sysfs sys sysfs defaults 0 0 /home/gary /home/gary none bind 0 0 I expected to see an fstab that looked like this older instance: $ cat /var/lib/lxc/lpdev/fstab proc/var/lib/lxc/lpdev/rootfs/proc proc nodev,noexec,nosuid 0 0 sysfs /var/lib/lxc/lpdev/rootfs/sys sysfs defaults 0 0 /home/gary /var/lib/lxc/lpdev/rootfs//home/gary none bind 0 0 Starting the new container gives me an empty home directory, rather than my bound home directory from the host. If I edit fstab as follows then the new container does give me a bound home directory from the host as I expect. $ cat /var/lib/lxc/lptests/fstab procproc procnodev,noexec,nosuid 0 0 sysfs sys sysfs defaults 0 0 /home/gary /var/lib/lxc/lptests/rootfs/home/gary none bind 0 0 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/968371 Title: lxc-create -b is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/968371/+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 959352] Re: Ephemeral containers have /rootfs prefix in /proc/self/maps entries
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352/+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 960262] [NEW] include an option to use aufs instead of overlayfs in lxc-start-ephemeral
Public bug reported: Because of the problems we've encountered with overlayfs over the past couple of months, and because aufs did seem to be working earlier, I'd like it if we could have an option to use aufs with lxc-start-ephemeral. Because overlayfs is the well-advertised future and aufs is the deprecated past, and because we currently have workarounds for the known overlayfs issues, I'd like overayfs to continue to be the default. If this doesn't make into Precise, it is not essential: we can always make our own version of the script later if necessary. However, this would be nice to have. Thank you ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/960262 Title: include an option to use aufs instead of overlayfs in lxc-start- ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/960262/+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 959352] Re: Ephemeral containers have /rootfs prefix in /proc/self/maps entries
We are discovering that this, or something very similar to it, is serious. For our own use, at least, I'd raise this to high (we don't have privileges to do so). According to lsof, many, many processes (sshd, upstart, init, ntpd, etc., as well as processes we start directly such as xvfb-run and our own code are looking in the wrong place (/rootfs/...) for important and sometimes essential files, including /rootfs/dev/random, /rootfs/dev/null, /rootfs/lib/tls ... , /rootfs/lib/security... , /rootfs/lib/libdbus-1.so.3.4.0, /rootfs/lib/libcom_err.so.2.1, /rootfs/usr/lib/libkrb5.so.3.3, and so on. We could maybe make symlinks for /rootfs/usr, /rootfs/lib, and /rootfs/dev but that feels like we're going too far, and that we really ought to address this. I'm not sure where to look to fix this. Is there something else important we are missing from lxc-clone? Help would be very appreciated. Thank you -- 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/959352 Title: Ephemeral containers have /rootfs prefix in /proc/self/maps entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/959352/+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 959352] Re: Ephemeral containers have /rootfs prefix in /proc/self/maps entries
Hi Serge. Thanks for looking at this. On an aufs-mounted ephemeral: gary@lpdev-temp-tKJg9Ss:~$ cat /proc/self/maps 08048000-08054000 r-xp 08:12 414657 /var/lib/lxc/lpdev/rootfs/bin/cat 08054000-08055000 r--p b000 08:12 414657 /var/lib/lxc/lpdev/rootfs/bin/cat 08055000-08056000 rw-p c000 08:12 414657 /var/lib/lxc/lpdev/rootfs/bin/cat 09aba000-09adb000 rw-p 00:00 0 [heap] f7629000-f762a000 rw-p 00:00 0 f762a000-f777d000 r-xp 08:12 395454 /var/lib/lxc/lpdev/rootfs/lib/tls/i686/cmov/libc-2.11.1.so f777d000-f777f000 r--p 00153000 08:12 395454 /var/lib/lxc/lpdev/rootfs/lib/tls/i686/cmov/libc-2.11.1.so f777f000-f778 rw-p 00155000 08:12 395454 /var/lib/lxc/lpdev/rootfs/lib/tls/i686/cmov/libc-2.11.1.so f778-f7783000 rw-p 00:00 0 f778d000-f778f000 rw-p 00:00 0 f778f000-f779 r-xp 00:00 0 [vdso] f779-f77ab000 r-xp 08:12 393068 /var/lib/lxc/lpdev/rootfs/lib/ld-2.11.1.so f77ab000-f77ac000 r--p 0001a000 08:12 393068 /var/lib/lxc/lpdev/rootfs/lib/ld-2.11.1.so f77ac000-f77ad000 rw-p 0001b000 08:12 393068 /var/lib/lxc/lpdev/rootfs/lib/ld-2.11.1.so ffd7f000-ffda rw-p 00:00 0 [stack] gary@lpdev-temp-tKJg9Ss:~$ cat /proc/self/mounts rootfs / rootfs rw 0 0 none / aufs rw,relatime,si=bf91329ce378bd10,noplink 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /home/gary aufs rw,relatime,si=bf91329dec9efd10,noplink 0 0 devpts /dev/console devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty1 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty2 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty3 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty4 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=666 0 0 devpts /dev/ptmx devpts rw,relatime,mode=600,ptmxmode=666 0 0 none /lib/init/fstab aufs rw,relatime,si=bf91329ce378bd10,noplink 0 0 On an overlayfs-mounted ephemeral: gary@lpdev-temp-P4zdc8P:~$ cat /proc/self/maps 08048000-08054000 r-xp 08:12 414657 /rootfs/bin/cat 08054000-08055000 r--p b000 08:12 414657 /rootfs/bin/cat 08055000-08056000 rw-p c000 08:12 414657 /rootfs/bin/cat 09081000-090a2000 rw-p 00:00 0 [heap] f7586000-f7587000 rw-p 00:00 0 f7587000-f76da000 r-xp 08:12 395454 /rootfs/lib/tls/i686/cmov/libc-2.11.1.so f76da000-f76dc000 r--p 00153000 08:12 395454 /rootfs/lib/tls/i686/cmov/libc-2.11.1.so f76dc000-f76dd000 rw-p 00155000 08:12 395454 /rootfs/lib/tls/i686/cmov/libc-2.11.1.so f76dd000-f76e rw-p 00:00 0 f76ea000-f76ec000 rw-p 00:00 0 f76ec000-f76ed000 r-xp 00:00 0 [vdso] f76ed000-f7708000 r-xp 08:12 393068 /rootfs/lib/ld-2.11.1.so f7708000-f7709000 r--p 0001a000 08:12 393068 /rootfs/lib/ld-2.11.1.so f7709000-f770a000 rw-p 0001b000 08:12 393068 /rootfs/lib/ld-2.11.1.so ff936000-ff957000 rw-p 00:00 0 [stack] gary@lpdev-temp-P4zdc8P:~$ cat /proc/self/mounts rootfs / rootfs rw 0 0 none / overlayfs rw,relatime,lowerdir=/var/lib/lxc/lpdev,upperdir=/tmp/lxc-lp-8lXebKT 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /home/gary overlayfs rw,relatime,lowerdir=/home/gary,upperdir=/var/lib/lxc/lpdev-temp-P4zdc8P/ephemeralbind/home/gary 0 0 devpts /dev/console devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty1 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty2 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty3 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/tty4 devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=666 0 0 devpts /dev/ptmx devpts rw,relatime,mode=600,ptmxmode=666 0 0 none /lib/init/fstab overlayfs rw,relatime,lowerdir=/var/lib/lxc/lpdev,upperdir=/tmp/lxc-lp-8lXebKT 0 0 The maps are obviously different. The rootfs is not in the aufs version, but then the paths are from the host, and for the template container. I'm not sure what to make
[Bug 954632] [NEW] The -- option to lxc-start-ephemeral no longer works
Public bug reported:
This fixes it:
=== modified file 'debian/local/lxc-start-ephemeral'
--- debian/local/lxc-start-ephemeral2012-03-12 13:22:06 +
+++ debian/local/lxc-start-ephemeral2012-03-14 01:10:20 +
@@ -100,6 +100,8 @@
esac
done
+COMMAND=$@
+COMMAND_LENGTH=$#
LXC_USER=${LXC_USER:-`id -un`}
# validation
@@ -193,7 +195,7 @@
sudo lxc-start -n $LXC_NAME -d
LXC_RUNNING=1
-if [ $# -gt 0 ]; then
+if [ $COMMAND_LENGTH -gt 0 ]; then
# when lxc-attach support arrives in the kernel, we can switch to
# that
delay=30
@@ -209,7 +211,7 @@
# Repeatedly try to connect over SSH until we either succeed
# or time out.
for i in $(seq 1 30); do
-ssh -n -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
$LXC_KEY $LXC_USER@$IP_ADDRESS -- $@
+ssh -n -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
$LXC_KEY $LXC_USER@$IP_ADDRESS -- $COMMAND
if [ ! 255 -eq $? ]; then
# If ssh returns 255 then its connection failed.
# Anything else is either success (status 0) or a
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/954632
Title:
The -- option to lxc-start-ephemeral no longer works
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/954632/+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 951150] Re: lxc-start-ephemeral is not all ephemeral
Hi Serge. I don't actually know the original intent of -b, but what you say makes sense. I changed our code to change all bind mounts in the ephemeral's container to an ephemeral overlay, instead. That's kind of what I wanted anyway, but I was being lazy. :-) I also worried it would not be safe, but I thought about it some more and I think it might be fine. Also, now -b will change fstab rather than directly mounting, which simplifies some of the cleanup code. I'll add a changelog as you request. We still want to test it a bit more before we make an MP, but I'll link it now in case you have any thoughts you want to share early. Thanks! ** Branch linked: lp:~gary/ubuntu/precise/lxc/bug-951150 -- 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/951150 Title: lxc-start-ephemeral is not all ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/951150/+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 951150] [NEW] lxc-start-ephemeral is not all ephemeral
Public bug reported: The directories mounted both using the ephemeral's fstab and using -b are not ephemeral. Changes to them persist on the filesystem, and are thus shared across other ephemeral instances that mount the same directories. We have a branch that addresses this concern. We took the approach that -b should bind ephemeral directories; *and* if the destination directory is in the ephemeral's inherited fstab, we disable that mount from the fstab. Thus, if a base container's fstab mounts proc, sys, and /home/gary, and you pass -b /home/gary to lxc-start-ephemeral, /home/gary will be mounted as an ephemeral, local copy; otherwise, without the -b, the fstab entry will be mounted as usual, and /home/gary will be persisted and shared. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/951150 Title: lxc-start-ephemeral is not all ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/951150/+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 951181] [NEW] lxc-wait: bind : Address already in use.
Public bug reported: If multiple lxc-waits are run simultaneously, all after the first will fail with bind : Address already in use. This is apparently a known issue. http://comments.gmane.org/gmane.linux.kernel.containers.lxc.general/962 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/951181 Title: lxc-wait: bind : Address already in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/951181/+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 949956] [NEW] lxc-start-ephemeral keeps same MAC address, and so same IP address, as base instance
Public bug reported:
As smoser pointed out, lxc-start-ephemeral needs to do the same kinds of
things that lxc-clone does, such as this:
# change hwaddrs
mv ${c} ${c}.old
(
while read line; do
if [ ${line:0:18} = lxc.network.hwaddr ]; then
echo lxc.network.hwaddr= 00:16:3e:$(openssl rand -hex 3| sed
's/\(..\)/\1:/g; s/.$//')
else
echo $line
fi
done
) ${c}.old ${c}
rm -f ${c}.old
# set the hostname
cat EOF $rootfs/etc/hostname
$hostname
EOF
# set minimal hosts
cat EOF $rootfs/etc/hosts
127.0.0.1 localhost $hostname
EOF
We have a version that does this, and will propose it.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/949956
Title:
lxc-start-ephemeral keeps same MAC address, and so same IP address, as
base instance
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/949956/+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 945183] [NEW] lxc-start-ephemeral is difficult to use with non-ubuntu accounts
Public bug reported: Because of the current ssh approach used in lxc-start-ephemeral in lieu of lxc-attach, you need a password or key in the ubuntu account to connect. If you want to do this with automation, you can use a key. If you want to use this with another user and that user's key, you do not have an option at this time. http://paste.ubuntu.com/865767/ adds support for this scenario. We will switch -k for -S to match the ubuntu template, per Serge's suggestion ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/945183 Title: lxc-start-ephemeral is difficult to use with non-ubuntu accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/945183/+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 933779] [NEW] lxc-start-ephemeral intermittently fails to connect to container
Public bug reported: We believe sshd just hasn't started quickly enough, sometimes. Graham Binns worked out this kind of solution, if it works for you: http://pastebin.ubuntu.com/844925/ (see lines 146-157 in particular). Thanks Gary ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/933779 Title: lxc-start-ephemeral intermittently fails to connect to container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/933779/+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 925024] Re: apparmor makes it impossible to install postgresql-common on Precise
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925028] Re: apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns -EINVAL)
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/925028 Title: apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns -EINVAL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] Re: apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns -EINVAL)
** Tags added: bot-stop-nagging -- 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/925028 Title: apparmor breaks lxc-start-ephemeral (apparmor+overlayfs returns -EINVAL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925520] Re: lxc script non-root errors can be confusing
This seems related, but not identical, to bug 918327 -- 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/925520 Title: lxc script non-root errors can be confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925520/+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 925520] [NEW] lxc script non-root errors can be confusing
Public bug reported: A trivial thing, but at least a couple of people have been confused by something like this, just being forgetful: $ lxc-start -n lp lxc-start: failed to cap_get_flag: Invalid argument lxc-start: failed to create veth5HNAcN-vethyuiOEf : Operation not permitted lxc-start: failed to create netdev lxc-start: failed to create the network lxc-start: failed to spawn 'lp' lxc-start: No such file or directory - failed to remove cgroup '/sys/fs/cgroup/cpuset//lxc/lp' The fix is to simply use sudo. The error message does not communicate this clearly. I'd suggest that the lxc scripts that need to be run as root (is that all of them except lxc-list?) have a this script must be run as root error message, or similar. It's a small thing, but I think it would be appreciated by users. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/925520 Title: lxc script non-root errors can be confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925520/+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 924337] Re: lxc on precise is not working with lucid containers
I tried the fix and I got the same symptom. For clarity: - I wiped out /var/lxc/cache before I started because lxc-create wasn't working. That got lxc-create working. I used the same commands I listed in the bug description. - I changed the container's console.conf as described: $ cat /var/lib/lxc/lp/rootfs/etc/init/console.conf # /dev/console - getty # # This service maintains a getty on /dev/console from the point the # system is started until it is shut down again. # It only runs in lxc containers. # Libvirt links /dev/tty1 to /dev/pts/0. ## start on stopped rc RUNLEVEL=[2345] start on mounted MOUNTPOINT=/run stop on runlevel [!2345] env container env LIBVIRT_LXC_UUID pre-start script [ x$container = xlxc ] exit 0; stop; exit 0; end script respawn exec /sbin/getty -8 38400 /dev/console - sudo lxc-start -n lp then hangs with the exact same symptoms described initially. 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/924337 Title: lxc on precise is not working with lucid containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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 925024] [NEW] apparmor makes it impossible to install postgresql-common on Precise
Public bug reported: Repro: $ sudo lxc-create -t ubuntu -n precise -f /etc/lxc/local.conf -- -r precise -a i686 -b gary $ sudo lxc-start -n precise [log in as root] root@precise:~# apt-get install postgresql-common Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: openssl postgresql-client-common ssl-cert Suggested packages: ca-certificates openssl-blacklist The following NEW packages will be installed: openssl postgresql-client-common postgresql-common ssl-cert 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 643 kB of archives. After this operation, 1618 kB of additional disk space will be used. Do you want to continue [Y/n]? Y Get:1 http://archive.ubuntu.com/ubuntu/ precise/main openssl i386 1.0.0e-3ubuntu1 [510 kB] Get:2 http://archive.ubuntu.com/ubuntu/ precise/main postgresql-client-common all 128 [25.6 kB] Get:3 http://archive.ubuntu.com/ubuntu/ precise/main ssl-cert all 1.0.28 [12.2 kB] Get:4 http://archive.ubuntu.com/ubuntu/ precise/main postgresql-common all 128 [94.9 kB] Fetched 643 kB in 1s (482 kB/s) Preconfiguring packages ... Selecting previously unselected package openssl. (Reading database ... 12500 files and directories currently installed.) Unpacking openssl (from .../openssl_1.0.0e-3ubuntu1_i386.deb) ... Selecting previously unselected package postgresql-client-common. Unpacking postgresql-client-common (from .../postgresql-client-common_128_all.deb) ... Selecting previously unselected package ssl-cert. Unpacking ssl-cert (from .../ssl-cert_1.0.28_all.deb) ... Selecting previously unselected package postgresql-common. Unpacking postgresql-common (from .../postgresql-common_128_all.deb) ... Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common' dpkg: unrecoverable fatal error, aborting: failed to fstat previous diversions file: No such file or directory E: Sub-process /usr/bin/dpkg returned an error code (2) Workaround (thanks to wgrant): sudo ln -s /etc/apparmor.d/usr.bin.lxc-start /etc/apparmor.d/disable/ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.lxc-start Then it should work. Ideally we'd be able to keep apparmor involved. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925024/+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 925028] [NEW] apparmor breaks lxc-start-ephemeral
Public bug reported: Repro: $ sudo lxc-create -t ubuntu -n precise -f /etc/lxc/local.conf -- -r precise -a i686 -b gary $ sudo lxc-start-ephemeral -o precise Setting up ephemeral container... Starting up the container... lxc-start: Invalid argument - failed to open /var/lib/lxc/precise-temp-P3RLwXk/config lxc-start: failed to read configuration file Workaround (thanks to wgrant): $ sudo ln -s /etc/apparmor.d/usr.bin.lxc-start /etc/apparmor.disable/usr. usr.bin.firefoxusr.sbin.rsyslogd $ sudo ln -s /etc/apparmor.d/usr.bin.lxc-start /etc/apparmor.d/d isable/ $ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.lxc-start $ sudo lxc-start-ephemeral -o precise Setting up ephemeral container... Starting up the container... precise-temp-JgTN0gj is running You connect with the command: sudo lxc-console -n precise-temp-JgTN0gj ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925028/+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 924337] Re: lxc on precise is not working with lucid containers
Serge, cool. The workaround is fine. 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/924337 Title: lxc on precise is not working with lucid containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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 925028] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706220/+files/AplayDevices.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706221/+files/Card0.Amixer.values.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706222/+files/Card0.Codecs.codec.0.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706219/+files/AlsaDevices.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706224/+files/IwConfig.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706223/+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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706227/+files/PciMultimedia.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706226/+files/Lsusb.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706225/+files/Lspci.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706230/+files/ProcModules.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706229/+files/ProcInterrupts.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] PulseSinks.txt
apport information ** Attachment added: PulseSinks.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706231/+files/PulseSinks.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706234/+files/UdevDb.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706233/+files/RfKill.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] PulseSources.txt
apport information ** Attachment added: PulseSources.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706232/+files/PulseSources.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925028] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706235/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925024] Re: apparmor makes it impossible to install postgresql-common on Precise
apport information ** Tags added: apport-collected running-unity ** Description changed: Repro: $ sudo lxc-create -t ubuntu -n precise -f /etc/lxc/local.conf -- -r precise -a i686 -b gary $ sudo lxc-start -n precise [log in as root] root@precise:~# apt-get install postgresql-common Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: openssl postgresql-client-common ssl-cert Suggested packages: ca-certificates openssl-blacklist The following NEW packages will be installed: openssl postgresql-client-common postgresql-common ssl-cert 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 643 kB of archives. After this operation, 1618 kB of additional disk space will be used. Do you want to continue [Y/n]? Y Get:1 http://archive.ubuntu.com/ubuntu/ precise/main openssl i386 1.0.0e-3ubuntu1 [510 kB] Get:2 http://archive.ubuntu.com/ubuntu/ precise/main postgresql-client-common all 128 [25.6 kB] Get:3 http://archive.ubuntu.com/ubuntu/ precise/main ssl-cert all 1.0.28 [12.2 kB] Get:4 http://archive.ubuntu.com/ubuntu/ precise/main postgresql-common all 128 [94.9 kB] Fetched 643 kB in 1s (482 kB/s) Preconfiguring packages ... Selecting previously unselected package openssl. (Reading database ... 12500 files and directories currently installed.) Unpacking openssl (from .../openssl_1.0.0e-3ubuntu1_i386.deb) ... Selecting previously unselected package postgresql-client-common. Unpacking postgresql-client-common (from .../postgresql-client-common_128_all.deb) ... Selecting previously unselected package ssl-cert. Unpacking ssl-cert (from .../ssl-cert_1.0.28_all.deb) ... Selecting previously unselected package postgresql-common. Unpacking postgresql-common (from .../postgresql-common_128_all.deb) ... Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by postgresql-common' dpkg: unrecoverable fatal error, aborting: failed to fstat previous diversions file: No such file or directory E: Sub-process /usr/bin/dpkg returned an error code (2) Workaround (thanks to wgrant): sudo ln -s /etc/apparmor.d/usr.bin.lxc-start /etc/apparmor.d/disable/ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.lxc-start Then it should work. Ideally we'd be able to keep apparmor involved. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. + ApportVersion: 1.91-0ubuntu1 + Architecture: amd64 + ArecordDevices: + List of CAPTURE Hardware Devices + card 0: NVidia [HDA NVidia], device 0: Cirrus Analog [Cirrus Analog] +Subdevices: 1/1 +Subdevice #0: subdevice #0 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gary 1953 F pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + Card0.Amixer.info: + Card hw:0 'NVidia'/'HDA NVidia at 0xe748 irq 21' +Mixer name : 'Cirrus Logic CS4206' +Components : 'HDA:10134206,106b4b00,00100301' +Controls : 18 +Simple ctrls : 9 + CurrentDmesg: + Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied + dmesg: write failed: Broken pipe + DistroRelease: Ubuntu 12.04 + MachineType: Apple Inc. MacBookPro5,3 + NonfreeKernelModules: wl nvidia + Package: lxc 0.7.5-3ubuntu16 + PackageArchitecture: amd64 + ProcEnviron: + PATH=(custom, user) + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic root=UUID=44d3af31-0b7b-42d9-a0ff-d3cfb63f282d ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 + Tags: precise running-unity precise running-unity + Uname: Linux 3.2.0-12-generic x86_64 + UpgradeStatus: Upgraded to precise on 2012-01-23 (9 days ago) + UserGroups: libvirtd sudo + WifiSyslog: + + dmi.bios.date: 06/15/09 + dmi.bios.vendor: Apple Inc. + dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 + dmi.board.asset.tag: Base Board Asset Tag# + dmi.board.name: Mac-F22587C8 + dmi.board.vendor: Apple Inc. + dmi.chassis.asset.tag: Asset Tag# + dmi.chassis.type: 10 + dmi.chassis.vendor: Apple Inc. + dmi.chassis.version: Mac-F22587C8 + dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,3:pvr1.0:rvnAppleInc.:rnMac-F22587C8:rvr:cvnAppleInc.:ct10:cvrMac-F22587C8: + dmi.product.name: MacBookPro5,3 + dmi.product.version: 1.0 + dmi.sys.vendor: Apple Inc. ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706238/+files/AcpiTables.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage
[Bug 925024] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706239/+files/AlsaDevices.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706240/+files/AplayDevices.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706241/+files/Card0.Amixer.values.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706242/+files/Card0.Codecs.codec.0.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706243/+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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706244/+files/IwConfig.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706245/+files/Lspci.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706248/+files/ProcCpuinfo.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706247/+files/PciMultimedia.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] PulseSinks.txt
apport information ** Attachment added: PulseSinks.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706251/+files/PulseSinks.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] PulseSources.txt
apport information ** Attachment added: PulseSources.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706252/+files/PulseSources.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706254/+files/UdevDb.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706255/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925028] Re: apparmor breaks lxc-start-ephemeral
apport information ** Tags added: apport-collected precise running-unity ** Description changed: Repro: $ sudo lxc-create -t ubuntu -n precise -f /etc/lxc/local.conf -- -r precise -a i686 -b gary $ sudo lxc-start-ephemeral -o precise Setting up ephemeral container... Starting up the container... lxc-start: Invalid argument - failed to open /var/lib/lxc/precise-temp-P3RLwXk/config lxc-start: failed to read configuration file Workaround (thanks to wgrant): $ sudo ln -s /etc/apparmor.d/usr.bin.lxc-start /etc/apparmor.disable/usr. usr.bin.firefoxusr.sbin.rsyslogd $ sudo ln -s /etc/apparmor.d/usr.bin.lxc-start /etc/apparmor.d/d isable/ $ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.lxc-start $ sudo lxc-start-ephemeral -o precise Setting up ephemeral container... Starting up the container... precise-temp-JgTN0gj is running You connect with the command: sudo lxc-console -n precise-temp-JgTN0gj + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. + ApportVersion: 1.91-0ubuntu1 + Architecture: amd64 + ArecordDevices: + List of CAPTURE Hardware Devices + card 0: NVidia [HDA NVidia], device 0: Cirrus Analog [Cirrus Analog] +Subdevices: 1/1 +Subdevice #0: subdevice #0 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gary 1953 F pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + Card0.Amixer.info: + Card hw:0 'NVidia'/'HDA NVidia at 0xe748 irq 21' +Mixer name : 'Cirrus Logic CS4206' +Components : 'HDA:10134206,106b4b00,00100301' +Controls : 18 +Simple ctrls : 9 + CurrentDmesg: + Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied + dmesg: write failed: Broken pipe + DistroRelease: Ubuntu 12.04 + MachineType: Apple Inc. MacBookPro5,3 + NonfreeKernelModules: wl nvidia + Package: lxc 0.7.5-3ubuntu16 + PackageArchitecture: amd64 + ProcEnviron: + PATH=(custom, user) + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic root=UUID=44d3af31-0b7b-42d9-a0ff-d3cfb63f282d ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 + Tags: precise running-unity precise running-unity + Uname: Linux 3.2.0-12-generic x86_64 + UpgradeStatus: Upgraded to precise on 2012-01-23 (9 days ago) + UserGroups: libvirtd sudo + WifiSyslog: + + dmi.bios.date: 06/15/09 + dmi.bios.vendor: Apple Inc. + dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 + dmi.board.asset.tag: Base Board Asset Tag# + dmi.board.name: Mac-F22587C8 + dmi.board.vendor: Apple Inc. + dmi.chassis.asset.tag: Asset Tag# + dmi.chassis.type: 10 + dmi.chassis.vendor: Apple Inc. + dmi.chassis.version: Mac-F22587C8 + dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,3:pvr1.0:rvnAppleInc.:rnMac-F22587C8:rvr:cvnAppleInc.:ct10:cvrMac-F22587C8: + dmi.product.name: MacBookPro5,3 + dmi.product.version: 1.0 + dmi.sys.vendor: Apple Inc. ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/925028/+attachment/2706218/+files/AcpiTables.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/925028 Title: apparmor breaks lxc-start-ephemeral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925028/+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 925024] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706246/+files/Lsusb.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 925024] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/925024/+attachment/2706253/+files/RfKill.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/925024 Title: apparmor makes it impossible to install postgresql-common on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925024/+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 924337] [NEW] lxc on precise is not working with lucid containers
Public bug reported: On precise with newest packages as of 2012-01-31 1500Z, trying to start an lxc lucid container hangs. Oneric and Precise containers work fine. $ sudo lxc-start -n lp init: ureadahead-other main process (31) terminated with status 4 init: console-setup main process (32) terminated with status 1 init: procps main process (33) terminated with status 255 init: ureadahead-other main process (37) terminated with status 4 [HANGS HERE, for at least two minutes] How I created the container: $ sudo lxc-create -t ubuntu -n lp -f /etc/lxc/local.conf -- -r lucid -a i686 -b gary local.conf: $ cat /etc/lxc/local.conf lxc.network.type=veth lxc.network.link=lxcbr0 lxc.network.flags=up /var/lib/lxc/lp/rootfs/etc/resolv.conf was a symlink to /etc/resolvconf/run/resolv.conf. On the basis of previous conversations, I tried changing it to nameserver 10.0.3.1 to no luck ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/924337 Title: lxc on precise is not working with lucid containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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 924337] Re: lxc on precise is not working with lucid containers
I reported on IRC to Serge that virbr0 did indeed have STP enabled, but that I did not see any obvious dnsmasq errors. He already had diagnosed the problem said as a workaround I could just change the 'start on' in /etc/init/console.conf in my container to 'start on mounted MOUNTPOINT=/run'. stgraber's new upstart will fix it properly when it hits the archive. -- 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/924337 Title: lxc on precise is not working with lucid containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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 914169] Re: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers
** No longer affects: launchpad -- 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/914169 Title: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/914169/+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 914169] Re: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers
@serge Thank you! @Robert IIUC we do both dhcp and dhcp3. My diff merely added a sudo. -- 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/914169 Title: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/914169/+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 914169] Re: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers
With the fix from bug 914169, the only basic change we need in this script is as follows: 121,122c121,122 mkdir -p $LXC_DIR/rootfs/var/lib/dhcp3 mkdir -p $LXC_DIR/rootfs/var/lib/dhcp --- sudo mkdir -p $LXC_DIR/rootfs/var/lib/dhcp3 sudo mkdir -p $LXC_DIR/rootfs/var/lib/dhcp We're also interested in making the ssh call more robust by retrying a few times if it fails. Sometimes the sshd has not yet started in the container, so this can give spurious errors. We gave an initial stab at this but do not have a solution yet. -- 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/914169 Title: lxc-start-ephemeral script does not support in-line programmatic commands to ephemeral containers To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/914169/+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
