[Bug 1389954] Re: Make .lxc domain name resolution easier to discover and enable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) 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/1389954 Title: Make .lxc domain name resolution easier to discover and enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+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 957957] Re: kvm: 7767: cpu0 unhandled rdmsr: 0xc0010001
on all kernel bug printed after "login:" string in 3-5 sec also tested on: uname -a Linux br04 3.14.27-031427-generic #201412170558 SMP Wed Dec 17 11:18:06 UTC 2014 i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/957957 Title: kvm: 7767: cpu0 unhandled rdmsr: 0xc0010001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/957957/+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 1406729] Re: dig does not have a default trusted key
Considering that the 'bind9' package ships the root key (in /etc/bind/bind.keys), I see no reason why it should not also be shipped in the dnsutils package as well. -- 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/1406729 Title: dig does not have a default trusted key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1406729/+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 957957] Re: kvm: 7767: cpu0 unhandled rdmsr: 0xc0010001
bug in qemu-kvm kvm: 5116: cpu0 unhandled rdmsr: 0xc0010001 cat /var/log/syslog | grep -i msr Jan 2 04:06:10 br04 kernel: [ 41.718164] kvm: 4966: cpu0 unhandled rdmsr: 0xc0010001 Jan 2 04:13:09 br04 kernel: [ 39.274060] kvm [5057]: vcpu0 unhandled rdmsr: 0xc0010001 Jan 2 04:18:31 br04 kernel: [ 41.354130] kvm [5313]: vcpu0 unhandled rdmsr: 0xc0010001 Jan 2 04:50:28 br04 kernel: [ 42.597555] kvm [5334]: vcpu0 unimplemented perfctr wrmsr: 0xc0010004 data 0xabcd Jan 2 04:53:05 br04 kernel: [ 33.581614] kvm: 5135: cpu0 unhandled rdmsr: 0xc0010001 Jan 2 05:06:10 br04 kernel: [ 36.954154] kvm [5253]: vcpu0 unhandled rdmsr: 0xc0010001 Jan 2 05:25:38 br04 kernel: [ 33.045732] kvm: 5145: cpu0 unhandled rdmsr: 0xc0010001 Jan 2 05:29:46 br04 kernel: [ 34.870194] kvm: 5116: cpu0 unhandled rdmsr: 0xc0010001 version of kernel: 3.2 last - debian 3.0.101, 3.12.35, 3.18.1 - ubuntu mainline OS: debian 7.7 32 bit kvm guest: debian 7.7 32 bit - kernel 3.2 last update hw: cat /proc/cpuinfo | grep -i name model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ dmidecode | grep -i asus Version: ASUS M2N-E ACPI BIOS Revision 5001 RAM: 4GB = 1GBx4 PC2-6400 cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md1 : active raid5 sdd2[0] sda2[4] sdb2[2] sdc2[1] 5812959744 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] md0 : active raid5 sdd1[0] sda1[4] sdb1[2] sdc1[1] 47159808 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] Disk /dev/md0: 48.3 GB, 48291643392 bytes 2 heads, 4 sectors/track, 11789952 cylinders, total 94319616 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 524288 bytes / 1572864 bytes Disk identifier: 0x Disk /dev/md1: 5952.5 GB, 5952470777856 bytes 2 heads, 4 sectors/track, 1453239936 cylinders, total 11625919488 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 524288 bytes / 1572864 bytes Disk identifier: 0x lspci 00:00.0 RAM memory: NVIDIA Corporation MCP55 Memory Controller (rev a1) 00:01.0 ISA bridge: NVIDIA Corporation MCP55 LPC Bridge (rev a2) 00:01.1 SMBus: NVIDIA Corporation MCP55 SMBus (rev a2) 00:02.0 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a1) 00:02.1 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a2) 00:04.0 IDE interface: NVIDIA Corporation MCP55 IDE (rev a1) 00:05.0 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:05.1 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:05.2 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:06.0 PCI bridge: NVIDIA Corporation MCP55 PCI bridge (rev a2) 00:06.1 Audio device: NVIDIA Corporation MCP55 High Definition Audio (rev a2) 00:08.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:06.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 54) lspnp 00:00 PNP0a08 (unknown) 00:01 PNP0c02 Motherboard resources 00:02 PNP0c02 Motherboard resources 00:03 PNP0200 AT DMA controller 00:04 PNP0103 High-Precision Event Timer 00:05 PNP0b00 AT real-time clock 00:06 PNP0800 AT speaker 00:07 PNP0c04 Math coprocessor 00:08 PNP0501 16550A-compatible serial port 00:09 PNP0401 ECP printer port 00:0a PNP0303 IBM enhanced keyboard (101/102-key, PS/2 mouse support) 00:0b PNP0c02 Motherboard resources 00:0c PNP0c01 System board -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/957957 Title: kvm: 7767: cpu0 unhandled rdmsr: 0xc0010001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/957957/+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 1406998] [NEW] عااااااااااااااااااااااااا
Public bug reported: ع ** 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/1406998 Title: عا To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1406998/+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 1406992] [NEW] fgsdfsd
Public bug reported: gsdgdfgdf ** 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/1406992 Title: fgsdfsd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1406992/+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 1341607] Re: HTTP authentication does not work
** Description changed: After trying multiple suggestions over several days, basic HTTP auth for Apache subdirs still does not work, usually resulting in "No require lines available" in the error log regardless of what I do. Vhost config appears correct. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apache2 2.4.7-1ubuntu4 Uname: Linux 3.10.23--std-ipv6-64 x86_64 Apache2ConfdDirListing: False ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Mon Jul 14 10:34:47 2014 InstallationDate: Installed on 2014-04-16 (89 days ago) InstallationMedia: - + ProcEnviron: - TERM=xterm - SHELL=/bin/bash - PATH=(custom, no user) - LANG=en_GB.UTF-8 - XDG_RUNTIME_DIR= + TERM=xterm + SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_GB.UTF-8 + XDG_RUNTIME_DIR= SourcePackage: apache2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apache2.apache2.conf: [modified] modified.conffile..etc.apache2.conf.available.security.conf: [modified] modified.conffile..etc.apache2.sites.available.000.default.conf: [modified] modified.conffile..etc.apache2.sites.available.default.ssl.conf: [modified] mtime.conffile..etc.apache2.apache2.conf: 2014-07-14T10:25:05.510444 mtime.conffile..etc.apache2.conf.available.security.conf: 2014-07-07T17:05:25.329780 mtime.conffile..etc.apache2.sites.available.000.default.conf: 2014-07-11T13:31:30.026502 mtime.conffile..etc.apache2.sites.available.default.ssl.conf: 2014-07-07T17:06:21.225780 -- 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/1341607 Title: HTTP authentication does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1341607/+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 1406729] Re: dig does not have a default trusted key
I can confirm this for Vivid's 9.9.5.dfsg-6ubuntu1 package. Not convinced either way in regards to whatever Ubuntu should distribute a /etc/trusted-key.key file. (Not my call either.) ** Changed in: bind9 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: bind9 (Ubuntu) Status: New => Confirmed -- 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/1406729 Title: dig does not have a default trusted key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1406729/+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 1406945] [NEW] Difference between lxc autostart from init script and manual lxc-start call
Public bug reported: According to https://answers.launchpad.net/ubuntu/+source/lxc/+question/255408, there seem to be a difference between `lxc start` and the autostart feature lxc.start.auto. On my Ubuntu 14.10, I have problem starting up containers manually, but autostarting the same containers works without problems. I cannot see a difference, the file /etc/init/lxc-instance.conf is very simple and doesn't set any important additional environment variables. The log output is as follows # lxc-start -n vm-mycontainer -F lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make / rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /dev rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /dev/pts rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /dev/shm rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /dev/mqueue rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /dev/hugepages rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /run rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /run/lock rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /run/user rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /run/user/23001/gvfs rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/kernel/security rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/systemd rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/cpuset rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/cpu,cpuacct rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/memory rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/devices rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/freezer rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/net_cls,net_prio rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/blkio rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/perf_event rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/cgroup/hugetlb rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/pstore rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/kernel/debug rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /sys/fs/fuse/connections rslave lxc-start: conf.c: remount_all_slave: 3885 Continuing... lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to make /proc rslave
[Bug 1406939] [NEW] Upgraded to 7.3
Public bug reported:
Hi
When will the package for Awstats be upgraded to version 7.3?
the new release have some good new things:
New features:
- Add command line option -version
- Better error management of geoip modules.
- Update domains, robots and search engines database:
- #877 Windows 8 + iOS Support in AWStats
- Detection of 8.1 and IE11.
Fixes:
- When using builddate option of script awstats_buildstaticpages,
static link is wrong.
- Restore detection of Opera browsers versions.
- #838 GeoIP Cities page doesnt work.
- Add missing icons.
- #881 Avoid warning mixed http/https with module graphgooglechartapi.
- #918 $MinHit{'Host'} rather than $MinHit{'Login'} used in sub HTMLShowLogins.
Other:
- Move version system to sourceforge Git instead of CVS.
** Affects: awstats (Ubuntu)
Importance: Undecided
Status: New
** Tags: awstats
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awstats in Ubuntu.
https://bugs.launchpad.net/bugs/1406939
Title:
Upgraded to 7.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1406939/+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 1278529] Re: Using S3, "BackendException: No connection to backend"
** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Status: Confirmed => Fix Committed ** Changed in: duplicity Milestone: None => 0.7.01 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, "BackendException: No connection to backend" To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1278529/+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 1406925] [NEW] lxc-start fails due to insufficient permission for creating netdev
Public bug reported: After installing an lxc with `sudo lxc-create -n Ubuntu-12.04.5-i386 -t /usr/share/lxc/templates/lxc-ubuntu -- --release precise --mirror http://richtercloud.de:3142/de.archive.ubuntu.com/ubuntu --arch i386`, starting the container with `sudo lxc-start -n Ubuntu-12.04.5-i386 --foreground` fails due to the following error: lxc-start: conf.c: instanciate_veth: 2817 failed to attach 'vethY1J1I1' to the bridge 'lxcbr0' : Operation not permitted lxc-start: conf.c: lxc_create_network: 3100 failed to create netdev lxc-start: start.c: lxc_spawn: 829 failed to create the network lxc-start: start.c: __lxc_start: 1087 failed to spawn 'Ubuntu-12.04.5-i386' lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. It should be possible to start the container right away after installation of the apt package and handle eventually necessary setup tasks (of permissions, etc.) in `debconf`. Currently it's necessary to comment out all `lxc.network.*` entries in the container configuration file. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha2-0ubuntu3 ProcVersionSignature: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/proc/version_signature' Uname: Linux 3.17.7-031707-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 1 14:31:03 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-28 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lxc UpgradeStatus: Upgraded to utopic on 2014-12-28 (4 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx upstart.lxc-net.override: manual ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Description changed: After installing an lxc with `sudo lxc-create -n Ubuntu-12.04.5-i386 -t /usr/share/lxc/templates/lxc-ubuntu -- --release precise --mirror http://richtercloud.de:3142/de.archive.ubuntu.com/ubuntu --arch i386`, starting the container with `sudo lxc-start -n Ubuntu-12.04.5-i386 --foreground` fails due to the following error: - lxc-start: conf.c: instanciate_veth: 2817 failed to attach 'vethY1J1I1' to the bridge 'lxcbr0' : Operation not permitted - lxc-start: conf.c: lxc_create_network: 3100 failed to create netdev - lxc-start: start.c: lxc_spawn: 829 failed to create the network - lxc-start: start.c: __lxc_start: 1087 failed to spawn 'Ubuntu-12.04.5-i386' - lxc-start: lxc_start.c: main: 337 The container failed to start. - lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. + lxc-start: conf.c: instanciate_veth: 2817 failed to attach 'vethY1J1I1' to the bridge 'lxcbr0' : Operation not permitted + lxc-start: conf.c: lxc_create_network: 3100 failed to create netdev + lxc-start: start.c: lxc_spawn: 829 failed to create the network + lxc-start: start.c: __lxc_start: 1087 failed to spawn 'Ubuntu-12.04.5-i386' + lxc-start: lxc_start.c: main: 337 The container failed to start. + lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. It should be possible to start the container right away after installation of the apt package and handle eventually necessary setup tasks (of permissions, etc.) in `debconf`. + + Currently it's necessary to comment out all `lxc.network.*` entries in + the container configuration file. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha2-0ubuntu3 ProcVersionSignature: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/proc/version_signature' Uname: Linux 3.17.7-031707-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 1 14:31:03 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-28 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lxc UpgradeStatus: Upgraded to utopic on 2014-12-28 (4 days ago) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up - lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx upstart.lxc-net.override: manual -- 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/1406925 Title: lxc-start fails due to insufficient permission for creating netdev To manage notifications about this bug go to: https://bugs.launchpad
[Bug 1365444] Re: dlm has broken init script + missing a dependency
The attachment "dlm.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gfs2-utils in Ubuntu. https://bugs.launchpad.net/bugs/1365444 Title: dlm has broken init script + missing a dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/1365444/+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 1365444] Re: dlm has broken init script + missing a dependency
#!/bin/bash
# Compile and install Distributed Lock Manager.
apt-get -y install daemon
cd /usr/src
apt-get source dlm
apt-get build-dep dlm
cd dlm-*
# Patch for broken init reference.
sed -i "s|/etc/rc.d/init.d/functions|/lib/lsb/init-functions|" init/dlm.init
debuild -b
cd ..
dpkg -i libdlm*.deb # Prerequisite Depends for DLM.
dpkg -i dlm_*.deb
rm -rf {libdlm*,dlm*}
** Patch removed: "dlm.diff"
https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/1365444/+attachment/4290862/+files/dlm.diff
** Patch added: "dlm.diff"
https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/1365444/+attachment/4290863/+files/dlm.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gfs2-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1365444
Title:
dlm has broken init script + missing a dependency
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/1365444/+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 1365444] Re: dlm has broken init script + missing a dependency
#!/bin/bash
# Compile and install Distributed Lock Manager.
apt-get -y install daemon
cd /usr/src
apt-get source dlm
apt-get build-dep dlm
cd dlm-*
# Patch for broken init reference.
sed -i "s|/etc/rc.d/init.d/functions|/lib/lsb/init-functions|" init/dlm.init
debuild -b
cd ..
dpkg -i libdlm*.deb # Prerequisite Depends for DLM.
dpkg -i dlm_*.deb
rm -rf {libdlm*,dlm*}
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gfs2-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1365444
Title:
dlm has broken init script + missing a dependency
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/1365444/+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 1365444] Re: dlm has broken init script + missing a dependency
** Patch added: "dlm.diff" https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/1365444/+attachment/4290862/+files/dlm.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gfs2-utils in Ubuntu. https://bugs.launchpad.net/bugs/1365444 Title: dlm has broken init script + missing a dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfs2-utils/+bug/1365444/+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
