[Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
Yep, fixed. With wily-proposed enabled, # apt-get install lxc installs: 2015-11-15 11:29:28 status installed liblxc1:amd64 1.1.5-0ubuntu0.15.10.2 2015-11-15 11:29:29 status installed python3-lxc:amd64 1.1.5-0ubuntu0.15.10.2 2015-11-15 11:29:30 status installed lxc:amd64 1.1.5-0ubuntu0.15.10.2 ... and, immediately, lxc works as I expected. I can confirm reboot is still broken, as per bug 1514690 , but this doesn't matter for my usecase, so woo, 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/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1497420/+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 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
I haven't seen this issue for ages, using primarily sid and wily guests. Trying again on my desktop, which definitely used to have the issue, I can't reproduce it, using: 2015-11-15 11:29:28 status installed liblxc1:amd64 1.1.5-0ubuntu0.15.10.2 2015-11-15 11:29:29 status installed python3-lxc:amd64 1.1.5-0ubuntu0.15.10.2 2015-11-15 11:29:30 status installed lxc:amd64 1.1.5-0ubuntu0.15.10.2 .. from wily-proposed. -- 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/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+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 1502977] [NEW] Fails to complete installation: won't start due to config block
Public bug reported: The package attempts to start itself as part of the post-install. However, the default config, shipped with the application, prevents it from starting. This makes apt Angry: Setting up openhpid (2.14.1-1.3ubuntu2) ... Job for openhpid.service failed. See "systemctl status openhpid.service" and "journalctl -xe" for details. invoke-rc.d: initscript openhpid, action "start" failed. dpkg: error processing package openhpid (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of openhpi: openhpi depends on openhpid; however: Package openhpid is not configured yet. dpkg: error processing package openhpi (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.21-0ubuntu4) ... No apport report written because the error message indicates it's a follow-up error from a previous failure. Processing triggers for systemd (219-7ubuntu6) ... Processing triggers for ureadahead (0.100.0-19) ... Errors were encountered while processing: openhpid openhpi E: Sub-process /usr/bin/dpkg returned an error code (1) The error is: ERROR: (init.c, 76, OpenHPI is not configured. See openhpi.conf file.) Caused by: % head -n 10 /etc/openhpi/openhpi.conf ### OpenHPI configuration example file ### ### ## OpenHPI will not be useful unless it is configured for your system. Once ## you have modified this file, remove or comment the following line to allow ## the OpenHPI daemon to run. This line causes the daemon to exit immediately. OPENHPI_UNCONFIGURED = "YES" ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: openhpi 2.14.1-1.3ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Mon Oct 5 17:26:12 2015 InstallationDate: Installed on 2014-08-01 (430 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: openhpi UpgradeStatus: Upgraded to vivid on 2014-09-11 (389 days ago) ** Affects: openhpi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openhpi in Ubuntu. https://bugs.launchpad.net/bugs/1502977 Title: Fails to complete installation: won't start due to config block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openhpi/+bug/1502977/+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 1497420] [NEW] systemd 226-2 (debian sid) breaks lxc-attach
Public bug reported: Once systemd 226 is installed in an unprivileged Debian Sid container, lxc-attach no-longer functions: % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process % journalctl -u cgmanager | tail -n 1 Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: pid 21918 (uid 1000 gid 1000) may not write to /run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks Full walkthrough: % lxc-create -n siddy -t download -- -d debian -r sid -a amd64 Using image from local cache Unpacking the rootfs ... % lxc-start -n siddy % lxc-attach -n siddy root@siddy:/# apt-get update Get:1 http://http.debian.net sid InRelease [253 kB] ... Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB] Fetched 13.2 MB in 3s (3789 kB/s) Reading package lists... Done root@siddy:/# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libsystemd0 Suggested packages: systemd-ui systemd-container Recommended packages: libpam-systemd dbus The following packages will be upgraded: libsystemd0 systemd 2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded. Need to get 3668 kB of archives. After this operation, 1100 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB] Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB] ... Setting up systemd (226-2) ... Installing new version of config file /etc/X11/xinit/xinitrc.d/50-systemd-user.sh ... Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.login1.conf ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Failed to execute operation: File exists Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf ... root@siddy:/# exit % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/lxc/lxc-net] ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Fri Sep 18 20:19:58 2015 SourcePackage: lxc UpgradeStatus: Upgraded to wily on 2015-08-28 (20 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug wily -- 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/1497420 Title: systemd 226-2 (debian sid) breaks lxc-attach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1497420/+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 1477453] [NEW] lxc-stop -n unknown-container creates a corrupted container
Public bug reported: Running lxc-stop on a container which doesn't exist actually creates the container, and messes up its permissions, causing sequences like: $ lxc-stop -n foo lxc-destroy -n foo lxc-clone clean-machine foo ..to fail with bad errors: # it definitely doesn't exist to start with: % lxc-ls foo % lxc-info -n foo foo doesn't exist % ls ~/.local/share/lxc/foo -al ls: cannot access /home/faux/.local/share/lxc/foo: No such file or directory # now let's stop it: % lxc-stop -n foo foo is not running # tooling still thinks it doesn't exist: % lxc-ls foo % lxc-info -n foo foo doesn't exist # .. but there are some files! % ls ~/.local/share/lxc/foo -al total 0 drwxr-xr-x 1 faux faux 14 Jul 23 09:45 . drwxr-xr-x 1 faux faux 8070 Jul 23 09:45 .. -rw-rw-r-- 1 faux faux0 Jul 23 09:45 foo.log # and now lxc-clone is totally broken: % lxc-clone base foo lxc_container: lxccontainer.c: lxcapi_clone: 2707 Permission denied - open /home/faux/.local/share/lxc/foo/config clone failed Can we worked around by manually rm -rfing ~/.local/share/lxc/foo. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Thu Jul 23 09:45:56 2015 SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid -- 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/1477453 Title: lxc-stop -n unknown-container creates a corrupted container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1477453/+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 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
No, that proposed work around seems to make no difference. -- 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/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+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 1452601] [NEW] vivid container's networking.service fails on boot with signal=PIPE
Public bug reported: When starting a Vivid container, it fails to get an IP address. It believes networking.service was successful, but actually it dies with SIGPIPE. Restarting networking.service gets an IP, as expected. Starting networking used to work with pre-vivid containers. I'm reasonably sure this fails 100% of the time. Limited user container, very standard setup (no unnecessary config; cgmanager and lxcfs installed), btrfs filesystem but not btrfs-backed (as it's limited user), ... root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago Docs: man:systemd-sysv-generator(8) Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE) root@vivid:/# systemctl restart networking.service root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago Docs: man:systemd-sysv-generator(8) Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS) Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) CGroup: /user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate ├─1109 lockfile-touch /var/lock/ntpdate-ifup ├─1125 /bin/sh /etc/network/if-up.d/ntpdate ├─1128 lockfile-create /var/lock/ntpdate-ifup └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com root@vivid:/# ip a ... 22: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ... inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 08:53:02 2015 SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid ** Attachment added: full boot log from lxc-start -F https://bugs.launchpad.net/bugs/1452601/+attachment/4392774/+files/vivid-boot.log -- 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/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+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 1441068] Re: lxc-destroy fails on btrfs subvolumes
This also occurs for limited user containers, without asking for a btrfs backing store. This is more of a problem as the limited user can't delete (or even detect) the subvolume themselves. On a standard whole-partition-as-btrfs system, as setup by the installer, this looks like: ID 257 gen 46021 top level 5 path @ ID 258 gen 46021 top level 5 path @home ... ID 373 gen 35464 top level 257 path @/var/lib/machines ID 374 gen 45983 top level 258 path faux/.local/share/lxc/vivid/rootfs/var/lib/machines ID 395 gen 45995 top level 258 path faux/.local/share/lxc/vivid2/rootfs/var/lib/machines ID 396 gen 46011 top level 258 path faux/.local/share/lxc/vivid3/rootfs/var/lib/machines ID 397 gen 46014 top level 258 path faux/.local/share/lxc/vivid4/rootfs/var/lib/machines -- 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/1441068 Title: lxc-destroy fails on btrfs subvolumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1441068/+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 1410746] [NEW] Interrupted lxc-snapshot deletes snapshot *and* vm
Public bug reported: lxc is configured for limited user usage, i.e. the backing store is always dir. Let's create a container, and snapshot it in its pristine state: % lxc-create -n restorebug -t download -- -d ubuntu -r utopic -a amd64 lxc-snapshot -n restorebug [...] lxc_container: lxccontainer.c: lxcapi_snapshot: 3011 Snapshot of directory-backed container requested. lxc_container: lxccontainer.c: lxcapi_snapshot: 3012 Making a copy-clone. [...] % ls ~/.local/share/lxc/restorebug/rootfs ~/.local/share/lxc/restorebug/snaps/snap0/rootfs .local/share/lxc/restorebug/rootfs: bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var .local/share/lxc/restorebug/snaps/snap0/rootfs: bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var Everything went to plan. Now, try restoring the snapshot, and ctrl+c'ing lxc-snapshot while it's running: % lxc-snapshot -n restorebug -r snap0 [ctrl+c, bang!] Depending on when you press it, you might get some rsync output, but never anything from the lxc-snapshot command itself. This isn't unexpected, it's probably just copying the snapshot over to the vm, right?! That sounds cancellable. e.g. rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632) [sender=3.1.1] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.1] Now, let's run lxc-snapshot again, no need to ctrl+c it: % lxc-snapshot -n restorebug -r snap0 lxc_container: bdev.c: bdev_copy: 3253 failed to detect blockdev type for ...local/share/lxc/restorebug/snaps/snap0/rootfs lxc_container: lxccontainer.c: copy_storage: 2543 Error copying storage lxc_container: lxccontainer.c: lxcapi_destroy: 2141 Container restorebug has snapshots; not removing lxc_container: lxc_snapshot.c: do_restore_snapshots: 109 Error restoring snapshot snap0 % ls -a ~/.local/share/lxc/restorebug/rootfs ~/.local/share/lxc/restorebug/snaps/snap0 .local/share/lxc/restorebug/rootfs: . .. .local/share/lxc/restorebug/snaps/snap0: . .. config ts It's deleted both the snapshot, and the original container. Further attempts to run lxc-snapshot give similar errors: % lxc-snapshot -n restorebug -r snap0 lxc_container: lxccontainer.c: lxcapi_snapshot_restore: 3217 Failed to find original backing store type lxc_container: lxc_snapshot.c: do_restore_snapshots: 109 Error restoring snapshot snap0 Also reproduced on cleaner utopic server installs, this bug report is from my laptop. (We hit this on our build server: a typical job is to restore a vm, then run some commands in it. Jobs are cancellable, which just interrupts any running process.) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha2-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Jan 14 10:11:15 2015 InstallationDate: Installed on 2014-08-01 (165 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: lxc UpgradeStatus: Upgraded to utopic on 2014-09-11 (125 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug utopic -- 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/1410746 Title: Interrupted lxc-snapshot deletes snapshot *and* vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1410746/+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 1391452] Re: lxc-net fails to start properly after system crash: lock file
Good spot, thanks: /var/lock is on /, not a symlink to /var/run. These machines are provisioned from OVH.com templates. I have raised a support request with them to see if they are aware of this or are doing anything strange on purpose. -- $ cat /proc/self/mountinfo | fgrep lock 27 20 0:19 / /run/lock rw,nosuid,nodev,noexec,relatime - tmpfs none rw,size=5120k $ df -h /var/lock Filesystem Size Used Avail Use% Mounted on /dev/disk/by-uuid/56f53efc-[..] 20G 3.2G 15G 18% / $ ls -ld /var/lock drwxrwxrwt 2 root root 4096 Nov 12 10:42 /var/lock $ df -h /run/lock Filesystem Size Used Avail Use% Mounted on none5.0M 0 5.0M 0% /run/lock -- 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/1391452 Title: lxc-net fails to start properly after system crash: lock file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1391452/+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 1391452] [NEW] lxc-net fails to start properly after system crash: lock file
Public bug reported: The presence of /var/lock/lxc-net causes service lxc-net start to claim success but actually just do nothing useful. When the system goes down hard, /var/lock/lxc-net is not removed, fair enough. This means that systems require manual intervention after booting. You can reproduce the problem by crashing some processes and fiddling with lock-files, but this happens at every single hard reboot: faux@alohura:~% sudo service lxc-net stop lxc-net stop/waiting ## the presence of other dnsmasqs makes this all confusing to me, so let's just kill them anyway, even if they were started by NetworkManager faux@alohura:~% sudo killall dnsmasq faux@alohura:~% sudo killall dnsmasq dnsmasq: no process found ## simulate the lock-file being left over from a hard reboot faux@alohura:~% sudo touch /var/lock/lxc-net faux@alohura:~% sudo service lxc-net start lxc-net start/running ## we haven't bothered to start dnsmasq (or create the bridge interface or..) faux@alohura:~% ps aux | fgrep dnsmasq faux 10592 0.0 0.0 13680 2064 pts/4S+ 09:58 0:00 grep -F dnsmasq ## so containers won't start faux@alohura:~% lxc-start -n new lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 339 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. faux@alohura:~% lxc-start -F -n new Error attaching veth494WIK to lxcbr0 Quota reached lxc-start: start.c: lxc_spawn: 930 failed to create the configured network lxc-start: start.c: __lxc_start: 1087 failed to spawn 'new' lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. faux@alohura:~% The error message from lxc-start is very poor, too. This can be worked around by blowing away the lockfile, then restarting lxc-net. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha2-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Tue Nov 11 09:54:59 2014 InstallationDate: Installed on 2014-04-16 (209 days ago) InstallationMedia: KernLog: ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- 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/1391452 Title: lxc-net fails to start properly after system crash: lock file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1391452/+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 933480] [NEW] Picks hmac-md5 over hmac-sha1
Public bug reported: The OpenSSH client defaults to picking hmac-md5, which is based on the demonstrably insecure MD5 algorithm: faux@wilf:~% ssh -v localhost true 21 | grep hmac debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none MD5 has had practical vulnerabilities for around eight years, and its use is highly discouraged. SHA1 is a supported alternative, and is supported by the packaged openssh-server, and many other ssh implementations. MD5 is selected as man ssh_config suggests the default algorithms are, in order of preference (most preferred first): hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 Please append: MACs hmac-sha1,hmac-md5,umac...@openssh.com,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 ...to /etc/ssh/ssh_config, such that the client will prefer SHA-1: faux@wilf:~% ssh -v localhost true 21 | grep hmac debug1: kex: server-client aes128-ctr hmac-sha1 none debug1: kex: client-server aes128-ctr hmac-sha1 none This should have no compatibility concerns as MD5 is still a supported algorithm. Note that non-privileged users can override this setting either way on a per-connection basis by specifying MACs in ~/.ssh/config. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: openssh-client 1:5.8p1-7ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CheckboxSubmission: b0d31efda01870980e2e5a89390b685c CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d Date: Thu Feb 16 13:59:43 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:5.8p1-7ubuntu1 SSHClientVersion: OpenSSH_5.8p1 Debian-7ubuntu1, OpenSSL 1.0.0e 6 Sep 2011 SourcePackage: openssh UpgradeStatus: Upgraded to oneiric on 2011-05-03 (289 days ago) modified.conffile..etc.ssh.ssh.config: [modified] mtime.conffile..etc.ssh.ssh.config: 2012-02-16T13:59:11.376423 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- 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/933480 Title: Picks hmac-md5 over hmac-sha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/933480/+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 933480] Re: Picks hmac-md5 over hmac-sha1
-- 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/933480 Title: Picks hmac-md5 over hmac-sha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/933480/+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 933480] Re: Picks hmac-md5 over hmac-sha1
For precise, openssh-5.9 supports even more secure algorithms, so the line should perhaps be: MACs hmac-sha2-512,hmac-sha2-256,hmac-sha1,hmac-ripemd160,umac...@openssh.com,hmac-md5,hmac-sha1-96,hmac-sha2-512-96,hmac-sha2-256-96,hmac-md5-96 -- 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/933480 Title: Picks hmac-md5 over hmac-sha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/933480/+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
