[Bug 1551150] Re: devel-proposed - android lxc container fails to start
/proc/cgroups #subsys_namehierarchy num_cgroups enabled debug 0 1 1 cpu 0 1 1 cpuacct 0 1 1 freezer 0 1 1 /proc/self/cgroup is empty There is no /var/log/upstart/cgroup-lite.log file and I verified that the upstart job cgroup-lite starts. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
And the content of fstab /system/etc # cat fstab # override the forced fsck from /lib/init/fstab, we use a bindmount which confuses mountall /dev/root / rootfs defaults0 0 # swap file /SWAP.swap noneswapsw 0 0 -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
** Changed in: canonical-devices-system-image Assignee: (unassigned) => Ondrej Kubik (w-ondra) -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
android container log with cgroup-lite installed and content of mountinfo from the same boot. ** Attachment added: "mountinfo.out" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584668/+files/mountinfo.out -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
And syslog ** Attachment added: "syslog" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584669/+files/syslog -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
The phone uses upstart. I'll try to get the content of mountinfo -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
With cgroup-lite install the error message is different: lxc-start 20160229153538.890 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 - cgroupfs failed to detect cgroup metadata lxc-start 20160229153538.890 ERRORlxc_start - start.c:lxc_spawn:1026 - failed initializing cgroup support lxc-start 20160229153538.891 ERRORlxc_start - start.c:__lxc_start:1276 - failed to spawn 'android' lxc-start 20160229153538.891 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 20160229153538.891 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. lxc-start 20160229160049.670 ERRORlxc_cgfs - cgfs.c:lxc_cgroupfs_create:874 - Could not find writable mount point for cgroup hierarchy 7 while trying to create cgroup. lxc-start 20160229160049.671 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/ lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuacct/ lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu/ lxc-start 20160229160049.672 ERRORlxc_cgfs - cgfs.c:cgroup_rmdir:208 - Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/debug/ lxc-start 20160229160049.672 ERRORlxc_start - start.c:lxc_spawn:1033 - failed creating cgroups lxc-start 20160229160049.673 ERRORlxc_start - start.c:__lxc_start:1276 - failed to spawn 'android' lxc-start 20160229160049.673 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 20160229160049.673 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
I installed cgroup-lite 1.10 but it still doesn't boot. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed - android lxc container fails to start
cgroup-lite is not installed: un cgroup-lite ii systemd:armhf 229-1ubuntu4 I cannot paste the content of /proc/mounts because I only have adb in recovery (the devices fails before adb starts otherwise) -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
dmesg from a system that doesn't boot. ** Attachment added: "dmesg.out" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551150/+attachment/4584338/+files/dmesg.out ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. + + Device tarballs between 446 and 447 are the same. -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
~ # cat /data/system-data/var/log/lxc/android.log lxc-start 20160229125348.090 ERRORlxc_cgfs - cgfs.c:cgfs_init:2300 - cgroupfs failed to detect cgroup metadata lxc-start 20160229125348.091 ERRORlxc_start - start.c:lxc_spawn:1026 - failed initializing cgroup support lxc-start 20160229125348.091 ERRORlxc_start - start.c:__lxc_start:1276 - failed to spawn 'android' lxc-start 20160229125348.091 ERRORlxc_start_ui - lxc_start.c:main:344 - The container failed to start. lxc-start 20160229125348.092 ERRORlxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. ** Summary changed: - devel-proposed doesn't boot + devel-proposed - android lxc container fails to start ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 -- 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/1551150 Title: devel-proposed - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 - ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on - other devices do not boot and hang on the boot logo. + ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent + images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium - * New upstream release (2.0.0~rc3) - - Make the cgfs backend and cgns work without cgmanager - - Manpage updates - - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) - * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral + * New upstream release (2.0.0~rc3) + - Make the cgfs backend and cgns work without cgmanager + - Manpage updates + - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) + * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium - * Use versioned dependencies against the various binary packages. - * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) - * Move the lxcfs recommends from lxc-templates to liblxc1. - * Drop cgmanager, use the cgfs backend instead. - * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. + * Use versioned dependencies against the various binary packages. + * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) + * Move the lxcfs recommends from lxc-templates to liblxc1. + * Drop cgmanager, use the cgfs backend instead. + * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 + + Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. -- 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/1551150 Title: devel-proposed doesn't boot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1551150] Re: devel-proposed doesn't boot
changes list between 446 and 447. ** Attachment added: "446-447.changes" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+attachment/4584311/+files/446-447.changes ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: - ubuntu-touch/devel-proposed/krillin.en/mako/ 338 and equivalent images - on other devices do not boot and hang on the boot logo. + Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 + + ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on + other devices do not boot and hang on the boot logo. ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on other devices do not boot and hang on the boot logo. + + From the list of changes, it could be lxc: + 446: lxc 2.0.0~rc2-0ubuntu2 + 447: lxc 2.0.0~rc3-0ubuntu1 ** Description changed: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 + + lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium + + * New upstream release (2.0.0~rc3) + - Make the cgfs backend and cgns work without cgmanager + - Manpage updates + - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) + * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral + + lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium + + * Use versioned dependencies against the various binary packages. + * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) + * Move the lxcfs recommends from lxc-templates to liblxc1. + * Drop cgmanager, use the cgfs backend instead. + * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. -- 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/1551150 Title: devel-proposed doesn't boot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+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 1526264] Re: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16)
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Committed ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1526264 Title: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264/+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 1528136] [NEW] [1.2.16] Failed to initialize KVM & other internal errors
Public bug reported: On Ubuntu Server 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux sudo systemctl status libvirt-bin ● libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2015-12-21 09:47:02 CET; 3s ago Docs: man:libvirtd(8) http://libvirt.org Main PID: 20980 (libvirtd) CGroup: /system.slice/libvirt-bin.service └─20980 /usr/sbin/libvirtd Dec 21 09:47:02 msi-ge60-ubuntu libvirtd[20980]: libvirt version: 1.2.16, package: 1.2.16-2ubuntu11.15.10.1 Dec 21 09:47:02 msi-ge60-ubuntu libvirtd[20980]: internal error: Unknown qemu capabilities flag vhost-user-multiqueue Dec 21 09:47:02 msi-ge60-ubuntu libvirtd[20980]: Failed to load cached caps from '/var/cache/libvirt/qemu/capabilities/2d1567fa77de202a8d45125ec58eadc9538916e0d21b9ecbc092...-multiqueue Dec 21 09:47:03 msi-ge60-ubuntu libvirtd[20980]: internal error: QEMU / QMP failed: Could not access KVM kernel module: Permission denied failed to initialize KVM: Permission denied Dec 21 09:47:03 msi-ge60-ubuntu libvirtd[20980]: Failed to probe capabilities for /usr/bin/kvm: internal error: QEMU / QMP failed: Could not access KVM kernel module: Permission denied failed to initialize KVM: Permission denied Dec 21 09:47:03 msi-ge60-ubuntu libvirtd[20980]: internal error: Unknown qemu capabilities flag vhost-user-multiqueue Dec 21 09:47:03 msi-ge60-ubuntu libvirtd[20980]: Failed to load cached caps from '/var/cache/libvirt/qemu/capabilities/2d1567fa77de202a8d45125ec58eadc9538916e0d21b9ecbc092...-multiqueue Dec 21 09:47:03 msi-ge60-ubuntu libvirtd[20980]: internal error: QEMU / QMP failed: Could not access KVM kernel module: Permission denied failed to initialize KVM: Permission denied Dec 21 09:47:03 msi-ge60-ubuntu libvirtd[20980]: Failed to probe capabilities for /usr/bin/kvm: internal error: QEMU / QMP failed: Could not access KVM kernel module: Permission denied failed to initialize KVM: Permission denied Dec 21 09:47:03 msi-ge60-ubuntu libvirtd[20980]: error creating bridge interface virbr0: File exists Hint: Some lines were ellipsized, use -l to show in full. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1528136 Title: [1.2.16] Failed to initialize KVM & other internal errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1528136/+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 1486865] Re: [FFE] Sync rrdtool 1.5.4-5 (main) from Debian unstable (main)
** Changed in: rrdtool (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rrdtool in Ubuntu. https://bugs.launchpad.net/bugs/1486865 Title: [FFE] Sync rrdtool 1.5.4-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rrdtool/+bug/1486865/+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 1526264] [NEW] ntpdate fails with invalid argument when device is set to a date in the future
Public bug reported: current build number: 204 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en when the current date of the device is in the future, ntpdate fails with 'Invalid Argument' For example: * current date: passed root@ubuntu-phablet:~# date mardi 15 décembre 2015, 12:01:22 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:01:38 ntpdate[4360]: adjust time server 91.189.94.4 offset 0.000150 sec * Date in the past: passed root@ubuntu-phablet:~# date -s '2015-12-14 13:00:00' lundi 14 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:03:02 ntpdate[5008]: step time server 91.189.89.199 offset 82943.900852 sec * Date in the future: Failed root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 16 Dec 13:00:10 ntpdate[4820]: Can't adjust the time of day: Invalid argument = Workaround = Use option -b root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate -b ntp.ubuntu.com 15 Dec 12:07:08 ntpdate[7083]: step time server 91.189.94.4 offset -89602.883248 sec ** Affects: canonical-devices-system-image Importance: High Status: New ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Also affects: ntp (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Description changed: current build number: 204 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en when the current date of the device is in the future, ntpdate fails with 'Invalid Argument' For example: * current date: passed root@ubuntu-phablet:~# date mardi 15 décembre 2015, 12:01:22 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:01:38 ntpdate[4360]: adjust time server 91.189.94.4 offset 0.000150 sec * Date in the past: passed root@ubuntu-phablet:~# date -s '2015-12-14 13:00:00' lundi 14 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:03:02 ntpdate[5008]: step time server 91.189.89.199 offset 82943.900852 sec * Date in the future: Failed root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 16 Dec 13:00:10 ntpdate[4820]: Can't adjust the time of day: Invalid argument + + = Workaround = + Use option -b + + root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' + mercredi 16 décembre 2015, 13:00:00 (UTC+0100) + root@ubuntu-phablet:~# ntpdate -b ntp.ubuntu.com + 15 Dec 12:07:08 ntpdate[7083]: step time server 91.189.94.4 offset -89602.883248 sec -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1526264 Title: ntpdate fails with invalid argument when device is set to a date in the future To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264/+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 1526264] Re: ntpdate fails with invalid argument when device is set to a date in the future
** Description changed: current build number: 204 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en when the current date of the device is in the future, ntpdate fails with 'Invalid Argument' For example: * current date: passed root@ubuntu-phablet:~# date mardi 15 décembre 2015, 12:01:22 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:01:38 ntpdate[4360]: adjust time server 91.189.94.4 offset 0.000150 sec * Date in the past: passed root@ubuntu-phablet:~# date -s '2015-12-14 13:00:00' lundi 14 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 15 Dec 12:03:02 ntpdate[5008]: step time server 91.189.89.199 offset 82943.900852 sec * Date in the future: Failed root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate ntp.ubuntu.com 16 Dec 13:00:10 ntpdate[4820]: Can't adjust the time of day: Invalid argument + After some experimentation, ntpdate fails if the difference between the + current time on the device and the real time is bigger than 2^16 (65536) + = Workaround = - Use option -b + Use option -b root@ubuntu-phablet:~# date -s '2015-12-16 13:00:00' mercredi 16 décembre 2015, 13:00:00 (UTC+0100) root@ubuntu-phablet:~# ntpdate -b ntp.ubuntu.com 15 Dec 12:07:08 ntpdate[7083]: step time server 91.189.94.4 offset -89602.883248 sec ** Summary changed: - ntpdate fails with invalid argument when device is set to a date in the future + ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16) ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1526264 Title: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264/+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 1522371] Re: iproute2: seg fault with 'ip link type gre ...' commands
** Tags added: 6wind -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1522371 Title: iproute2: seg fault with 'ip link type gre ...' commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1522371/+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 1511735] Re: libnl: fail to bind() netlink sockets
** Tags added: 6wind -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+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 1522190] Re: Permission denied (publickey) whereas the public key has been inserted into ~/.ssh/authorized_keys
We have a winner: setting usePAM to no generates the issue: /etc/ssh/sshd_config --- ... usePAM no ChallengeResponseAuthentication no PasswordAuthentication no PermitEmptyPasswords no ... ssh -v root@localhost - ... debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /root/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Trying private key: /root/.ssh/id_dsa debug1: Trying private key: /root/.ssh/id_ecdsa debug1: Offering ED25519 public key: /root/.ssh/id_ed25519 debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey). However, setting usePAM to yes makes the session work: /etc/ssh/sshd_config --- ... use PAM yes ChallengeResponseAuthentication no PasswordAuthentication no PermitEmptyPasswords no ... ssh -v root@localhost ... debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /root/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 279 Enter passphrase for key '/root/.ssh/id_rsa': debug1: Authentication succeeded (publickey). Authenticated to localhost ([::1]:xxx). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 Welcome to Ubuntu 15.10 (GNU/Linux 4.2.0-19-generic x86_64) ... ** Information type changed from Private Security to Public Security ** Summary changed: - Permission denied (publickey) whereas the public key has been inserted into ~/.ssh/authorized_keys + Permission denied (publickey) whereas the public key has been inserted into ~/.ssh/authorized_keys: usePAM no issue ** Summary changed: - Permission denied (publickey) whereas the public key has been inserted into ~/.ssh/authorized_keys: usePAM no issue + Permission denied (publickey) whereas the public key has been inserted into ~/.ssh/authorized_keys: "usePAM no" issue -- 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/1522190 Title: Permission denied (publickey) whereas the public key has been inserted into ~/.ssh/authorized_keys: "usePAM no" issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1522190/+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 1497263] Re: Unable to negotiate a key exchange method
I really appreciate you're taking some time to answer this. However, there's some confusion here: you're answering in this thread to another issue which is located in another thread (https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1522190). My configuration is not the same. could you try to reproduce the new issue with my new settings and answer in the new thread? In the meantime, I'll post more information about sshd_config & ssh_config in the new thread. You were right: I'm not using a default configuration, but openssh should also work in other situations that the default one, right? -- 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/1497263 Title: Unable to negotiate a key exchange method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1497263/+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 1497263] Re: Unable to negotiate a key exchange method
** Changed in: openssh (Ubuntu) Status: Incomplete => Fix Released -- 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/1497263 Title: Unable to negotiate a key exchange method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1497263/+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 1497263] Re: Unable to negotiate a key exchange method
That issue has been solved with newer versions openssh-server/client 6.9p1-2. However, another issue has surfaced: cf. https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1522190 -- 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/1497263 Title: Unable to negotiate a key exchange method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1497263/+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 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels
** Changed in: canonical-devices-system-image Status: Confirmed => Fix Released -- 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/1516971 Title: LXC's preserve_ns fails on < 3.8 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+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 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
It is also affecting devel-proposed phone images cf bug 1516971 -- 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1516037/+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 1516037] Re: lxc-start fails with 1.1.5-0ubuntu1
I confirm that the phone boots successfully after downgrading liblxc1, lxc and python3-lxc to version 1.1.4-0ubuntu3 ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Status: New => 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/1516037 Title: lxc-start fails with 1.1.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+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 1516971] Re: devel-proposed mako 350 - android lxc container fails to start
** This bug is no longer a duplicate of bug 1516037 lxc-start fails with 1.1.5-0ubuntu1 ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1516971 Title: devel-proposed mako 350 - android lxc container fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+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 1508744] Re: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade
** Also affects: ubuntu-release-notes 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/1508744 Title: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508744/+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 1486865] Re: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main)
Hi "The Wily Werewolf (pre-release freeze)" now has version 1.5.4-5. Am I correct in assuming this bug can be closed, now? https://bugs.launchpad.net/ubuntu/+source/rrdtool -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rrdtool in Ubuntu. https://bugs.launchpad.net/bugs/1486865 Title: [FFE] Sync rrdtool 1.5.4-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rrdtool/+bug/1486865/+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 1500428] Re: package mysql-server-5.6 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1
Actually I found the way to fix it : + I had to remove whatever (sorry i don't remember) lock file in /var/... + force apt-get install + Launch mysql in safe mode + remove the plugins defined in the user table + restart mysql The last steps are here : https://zhxq.io/how-to-solve-mariadb-plugin-unix_socket-is-not-loaded-problem-after-upgrade-to-ubuntu-15-04/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1500428 Title: package mysql-server-5.6 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500428/+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 1500428] [NEW] package mysql-server-5.6 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1
Public bug reported: The installation mysql server as dependency of build-deps of php-dev removed mariadb and didn't work. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: mysql-server-5.6 (not installed) ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Mon Sep 28 12:38:04 2015 DuplicateSignature: package:mysql-server-5.6:(not installed):le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2015-07-20 (69 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: mysql-5.6 Title: package mysql-server-5.6 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2015-07-11T20:43:37 mtime.conffile..etc.init.d.mysql: 2015-08-27T14:45:46.163455 mtime.conffile..etc.logrotate.d.mysql.server: 2015-07-11T20:43:48 mtime.conffile..etc.mysql.debian.start: 2015-02-17T19:24:15 ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1500428 Title: package mysql-server-5.6 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500428/+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 1497263] [NEW] Unable to negotiate a key exchange method
Public bug reported: Client: Ubuntu Server 15.04 with openssh-client 6.7p1 Server: Ubuntu cloud server 15.04 with openssh-server 6.7p1 Connection trace: root@msi-ge60-ubuntu:/media/actionmystique/SAMSUNG-Ext4/KVM-Qemu/VMs# ssh -v -p 22 -i ./KVM-Ubuntu-Server-15.04-ubuntu-id_rsa ubuntu@172.16.100.245 OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to 172.16.100.245 [172.16.100.245] port 22. debug1: Connection established. debug1: key_load_private_type: No such file or directory debug1: key_load_private_cert: No such file or directory debug1: key_load_private_cert: No such file or directory debug1: key_load_private_cert: No such file or directory debug1: key_load_private_cert: No such file or directory debug1: key_load_private_type: No such file or directory debug1: permanently_set_uid: 0/0 debug1: identity file ./KVM-Ubuntu-Server-15.04-ubuntu-id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file ./KVM-Ubuntu-Server-15.04-ubuntu-id_rsa-cert type -1 debug1: identity file /root/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Ubuntu-5ubuntu1.3 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Ubuntu-5ubuntu1.3 debug1: match: OpenSSH_6.7p1 Ubuntu-5ubuntu1.3 pat OpenSSH* compat 0x0400 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-sha1 none debug1: kex: client->server aes128-ctr hmac-sha1 none Unable to negotiate a key exchange method Am I missing something? ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1497263 Title: Unable to negotiate a key exchange method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1497263/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
@michael.heuberger, it works fine for me already with the packages currently available from the Ubuntu repositories. If you downgraded the DNS packages, you can upgrade them to the latest version. It works very well for me. Just upgrade your whole Ubuntu 15.04 system. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
I removed the holds on all aforementioned packages, and upgraded them to the latest versions from repositories a few minutes ago. I am not experiencing problems anymore. DNS works fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
I have no idea, I am just a guy that happened to do a little research on this bug. I do not maintain this package and I haven't read its source code. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
Possible culprits: libdns100_1:9.9.5.dfsg-9ubuntu0.3_amd64.deb libdns-export100_1:9.9.5.dfsg-9ubuntu0.3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1488056/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
When connecting to an OpenVPN network with NetworkManager, I see these same messages just after dnsmasq reports "using nameserver ...," then the system fails to use those nameservers. This means that my system is not using the DNS servers that correspond to the VPN, but those that were already set in the system. The upgrade that caused this must have happened earlier today. It was working fine less than two hours ago. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1488056/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
I downgraded these packages and the problem got solved: libbind9-90 dnsutils libisccfg90 libdns100 libisc95 liblwres90 bind9-host Version those packages downgraded to: 1:9.9.5.dfsg-9 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
I have determined it is one of the packages related to bind9, as comments show. ** Package changed: dnsmasq (Ubuntu) => bind9 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+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 1486865] Re: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main)
Mathieu Trudel-Lapierre wrote: Having a new rrdtool and not lagging behind would be good, I think. I'll complete the bug on Monday when I am back home, we just need to list things from the upstream ChangeLog. Here it is: RRDtool 1.5.4 - 2015-08-09 == Bug Fixes - * parse floating point numbers according to C locale in rrdtool create arguments, regardles of the systems locale setting. * include missing rrd_rados.h into distribution archive * make rrdtool work on ARM again * make rrdtool test suit pass on 32bit OSs * fix --grid-dash option regression in graph * fix systemd support * fix link dependency for libpng since we are using functions directly * fix python modulename * fix rrdtool tune to accept U in minimum and maximum options * fi * rrd_parsetime now uses a mutex lock to become threadsafe * rrd_xport is now threadsafe * stop using MAX_PATH and make everything dynamic and make rrdtool work on Gnu HURD ... thanks nirgal! Features * new RPN operators: STEPWIDTH, NEWDAY, NEWWEEK, NEWMONTH and NEWWEEK together they allow to draw graphs where a rate is converted back to absolute numbers and accumulated over a periode. RRDtool 1.5.3 - 2015-04-30 == Bug Fixes - * Brought commmand-line options and documentation back into sync. * Make LINE dashes option work again RRDtool 1.5.2 - 2015-04-23 == Bug Fixes - * paramters in VDEF are vnames and not data source names, hence they can be 255 chars long and not only 20 RRDtool 1.5.1 - 2015-04-22 == Bug Fixes - * parse numbers up to 40 characters long .. * fix install rules for Python and Lua * include missing VERSION and LICENSE file * unlink before rename in rrd_create when running on WIN32 RRDtool 1.5.0 - 2015-04-16 == New Features * automatic x-axis labels that work from 1s to 30y on a single chart * librados integration * new datasource types: DCOUNTER and DDERIVE (they work the same as the original DS, except that they can deal with floatingpoint numbers). * compile without graphics libraries: ./configure --disable-rrd_graph * updated windows port (see WIN32-BUILD-TIPS.txt) * single step RRAs for MIN,MAX,LAST are generated virtually from an AVERAGE RRA * ignore updates in the past with rrdtool update --skip-past-updates * ignore a LINE when scaling a chart using the skipscale option * detect 32bit timeoverflows * massive performance boost for charts with more than 100 DEF line by switching form a linear search to a HASH when searching for data * improved cross compilation support * .Net bindings * allow rrdtool graph to silently skip non-existing source files using the --use-nan-for-all-missing-data option * restore from a pipe (rrdtool restore - y.rrd) * in rrdtool create, row count and step can be defined in absolute time * all new create on steroids can pull both data and configuration from existing rrd files * use rrdtool graph to chart arbitrary data via a callback function for data fetching support is integrated in the perl bindings. * re-written parser for rrdtool graph commands. It now follows a simple key value pattern, compatible with the previous syntax. * MEDIAN op for CDEF expressions * DEPTH,INDEX,COPY,ROL ops for CDEF (as seen in PostScript) * gradient AREA backgrounds * no more locale magic while reading numeric data. Bugfixes all the bugs fixed in 1.4.x during 1.5 development RRDtool 1.4.9 - 2014-09-29 == New Features * allows rrdrestore to read input from stdin * add documentation for RRDs::xport * RPN operators MINNAN and MAXNAN * --left-axis-format option to rrd_graph Bugfixes * properly verify validity of user suplied format strings * remove graph functions from python module when compiled without graphing support * verify that only short integers are used in COMPUTE rpn expressions * eliminate duplicate setlocale calls * fixed endless loop and double frees in rrd_restore * fixed missing variable initializations in rrd_graph * fixed JSON output format to actually be valid JSON * detect failing fallocate and fall back to seeking * fixed format string in ruby bindings -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rrdtool in Ubuntu. https://bugs.launchpad.net/bugs/1486865 Title: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rrdtool/+bug/1486865/+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 1486865] Re: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main)
If you don't want version 1.5, you should at least take 1.4.8-3 that fixes use-after-free stuff. http://metadata.ftp-master.debian.org/changelogs/main/r/rrdtool/unstable_changelog Mathieu Trudel-Lapierre: Unfortunately we missed the Feature Freeze cutoff (and I realise it's partly my fault). Let's fix this bug up to add the details needed for a Freeze Exception (https://wiki.ubuntu.com/FreezeExceptionProcess) ** Changed in: rrdtool (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rrdtool in Ubuntu. https://bugs.launchpad.net/bugs/1486865 Title: Sync rrdtool 1.5.4-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rrdtool/+bug/1486865/+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 1486865] [NEW] Sync rrdtool 1.5.4-5 (main) from Debian unstable (main)
Public bug reported: Please sync rrdtool 1.5.4-5 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Resynchronise with Debian. Remaining changes: - Updating to lua 5.2 version: - debian/rules: build 5.2 version, use autoconf. - debian/control: update lua to 5.2 version, added autoreconf. - debian/liblua5.2-rrd0.install: updated path to 5.2 version. - debian/liblua5.2-rrd-dev.install: updated path to 5.2 version. - debian/patches/rrdtool-1.4.7-lua-5.2.patch: fixes for lua 5.2 version. - Enable verbose build. - Stop building the librrd-ruby1.8 transitional package. Hi. New debian version support lua5.2 out of the box. See new binary package lua-rrd and lua-rrd-dev. (lua5.3 is there too) The is no Ubuntu reverse dependency on Ubuntu-specific packages liblua5.2-rrd-dev and liblua5.2-rrd0, so adding transitionnal packages in Ubuntu is not really necessary (If someone has time to make them, that would be nice however). The other Ubuntu changes (verbose build and drop of librrd-ruby1.8) are now in Debian. Changelog entries since current wily version 1.4.8-1.2ubuntu1: rrdtool (1.5.4-5) unstable; urgency=medium * Removed Multi-Arch:no. (Closes: #795646) * Added support for lua5.3. * Removed rrdcached from hurd since it uses 'Not implemented' functions. * Reduced build and -dev dependencies. -- Jean-Michel Vourgère nir...@debian.org Mon, 17 Aug 2015 16:08:45 +0200 rrdtool (1.5.4-4) unstable; urgency=medium * Allowed dh_install to proceed when python-setuptools is not installed. * Added patch 390x_first_week_day to fix unit tests on 390x architectures. * Enabled Multi-Arch. Partial support due to #117142. Lintian override for python debug symbols (See #795275). * Enabled perl-shared unit tests. * Refreshed lua patches headers: Applied-Upstream. -- Jean-Michel Vourgère nir...@debian.org Fri, 14 Aug 2015 15:26:41 +0200 rrdtool (1.5.4-3) unstable; urgency=medium * Added new patches to support lua5.2. Thanks Yolanda Robla. * Switched building of lua, perl, python and ruby bindings packages to use debhelper specific buildsystems: - Created packages lua-rrd and lua-rrd-dev, providing support for both lua 5.1 and 5.2. The old packages are now transitional. Added dependency on dh_lua. - Adjusted cleaning, installing and testing to these systems. * Force LC_ALL during the build; Re-enabled rpn2 unit test. * Enabled rrdcached unit test. * d/control: Dropped pre-Jessie transitions. * Dropped unused lintian overrides. -- Jean-Michel Vourgère nir...@debian.org Wed, 12 Aug 2015 17:23:20 +0200 rrdtool (1.5.4-2) unstable; urgency=low * Force UTF-8 encoding and UTC timezone on build. * patches/breaks-long-man-lines: Force UTF-8. * New patch 7digits to limit precision in unit test success checks. -- Jean-Michel Vourgère nir...@debian.org Sun, 09 Aug 2015 22:58:54 +0200 rrdtool (1.5.4-1) unstable; urgency=low * Added myself in uploaders. * Update d/watch to look dirrectly at github. * New upstream version: - Fixes json output (Closes: #686825) - Fixes rrdupdate duplicate paragraph in man (Closes: #603507) - Adds support for floating point values with DERIVE, COUNTER with new datasource types: DCOUNTER and DDERIVE. (Closes: #543631) - Fixes compilation on hurd. (Closes: #721975) - Provide a python example with locale setup. (Closes: #729007). - Drop all patches but no-rpath-for-ruby: Applied upstream. - Added build-dependency on dc. - Ignoring new systemd files that would change the socket location and many options. Using upstream lsb files from github. (Closes: #717248, #748656) * Moved project to alioth: Updated maintainer address and Vcs-* fields. * Dropped transitional packages librrd-ruby*. * Bumped standards to 3.9.6: No change required. * Switch copyright to DEP5 format. * Bumped source format to 3.0 (quilt): - Dropped d/README.source; - Dropped quilt has a dependency. * Minimized d/rules: - Using dh_auto_configure fixes all hardening but for ruby. - Uses /usr/lib/arch-triplet. - Clean using d/clean. * Enabled verbose build. * Re-enabled optimisations on arm. (Closes: #467342) * Disable rpn2 unittest that fails. * Made the builds reproducible: - Set up fake BUILD_DATE and BUILD_TIME in d/rules from changelog. - New patch reproducible-builds to use these. * Added patch breaks-long-man-lines to fix Cant break line warnings. * Added librrd4.lintian-overrides for false positive. -- Jean-Michel Vourgère nir...@debian.org Sun, 09 Aug 2015 17:43:02 +0200 rrdtool (1.4.8-1.3) unstable; urgency=medium * Non-maintainer upload. * Fix setlocale calls, causing free'd memory usage. Thanks Matthias Nagel. (Closes: #751842) * Add libpng-dev as an alternative to libpng12-dev. (Closes: #662494) -- Jean-Michel Vourgère nir...@debian.org
[Bug 1471486] Re: package mysql-common 5.6.24-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I need mysql with version prior to 5.6, so I uninstalled all mysql packages and installed mysql-5.1.63-linux-x86_64-glibc23 from tgz , the system was ok (no kroken packages). But it seems that during the update, the installation the installation of package mysql-common 5.6.24-0ubuntu2.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1471486 Title: package mysql-common 5.6.24-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1471486/+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 1432414] Re: printing service not available after recent upgrade
What is the value of the 'Listen' variable in /etc/cups/cupsd.conf ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ssl-cert in Ubuntu. https://bugs.launchpad.net/bugs/1432414 Title: printing service not available after recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1432414/+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 1432414] Re: printing service not available after recent upgrade
You can get this value by typing the following command in a terminal: sudo grep Listen /etc/cups/cupsd.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ssl-cert in Ubuntu. https://bugs.launchpad.net/bugs/1432414 Title: printing service not available after recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1432414/+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 1407818] Re: pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio variables
** Summary changed: - pm-utils reset the vm.dirty_ratio and vm.dirty_background_bytes variables + pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio variables ** Description changed: On a desktop system, on AC power, pm-utils reset the vm.dirty_ratio and - vm.dirty_background_ratio at boot time. + vm.dirty_background_ratio at boot time (which also reset the + vm.dirty_bytes and vm.dirty_background_bytes variables). When setting these variables using sysctl.conf, they are silently reset by the /usr/lib/pm-utils/power.d/laptop-mode script shipped with pm- utils. The only way to give specific values to these variables using sysctl is to remove this script. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/power.d/laptop-mode] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jan 5 23:00:09 2015 PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: Upgraded to trusty on 2014-04-21 (259 days ago) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1407818 Title: pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1407818/+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 1407818] Re: pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio variables
** Description changed: On a desktop system, on AC power, pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio at boot time (which also reset the vm.dirty_bytes and vm.dirty_background_bytes variables). When setting these variables using sysctl.conf, they are silently reset by the /usr/lib/pm-utils/power.d/laptop-mode script shipped with pm- utils. The only way to give specific values to these variables using sysctl is to remove this script. + + The default values applied by pm-utils are vm.dirty_background_ratio=5 + and vm.dirty_ratio=10. On my 64-bits system with 16 GB RAM, this amounts + to 1.6 GB for vm.dirty_bytes and 800 MB for vm.dirty_background_bytes + (see http://lwn.net/Articles/572911/). These values are not reasonable + for my system and pm-utils prevents me to change them. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/power.d/laptop-mode] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jan 5 23:00:09 2015 PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: Upgraded to trusty on 2014-04-21 (259 days ago) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1407818 Title: pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1407818/+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 1407818] [NEW] pm-utils reset the vm.dirty_ratio and vm.dirty_background_bytes variables
Public bug reported: On a desktop system, on AC power, pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio at boot time. When setting these variables using sysctl.conf, they are silently reset by the /usr/lib/pm-utils/power.d/laptop-mode script shipped with pm- utils. The only way to give specific values to these variables using sysctl is to remove this script. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/power.d/laptop-mode] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jan 5 23:00:09 2015 PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: Upgraded to trusty on 2014-04-21 (259 days ago) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1407818 Title: pm-utils reset the vm.dirty_ratio and vm.dirty_background_bytes variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1407818/+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 1394919] Re: constant crash in trying to collect info for recoverable error of cgmanager
Here are all the logs you requested. The first dbus-send command hangs and the second works. Perhaps it is a coincidence but the problem seems to be triggered when the systems running out of memory, killed webapp-container and tries to restore gmail webapp (or maybe any other webapp) In syslog webapp-container is killed at Nov 25 08:24:23 ubuntu-phablet kernel: [16138.987397]Killing 'webapp-containe' (23587), adj 900, It almost match with the time of the apport crash (symptom of this bug) $ grep ^Date /var/crash/_usr_share_apport_recoverable_problem.32011.crash Date: Tue Nov 25 08:24:50 2014 ** Attachment added: 20141125_1394919_logs.tgz https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+attachment/4267492/+files/20141125_1394919_logs.tgz ** Summary changed: - constant crash in trying to collect info for recoverable error of cgmanager + cgproxy hangs ** Changed in: cgmanager (Ubuntu) Importance: Undecided = Critical ** Changed in: apport (Ubuntu) Status: Confirmed = Invalid ** Changed in: apport (Ubuntu RTM) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1394919 Title: cgproxy hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+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 1394919] Re: cgproxy hangs
*** This bug is a duplicate of bug 1377332 *** https://bugs.launchpad.net/bugs/1377332 I'm marking this report as duplicate of 1377332 since this is the original issue and apport was the symptom. I created bug 1396160 for apport specific issue. ** This bug has been marked a duplicate of bug 1377332 [TOPBLOCKER] UI randomly freezes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1394919 Title: cgproxy hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1394919/+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 1360780] [NEW] Setup Error
Public bug reported: Ubuntu 14.04.1 LTS root@MSI-GE60-Ubuntu-14:/home/actionmystique/Program-Files/Ubuntu/Libvirt-python/libvirt-python-1.2.2# python setup.py build running build /usr/bin/python generator.py libvirt /usr/local/share/libvirt/api/libvirt-api.xml Found 388 functions in /usr/local/share/libvirt/api/libvirt-api.xml Found 0 functions in libvirt-override-api.xml Generated 325 wrapper functions Missing type converters: virNetworkDHCPLeasePtr **:1 virNetworkDHCPLeasePtr:1 long long *:1 unsigned int *:1 char **:2 ERROR: failed virDomainFSFreeze ERROR: failed virDomainFSThaw ERROR: failed virDomainGetTime ERROR: failed virNetworkDHCPLeaseFree ERROR: failed virNetworkGetDHCPLeases ERROR: failed virNodeGetFreePages error: command '/usr/bin/python' failed with exit status 1 ** Affects: libvirt-python (Ubuntu) Importance: Undecided Status: New ** Tags: libvirt-python ** Tags added: libvirt-python -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt-python in Ubuntu. https://bugs.launchpad.net/bugs/1360780 Title: Setup Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt-python/+bug/1360780/+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 1353923] [NEW] Installing Docker Breaks KVM
Public bug reported: Installing Docker 0.9.1 on Ubuntu 14.04 Desktop: - creates a new bridge docker0 - deletes virbr0 Since thern, I've never been able to restore the correct environment for KVM, even by uninstalling docker. If I try to manually add the bridge with *brctl addbr virbr0*, the creation does not survive across reboots and: virsh net-start default error: Failed to start network default error: Unable to create bridge virbr0: File exists Very strange error. What must be done to solve or workaround that issue? Any help will be greatly appreciated. ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1353923 Title: Installing Docker Breaks KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1353923/+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 1337492] [NEW] pcre support missing for snmpd
Public bug reported: Hi, I'd like to monitor my running processes on my server with snmp. Snmp offers this feature but when you have process running like: perl /usr/sbin/mysql-snmp --daemon-pid /var/run/mysql-snmp.pid -c /etc/mysql-snmp/my.cnf the process name detected by snmp is perl... They have pcre support to be able to add patterns to better detect process name proc mysql-snmp 1 1 ^perl /usr/sbin/mysql-snmp instead of proc mysql-snmp 1 1 The current package is not compiled with pcre support. Could this be added/updated ? looks like you would need to add pcre-devel as package dependency. Thank you. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1337492 Title: pcre support missing for snmpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1337492/+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 1313739] Re: package samba-libs (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1
Ok, it seems to be a known bug. When trying to reinstall samba-libs, the log states : secrets.tdb exists in /var/lib/samba and /var/lib/samba/private, aborting samba-libs preinst rename one of them to allow the install/upgrade to continue http://bugs.debian.org/726472 Renaming the file and reinstalling seems to work. ** Bug watch added: Debian Bug tracker #726472 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726472 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1313739 Title: package samba-libs (not installed) failed to install/upgrade: le sous- processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1313739/+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 1313739] [NEW] package samba-libs (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1
Public bug reported: Encountered an issue while updating from 13.10 to 14.04 : the upgrade encountered an error, stated the system could be unusable. Every time I tried to use sudo afterwards, it resulted in a segmentation fault (core dumped error. I removed samba (and a lot of other, important looking, packages) via synaptic, and now sudo works again. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: samba-libs (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Mon Apr 28 15:28:32 2014 DuplicateSignature: package:samba-libs:(not installed):le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2013-07-18 (283 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) SourcePackage: samba Title: package samba-libs (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to trusty on 2014-04-28 (0 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1313739 Title: package samba-libs (not installed) failed to install/upgrade: le sous- processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1313739/+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 1313739] Re: package samba-libs (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1
I must say it looks a lot like the bugs reported in these questions : http://askubuntu.com/questions/449325/failed-upgrade-of-l-xubuntu-13-10-to-14-04 and http://ubuntuforums.org/showthread.php?t=2219927 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1313739 Title: package samba-libs (not installed) failed to install/upgrade: le sous- processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1313739/+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 1311158] Re: WebUI do not work after fresh install
*** This bug is a duplicate of bug 1311433 *** https://bugs.launchpad.net/bugs/1311433 I confirm the workaround. I got it working with: sudo apt-get install -y --force-yes python-django=1.6.1-2 sudo dpkg-reconfigure maas-region-controller -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1311158 Title: WebUI do not work after fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1311158/+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 1306575] [NEW] package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgrade test from Precise AMD64 to Trusty with nearly all of main installed. Note that nova.conf has not been manually modified before upgrade. From apt-term.log: Setting up nova-common (1:2014.1~rc2-0ubuntu1) ... Installing new version of config file /etc/logrotate.d/nova-manage ... Installing new version of config file /etc/nova/api-paste.ini ... Installing new version of config file /etc/nova/policy.json ... Installing new version of config file /etc/nova/nova.conf ... Installing new version of config file /etc/sudoers.d/nova_sudoers ... Command failed, please check log for more info 2014-04-11 12:03:57.516 57962 CRITICAL nova [-] KeyError: VerNum(83) 2014-04-11 12:03:57.516 57962 TRACE nova Traceback (most recent call last): 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/bin/nova-manage, line 10, in module 2014-04-11 12:03:57.516 57962 TRACE nova sys.exit(main()) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/cmd/manage.py, line 1374, in main 2014-04-11 12:03:57.516 57962 TRACE nova ret = fn(*fn_args, **fn_kwargs) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/cmd/manage.py, line 883, in sync 2014-04-11 12:03:57.516 57962 TRACE nova return migration.db_sync(version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/migration.py, line 29, in db_sync 2014-04-11 12:03:57.516 57962 TRACE nova return IMPL.db_sync(version=version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/migration.py, line 44, in db_sync 2014-04-11 12:03:57.516 57962 TRACE nova return versioning_api.upgrade(get_engine(), repository, version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 186, in upgrade 2014-04-11 12:03:57.516 57962 TRACE nova return _migrate(url, repository, version, upgrade=True, err=err, **opts) 2014-04-11 12:03:57.516 57962 TRACE nova File string, line 2, in _migrate 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py, line 159, in with_engine 2014-04-11 12:03:57.516 57962 TRACE nova return f(*a, **kw) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/api.py, line 345, in _migrate 2014-04-11 12:03:57.516 57962 TRACE nova changeset = schema.changeset(version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/schema.py, line 80, in changeset 2014-04-11 12:03:57.516 57962 TRACE nova changeset = self.repository.changeset(database, start_ver, version) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/repository.py, line 225, in changeset 2014-04-11 12:03:57.516 57962 TRACE nova changes = [self.version(v).script(database, op) for v in versions] 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/repository.py, line 189, in version 2014-04-11 12:03:57.516 57962 TRACE nova return self.versions.version(*p, **k) 2014-04-11 12:03:57.516 57962 TRACE nova File /usr/lib/python2.7/dist-packages/migrate/versioning/version.py, line 155, in version 2014-04-11 12:03:57.516 57962 TRACE nova return self.versions[VerNum(vernum)] 2014-04-11 12:03:57.516 57962 TRACE nova KeyError: VerNum(83) 2014-04-11 12:03:57.516 57962 TRACE nova dpkg: error processing package nova-common (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nova-common 1:2014.1~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 11 12:03:58 2014 DuplicateSignature: package:nova-common:1:2014.1~rc2-0ubuntu1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all SourcePackage: nova Title: package nova-common 1:2014.1~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-04-11 (0 days ago) mtime.conffile..etc.nova.nova.conf: 2014-04-11T12:03:56.317961 ** Affects: nova (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-package rls-t-incoming trusty uec-images ** Description changed: - Upgrade test from Precise AMD64 to Trusty + Upgrade test from Precise AMD64 to Trusty with nearly all of main + installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nova-common 1:2014.1~rc2-0ubuntu1 ProcVersionSignature: Ubuntu
[Bug 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
I'm reopening this report, it is still an issue with krb5 1.12+dfsg- 2ubuntu3 ** Changed in: krb5 (Ubuntu Trusty) Status: Fix Released = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1304403] Re: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9
New apt.log for P-T upgrade See also bug 1304702 for an upgrade with the same failure from S to T ** Attachment added: apt_krb5_1.12+dfsg-2ubuntu3.log https://bugs.launchpad.net/ubuntu/trusty/+source/krb5/+bug/1304403/+attachment/4076761/+files/apt_krb5_1.12%2Bdfsg-2ubuntu3.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1304403] Re: Precise to Trusty - all of main - fails: The package 'postgresql-server-dev-9.1' is marked for removal but it's in the removal blacklist
** Also affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Precise to Trusty - all of main - fails: The package 'postgresql-server-dev-9.1' is marked for removal but it's in the removal blacklist + Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1304403 Title: Precise to Trusty - all of main - fails: Broken transition from libkadm5srv-mit8 to libkadm5srv-mit9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1304403/+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 1267367] [NEW] lxc-create shouldn't create container when template is called with --help argument
Public bug reported: When option --help is passed as template argument, lxc-create creates the base directory structure of the container. Then next call to lxc- create with the same name will fail because the container already exists. TEST CASE: 1. $ sudo lxc-create -n test--help -t ubuntu -- -h [...] output of lxc-ubuntu -h [...] $ sudo lxc-create -n test--help -t ubuntu -- -a amd64 Container already exists EXPECTED RESULT Container is not created and another call to lxc-create with the same name can be executed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta1-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 9 09:19:01 2014 SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2012-01-31 (708 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug trusty ** Description changed: When option --help is passed as template argument, lxc-create creates the base directory structure of the container. Then next call to lxc- create with the same name will fail because the container already exists. TEST CASE: 1. $ sudo lxc-create -n test--help -t ubuntu -- -h [...] output of lxc-ubuntu -h [...] $ sudo lxc-create -n test--help -t ubuntu -- -a amd64 Container already exists EXPECTED RESULT - Container is not create and another call to lxc-create with the same name can be executed. + Container is not created and another call to lxc-create with the same name can be executed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.0~beta1-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 9 09:19:01 2014 SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2012-01-31 (708 days ago) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up -- 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/1267367 Title: lxc-create shouldn't create container when template is called with --help argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267367/+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 1267367] Re: lxc-create shouldn't create container when template is called with --help
** Summary changed: - lxc-create shouldn't create container when template is called with --help argument + lxc-create shouldn't create container when template is called with --help -- 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/1267367 Title: lxc-create shouldn't create container when template is called with --help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267367/+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 1267367] Re: lxc-create shouldn't create container when template is called with --help
test--help is the name of the container, it is just a bad name. Sorry for the confusion. You can try with lxc-create -n lp1267367 -t ubuntu -- -h or any name. ** Changed in: lxc (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/1267367 Title: lxc-create shouldn't create container when template is called with --help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1267367/+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 390730] Re: mdb-export prints binary for OLE fields.
** Changed in: mdbtools (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mdbtools in Ubuntu. https://bugs.launchpad.net/bugs/390730 Title: mdb-export prints binary for OLE fields. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdbtools/+bug/390730/+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 1227033] Re: mdb-sql crashed with SIGSEGV in _IO_vfprintf_internal()
** Changed in: mdbtools (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mdbtools in Ubuntu. https://bugs.launchpad.net/bugs/1227033 Title: mdb-sql crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdbtools/+bug/1227033/+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 1244910] Re: dep8 test failed: missing test dependency '@'
** Changed in: cherrypy3 (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cherrypy3 in Ubuntu. https://bugs.launchpad.net/bugs/1244910 Title: dep8 test failed: missing test dependency '@' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cherrypy3/+bug/1244910/+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 1227033] Re: mdb-sql crashed with SIGSEGV in _IO_vfprintf_internal()
Fixed upstream https://github.com/brianb/mdbtools/commit/abcb273f2b7ec2bfb743c79ebbc390f817cab3e6 ** Changed in: mdbtools (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mdbtools in Ubuntu. https://bugs.launchpad.net/bugs/1227033 Title: mdb-sql crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdbtools/+bug/1227033/+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 1237866] [NEW] package php5-pgsql 5.4.9-4ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2
Public bug reported: Bonjour, Aucune mise a jour n'est accepté, avec le motif suivant l'installation ou la suppression d'un paquet logiciel a échoué, le paquet en question doit être php5-ldap;i386 que j'ai tenté de supprimé et de réinstallé mais j'ai subi le bug que je viens de vous soumettre. Traduction anglaise (selon mes moyens) ... English translation (within my means) No update is accepted with the following pattern installation or removal of a software package failed , the package in question must be php5-ldap; i386 I tried deleted and to reinstall but I experienced the bug that I just submitted. Cordialement ProblemType: Package DistroRelease: Ubuntu 13.04 Package: php5-pgsql 5.4.9-4ubuntu2.3 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: i386 Date: Thu Oct 10 11:11:35 2013 DpkgTerminalLog: Paramétrage de php5-pgsql (5.4.9-4ubuntu2.3) ... Not replacing deleted config file /etc/php5/mods-available/pgsql.ini ERROR: /etc/php5/mods-available/pgsql.ini does not exist dpkg: erreur de traitement de php5-pgsql (--configure) : le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 DuplicateSignature: package:php5-pgsql:5.4.9-4ubuntu2.3:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 InstallationDate: Installed on 2013-08-14 (56 days ago) InstallationMedia: Ubuntu Raring - Build i386 LIVE Binary 20130508-11:01 MarkForUpload: True SourcePackage: php5 Title: package php5-pgsql 5.4.9-4ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1237866 Title: package php5-pgsql 5.4.9-4ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1237866/+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 1232493] [NEW] package php5-pspell 5.4.9-4ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2
Public bug reported: A anomalies after update appears automaitquement Failed processing package installation or removal of a software package failed validate or configuration ProblemType: Package DistroRelease: Ubuntu 13.04 Package: php5-pspell 5.4.9-4ubuntu2.3 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.9.2-0ubuntu8.4 AptOrdering: php5-ldap: Configure php5-pgsql: Configure php5-pspell: Configure php5-snmp: Configure php5-tidy: Configure Architecture: i386 Date: Sat Sep 28 18:17:29 2013 DuplicateSignature: package:php5-pspell:5.4.9-4ubuntu2.3:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 InstallationDate: Installed on 2013-08-14 (45 days ago) InstallationMedia: Ubuntu Raring - Build i386 LIVE Binary 20130508-11:01 MarkForUpload: True SourcePackage: php5 Title: package php5-pspell 5.4.9-4ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1232493 Title: package php5-pspell 5.4.9-4ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1232493/+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 1216025] [NEW] package php5-ldap 5.4.9-4ubuntu2.2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2
Public bug reported: Impossible de lancer php5 ? ProblemType: Package DistroRelease: Ubuntu 13.04 Package: php5-ldap 5.4.9-4ubuntu2.2 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Fri Aug 23 18:44:41 2013 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 InstallationDate: Installed on 2013-08-14 (9 days ago) InstallationMedia: Ubuntu Raring - Build i386 LIVE Binary 20130508-11:01 MarkForUpload: True SourcePackage: php5 Title: package php5-ldap 5.4.9-4ubuntu2.2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1216025 Title: package php5-ldap 5.4.9-4ubuntu2.2 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1216025/+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 1216064] [NEW] package php5-pspell 5.4.9-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: NO ProblemType: Package DistroRelease: Ubuntu 13.04 Package: php5-pspell 5.4.9-4ubuntu2.2 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 AptOrdering: python-central: Install php5-ldap: Configure php5-pspell: Configure php5-snmp: Configure python-central: Configure Architecture: i386 Date: Fri Aug 23 19:00:36 2013 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2013-08-14 (9 days ago) InstallationMedia: Ubuntu Raring - Build i386 LIVE Binary 20130508-11:01 MarkForUpload: True SourcePackage: php5 Title: package php5-pspell 5.4.9-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1216064 Title: package php5-pspell 5.4.9-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1216064/+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 1212444] [NEW] cc_growpart failed in auto grow mode with Error: Could not stat device resizepart - No such file or directory. with parted 2.3-14
Public bug reported: During the provisioning of a local VM with cloud-init and parted 2.3.14, cc_growpart fails in auto grow mode with the following error: === 2013-08-14 08:07:02,117 - util.py[DEBUG]: Running command ['parted', 'resizepart', '/dev/vda', '1'] with allowed return codes [0] (shell=False, capture=True) 2013-08-14 08:07:02,139 - cc_growpart.py[DEBUG]: '/' FAILED: failed to resize: disk=/dev/vda, ptnum=1: Unexpected error while running command. Command: ['parted', 'resizepart', '/dev/vda', '1'] Exit code: 1 Reason: - Stdout: '\r \rError: Could not stat device resizepart - No such file or directory.\n' Stderr: '' === /dev/vda1 is not resized to use entire disk space and limited to 2GB. Run #90 on the 12th is successful with previous version of parted. Full log attached and online at [1] [1] http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt- setup-testbed/ARCH=amd64,label=albali/91/console ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cloud-init (not installed) ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 Uname: Linux 3.11.0-1-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 14 23:09:56 2013 InstallationDate: Installed on 2012-10-25 (293 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: cloud-init UpgradeStatus: Upgraded to saucy on 2012-12-02 (255 days ago) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: consoleText https://bugs.launchpad.net/bugs/1212444/+attachment/3773061/+files/consoleText -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1212444 Title: cc_growpart failed in auto grow mode with Error: Could not stat device resizepart - No such file or directory. with parted 2.3-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1212444/+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 1204518] Re: package apache2 2.4.4-6ubuntu5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Bug watch added: Debian Bug tracker #717496 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717496 ** Also affects: apache2 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717496 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1204518 Title: package apache2 2.4.4-6ubuntu5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1204518/+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 239048] Re: apache2 conf.d and sites-enabled oops
This is fixed in versio 2.4 ** Changed in: apache2 (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/239048 Title: apache2 conf.d and sites-enabled oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/239048/+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 1198833] [NEW] autopkgtest does not stop until service pygopherd is stopped or killed
Public bug reported: pygopherd is installed and started during autopkgtest of squid3 [1] as part of the test depedencies. But the run never ends until pygopherd is stopped/killed. The service should ever be stopped as part of the test cleanup, or autopkgtest should kill all the remaining children when all the tests are done. [1] http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt- squid3/22/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: squid3 3.1.20-1ubuntu7 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 8 10:22:26 2013 MarkForUpload: True SourcePackage: squid3 UpgradeStatus: Upgraded to saucy on 2012-01-31 (523 days ago) modified.conffile..etc.squid3.squid.conf: [modified] mtime.conffile..etc.squid3.squid.conf: 2012-08-07T15:04:05.743610 ** Affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Description changed: - pygopherd is installed and started during autopkgtest of squid3 as part - of the test depedencies. But the run never ends until pygopherd is + pygopherd is installed and started during autopkgtest of squid3 [1] as + part of the test depedencies. But the run never ends until pygopherd is stopped/killed. The service should ever be stopped as part of the test cleanup, or autopkgtest should kill all the remaining children when all the tests are done. + + [1] http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt- + squid3/22/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: squid3 3.1.20-1ubuntu7 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 8 10:22:26 2013 MarkForUpload: True SourcePackage: squid3 UpgradeStatus: Upgraded to saucy on 2012-01-31 (523 days ago) modified.conffile..etc.squid3.squid.conf: [modified] mtime.conffile..etc.squid3.squid.conf: 2012-08-07T15:04:05.743610 ** Also affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** Summary changed: - autopkgtest do not stop until pygopherd is killed + autopkgtest do not stop until service pygopherd is stopped or killed ** Summary changed: - autopkgtest do not stop until service pygopherd is stopped or killed + autopkgtest does not stop until service pygopherd is stopped or killed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1198833 Title: autopkgtest does not stop until service pygopherd is stopped or killed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1198833/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
I'm reopening because I can reproduce it on different hardware, but it doesn't fail when running the same command twice and it seems a bit racy. I'm searching for a way to reliably reproduce that problem. ** Changed in: lxc (Ubuntu) Status: Invalid = Confirmed ** Changed in: lxc (Ubuntu) Status: Confirmed = Incomplete -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
This is reproducible on several systems, but only the 1rst time I start a container when /sys/fs/cgroup/devices/lxc/NAME/ doesn't already exist. -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724404/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] lxc.default.txt
apport information ** Attachment added: lxc.default.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724406/+files/lxc.default.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
apport information ** Tags added: apparmor apport-collected ** Description changed: With kernel 3.10.0 lxc-create fails with the following error: lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012' is setup. lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called for subsys devices name lxc/saucy-i386-20130701-1012 lxc-start 1372673552.852 DEBUGlxc_cgroup - using cgroup mounted at '/sys/fs/cgroup/devices' lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: returning /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012 for subsystem devices.deny lxc-start 1372673552.852 ERRORlxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012/devices.deny : Invalid argument lxc-start 1372673552.852 ERRORlxc_conf - Error setting devices.deny to a for lxc/saucy-i386-20130701-1012 Second run of lxc-start works fine. Downgrading to 3.9.0-7 fixes the issue. The rootfs of the container is a loop-mounted squashfs from a loop- mounted ISO of latest saucy desktop image. pre-start, pre-mount, post-stop, lxc config and fstab attached ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 0.9.0-0ubuntu15 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 1 14:26:35 2013 MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2012-01-31 (516 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up + --- + ApportVersion: 2.10.2-0ubuntu3 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2012-10-25 (251 days ago) + InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) + MarkForUpload: True + Package: lxc 0.9.0-0ubuntu16 + PackageArchitecture: amd64 + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 + Tags: saucy apparmor + Uname: Linux 3.10.0-2-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2012-12-02 (214 days ago) + UserGroups: adm autopilot cdrom dip kvm lpadmin plugdev sambashare sudo wireshark + defaults.conf: + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724402/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
With otto from lp:otto I can reproduce the problem with the command: $ sudo ./bin/otto -d create -u lp1196518-$RANDOM ~/iso/ubuntu/saucy-desktop-amd64.iso The write(fd, value, strlen(value)) in do_cgroup_set in cgroup.c fails with Invalid Argument If the command is executed a second time with the same container name (replace $RANDOM by the number generated previoulsly), it works fine. -- 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] lxc-net.default.txt
apport information ** Attachment added: lxc-net.default.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724405/+files/lxc-net.default.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] KernLog.txt
apport information ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724403/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] lxcsyslog.txt
apport information ** Attachment added: lxcsyslog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724407/+files/lxcsyslog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
For the moment, the workaround is to remove lxc.cgroup.devices.deny from the config file, which is okay in our case since the machines are just test hosts, but is not in the general case. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] KernLog.txt
apport information ** Attachment added: KernLog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724623/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724626/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724622/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724620/+files/CurrentDmesg.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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Re: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10
apport information ** Description changed: With kernel 3.10.0 lxc-create fails with the following error: lxc-start 1372673552.852 NOTICE lxc_conf - 'saucy-i386-20130701-1012' is setup. lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: called for subsys devices name lxc/saucy-i386-20130701-1012 lxc-start 1372673552.852 DEBUGlxc_cgroup - using cgroup mounted at '/sys/fs/cgroup/devices' lxc-start 1372673552.852 DEBUGlxc_cgroup - cgroup_path_get: returning /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012 for subsystem devices.deny lxc-start 1372673552.852 ERRORlxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012/devices.deny : Invalid argument lxc-start 1372673552.852 ERRORlxc_conf - Error setting devices.deny to a for lxc/saucy-i386-20130701-1012 Second run of lxc-start works fine. Downgrading to 3.9.0-7 fixes the issue. The rootfs of the container is a loop-mounted squashfs from a loop- mounted ISO of latest saucy desktop image. pre-start, pre-mount, post-stop, lxc config and fstab attached ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 0.9.0-0ubuntu15 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Mon Jul 1 14:26:35 2013 MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2012-01-31 (516 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up --- ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2012-10-25 (251 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True Package: lxc 0.9.0-0ubuntu16 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Tags: saucy apparmor Uname: Linux 3.10.0-2-generic x86_64 UpgradeStatus: Upgraded to saucy on 2012-12-02 (214 days ago) UserGroups: adm autopilot cdrom dip kvm lpadmin plugdev sambashare sudo wireshark defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up + --- + ApportVersion: 2.10.2-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=9661ff9a-af2b-4768-a741-0a313db5b763 + InstallationDate: Installed on 2012-10-25 (251 days ago) + InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) + MachineType: ASUSTeK Computer Inc. U3SG + MarkForUpload: True + Package: lxc 0.9.0-0ubuntu16 + PackageArchitecture: amd64 + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=a25fbaa5-8321-48be-bd4f-d5027b955669 ro quiet splash swapaccount=1 vt.handoff=7 + ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + Tags: saucy saucy apparmor + Uname: Linux 3.10.0-2-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2012-12-02 (214 days ago) + UserGroups: adm autopilot cdrom dip kvm lpadmin plugdev sambashare sudo wireshark + defaults.conf: + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + dmi.bios.date: 01/28/2008 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 305 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: U3SG + dmi.board.vendor: ASUSTeK Computer Inc. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: ATN12345678901234567 + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK Computer Inc. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr305:bd01/28/2008:svnASUSTeKComputerInc.:pnU3SG:pvr1.0:rvnASUSTeKComputerInc.:rnU3SG:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: + dmi.product.name: U3SG + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK Computer Inc. ** Attachment added: AlsaInfo.txt
[Bug 1196518] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724618/+files/BootDmesg.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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724625/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724619/+files/CRDA.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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724621/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724624/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724631/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724628/+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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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 1196518] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1196518/+attachment/3724632/+files/UdevLog.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/1196518 Title: lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/NAME/devices.deny : Invalid argument with kernel 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196518/+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
