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
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
** 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 u
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.
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
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,
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 correc
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
T
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
** 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-
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/+attachmen
** 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 becau
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
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' (
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/bu
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 notification
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
17 matches
Mail list logo
