[Bug 1227195] Re: new upstream release
** Bug watch added: Debian Bug tracker #723662 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723662 ** Also affects: amavisd-new (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723662 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1227195 Title: new upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1227195/+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 1227195] [NEW] new upstream release
Public bug reported: According to http://www.ijs.si/software/amavisd/ a new release (2.8.1) was published on 2013-06-18. When will it be packaged? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: amavisd-new 1:2.7.1-2ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-30.22-lowlatency 3.8.13.6 Uname: Linux 3.8.0-30-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 Date: Wed Sep 18 17:03:16 2013 InstallationDate: Installed on 2012-06-14 (460 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: amavisd-new UpgradeStatus: Upgraded to raring on 2013-04-29 (142 days ago) ** Affects: amavisd-new (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1227195 Title: new upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1227195/+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 599342] Re: Temporary failure in name resolution
I am sorry for the delay. It looks like the grep from comment #13 will do the trick on standalone systems. Unfortunately we have moved away from KVM on our systems, so that I am not able to test it right now. -- 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/599342 Title: Temporary failure in name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+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 570513] Re: NIS-based autofs maps don't load on startup
This is a patch a applied to /etc/init/autofs.conf to make the autofs upstart job wait for NIS. The loop was inspired by the same loop in /etc/init.d/nis. ** Patch added: "Patch to /etc/init/autofs.conf waiting for NIS" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/570513/+attachment/2469380/+files/autofs.conf.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/570513 Title: NIS-based autofs maps don't load on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/570513/+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 517714] Re: [Lucid] Error starting domain: could not remove profile
I also encountered this issue just now. It is caused by an update of the
apparmor profile:
--- /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper 2010-04-14
14:19:00.0 +0200
+++ /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper.dpkg-dist2010-04-15
08:17:39.0 +0200
@@ -3,6 +3,7 @@
/usr/lib/libvirt/virt-aa-helper {
#include
+ #include
# needed for searching directories
capability dac_override,
@@ -14,9 +15,30 @@
deny @{PROC}/[0-9]*/mounts r,
@{PROC}/filesystems r,
+ # for hostdev
+ /sys/devices/ r,
+ /sys/devices/** r,
+
/usr/lib/libvirt/virt-aa-helper mr,
/sbin/apparmor_parser Ux,
/etc/apparmor.d/libvirt/* r,
/etc/apparmor.d/libvirt/libvirt-[0-9a-f]*-[0-9a-f]*-[0-9a-f]*-[0-9a-f]*-[0-9a-f]*
rw,
+
+ # For backingstore, virt-aa-helper needs to peek inside the disk image, so
+ # allow access to non-hidden files in @{HOME} as well as storage pools, and
+ # removable media and filesystems. A virt-aa-helper failure when checking a
+ # disk for backinsgstore is non-fatal (but obviously the backingstore won't
+ # be added).
+ audit deny @{HOME}/.* mrwkl,
+ audit deny @{HOME}/.*/ rw,
+ audit deny @{HOME}/.*/** mrwkl,
+ audit deny @{HOME}/bin/ rw,
+ audit deny @{HOME}/bin/** mrwkl,
+ @{HOME}/ r,
+ @{HOME}/** r,
+ /var/lib/libvirt/images/ r,
+ /var/lib/libvirt/images/** r,
+ /{media,mnt,opt,srv}/** r,
+ deny /dev/** mrwkl,
}
I reverted to the old one and virt-manager was able to start virtual
machines again.
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
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 511620] Re: write errors on virtual disc during install
Hi, where do I get qemu-kvm (0.12.3-0ubuntu15)? I have a lucid amd64 KVM host with similar symptoms but the available qemu-kvm version is only 0.12.3+noroms-0ubuntu9. -- write errors on virtual disc during install https://bugs.launchpad.net/bugs/511620 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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 599342] [NEW] Temporary failure in name resolution
Public bug reported: libvirt-bin is not started correctly. It tries to resolve the hostname when starting but at that time ther eis no network and no DNS available. It fails with error 6 and starts again immediately. After several attempts init disables the job completely: Jun 28 14:33:05 natta libvirtd: 14:33:05.885: error : virGetHostname:1838 : internal error getaddrinfo failed for 'natta': Temporary failure in name resolution Jun 28 14:33:05 natta init: libvirt-bin main process (1332) terminated with status 6 Jun 28 14:33:05 natta init: libvirt-bin main process ended, respawning Jun 28 14:33:05 natta libvirtd: 14:33:05.892: error : virGetHostname:1838 : internal error getaddrinfo failed for 'natta': Temporary failure in name resolution Jun 28 14:33:05 natta init: libvirt-bin main process (1338) terminated with status 6 Jun 28 14:33:05 natta init: libvirt-bin respawning too fast, stopped We have removed the "bogus" hostname entry from /etc/hosts poiting to a 127.0.0.2 address. Our network DNS resolves hostnames to their "real" IP addresses. If libvirt-bin needs to resolve a hostname to an IP address it should wait for the network when starting. The libvirt-bin upstart script may need a dependency. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libvirt-bin 0.7.5-5ubuntu27 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32.11-epi+drm33.2 x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Mon Jun 28 14:34:41 2010 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE= SourcePackage: libvirt ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Temporary failure in name resolution https://bugs.launchpad.net/bugs/599342 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 599342] Re: Temporary failure in name resolution
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/51031539/Dependencies.txt -- Temporary failure in name resolution https://bugs.launchpad.net/bugs/599342 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 599342] Re: Temporary failure in name resolution
After reading bug #595388 I have added the lines: hostname=$(hostname) until host $hostname do sleep 2s done to the pre-start section of libvirt-bin's upstart script. It works for me. -- Temporary failure in name resolution https://bugs.launchpad.net/bugs/599342 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 599342] Re: Temporary failure in name resolution
We have removed the local hostname from /etc/hosts pointing to 127.0.1.1 or any other address in 127.0.0.0/8, we only keep 127.0.0.1 for localhost in there. Every other name is resolved by our internal DNS. The loop above just waits until the DNS answers and the hostname can be resolved. Otherwise libvirtd refuses to start. We have reasons not to resolve the hostname to a 127.0.0.0/8 address. -- Temporary failure in name resolution https://bugs.launchpad.net/bugs/599342 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 1426910] [NEW] kdb5_ldap_util creates principal with wrong DNS domain
Public bug reported: If there is more than one domain in the "search" line of /etc/resolv.conf when kdb5_ldap_util create is used to populate the LDAP directory, a wrong hostname is composed. kdb5_ldap_util seems to use the last domain name of the search list, which is obviously not always correct. Maybe kdb5_ldap_util should use an algorithm like "hostname --fqdn" to determine the fully qualified domain name of the host. ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- 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/1426910 Title: kdb5_ldap_util creates principal with wrong DNS domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1426910/+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 1330504] Re: strongSwan 5.1.3
I am currently affected by https://wiki.strongswan.org/issues/547 which should be fixed in 5.1.3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1330504 Title: strongSwan 5.1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1330504/+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 1451091] [NEW] new upstream version 5.2.1
Public bug reported: Debian wheezy-backports and Debian jessie contain upstream version 5.2.1 of strongswan. Please make that available on Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: strongswan (not installed) ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 2 23:44:00 2015 InstallationDate: Installed on 2015-04-30 (2 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) SourcePackage: strongswan UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: strongswan (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 strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1451091 Title: new upstream version 5.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1451091/+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 1270193] [NEW] /etc/init.d/munin-node not systemd compliant
Public bug reported: The script in /etc/init.d/munin-node is not systemd compliant, but the package installs a systemd service: Setting up munin-node (2.0.17-2ubuntu1) ... Warning: The home dir /var/lib/munin you specified can't be accessed: No such file or directory Adding system user `munin' (UID 138) ... Adding new group `munin' (GID 149) ... Adding new user `munin' (UID 138) with group `munin' ... Not creating home directory `/var/lib/munin'. Initializing plugins..done. Restarting munin-node..munin-node start/running, process 19825 ln -s '/lib/systemd/system/munin-node.service' '/etc/systemd/system/multi-user.target.wants/munin-node.service' ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: munin-node 2.0.17-2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.8-lowlatency 3.11.10 Uname: Linux 3.11.0-15-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 17 16:38:54 2014 InstallationDate: Installed on 2012-06-14 (581 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: munin UpgradeStatus: Upgraded to saucy on 2013-10-29 (80 days ago) modified.conffile..etc.munin.plugin.conf.d.munin.node: [deleted] ** Affects: munin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy systemd ** Tags added: systemd -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/1270193 Title: /etc/init.d/munin-node not systemd compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1270193/+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 1270193] Re: /etc/init.d/munin-node not systemd compliant
The impact is that it is impossible to stop munin-node with sudo /etc/init.d/munin-node stop because systemd will automatically restart it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/1270193 Title: /etc/init.d/munin-node not systemd compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1270193/+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 1270193] Re: /etc/init.d/munin-node not systemd compliant
The xfce4-power-manager depends on systemd-services. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/1270193 Title: /etc/init.d/munin-node not systemd compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1270193/+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 1323814] Re: sshd: Default is PermitRootLogin without-password
** Also 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/1323814 Title: sshd: Default is PermitRootLogin without-password To manage notifications about this bug go to: https://bugs.launchpad.net/finnix/+bug/1323814/+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
