[Bug 807153] Re: named does not shut down after service bind9 stop
I disabled dnssec validation, and after a few days with a number of reboots and restarts of bind9, I haven't had any further trouble with stopping the bind9 service or with shutting down my system. So I'm pretty sure at this point that there's some bug with dnssec validation that intermittent prevents bind9 from shutting down properly. -- 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/807153 Title: named does not shut down after service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+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 807153] Re: named does not shut down after service bind9 stop
This looks like the bug I want to report. I find that shutting down bind9 is erratic: sometimes it succeeds, sometimes not. This is a common result of shutting it down at the command line: codebrian@$ sudo service bind9 stop * Stopping domain name service... bind9 rndc: connect failed: 127.0.0.1#953: connection refused/code I need to send a break (usually with CTRL-C) to get past this. I often have difficulty shutting down or rebooting my system, as it often hangs early in the process; bind9 seems to be among the first services to be shut down, so I suspect it is the root of that problem as well. I notice that Matthias pointed out that he is using IPv6 and dnssec. I am using an IPv6 tunnel and have configured bind9 for dnssec validation; I had purged and reinstalled bind9 in trying to troubleshoot this problem, and it didn't hang on restarts before I re-enabled dnssec validation. That was only a few restarts; with an intermittent problem, it's hard to be sure. I will try disabling dnssec validation for a few days and see if that helps. -- 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/807153 Title: named does not shut down after service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+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 853580] Re: Unable to start second virtual machine
@Soren -- Actually, you did help, as I didn't know where to look for troubleshooting information before your prompting. Thank you. -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
I'm attaching the xml files for server1.example.com and tester1.example.com, which I used when generating the error messages above. I have some other VMs defined, and I find that while I can start any one, any second one fails to start with the same error messages. ** Attachment added: server1.example.com.xml https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2425789/+files/server1.example.com.xml -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
** Attachment added: tester1.example.com.xml https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2425790/+files/tester1.example.com.xml -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
I am uploading the output from 'virsh dumpxml' for each domain. However, the output is identical to what I already posted. ** Attachment added: server1.example.com.xml https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2426894/+files/server1.example.com.xml -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
** Attachment added: tester1.example.com.xml https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2426895/+files/tester1.example.com.xml -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
That didn't seem to work. Should it have been testing for package libvirt-bin, rather than for libvirt? I got this: Waiting to hear from Launchpad about your decision... Package libvirt not installed and no hook available, ignoring brian@brian-desktop:~$ sudo aptitude show libvirt [sudo] password for brian: No current or candidate version found for libvirt Package: libvirt State: not a real package -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
Those were the files I uploaded the first time. In what way are they corrupt? I can display them from Launchpad. -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
They're definitely xml files, and are rendered as such when I click on the links to the files I've already uploaded. I'll copy-and-paste them here: server1.example.com: domain type='kvm' nameserver1.example.com/name uuidfb2d017b-f9cc-7534-126c-ffdd369c745f/uuid memory1048576/memory currentMemory1048576/currentMemory vcpu2/vcpu os type arch='x86_64' machine='pc-0.14'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/var/lib/libvirt/images/server1.example.com.img'/ target dev='vda' bus='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /disk interface type='network' mac address='52:54:00:38:a1:b7'/ source network='example.com'/ model type='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target type='serial' port='0'/ /console input type='tablet' bus='usb'/ input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' autoport='no'/ video model type='cirrus' vram='9216' heads='1'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /memballoon /devices /domain tester1.example.com: domain type='kvm' nametester1.example.com/name uuid66190ed3-0ce8-5d80-762f-684fef9d26d5/uuid memory1048576/memory currentMemory1048576/currentMemory vcpu2/vcpu os type arch='x86_64' machine='pc-0.14'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/var/lib/libvirt/images/tester1.example.com.img'/ target dev='vda' bus='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /disk interface type='network' mac address='52:54:00:2f:18:26'/ source network='example.com'/ model type='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target type='serial' port='0'/ /console input type='tablet' bus='usb'/ input type='mouse' bus='ps2'/ graphics type='vnc' port='5900' autoport='no'/ video model type='cirrus' vram='9216' heads='1'/ address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /video memballoon model='virtio' address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /memballoon /devices /domain -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
/var/log/libvirt/libvirtd.log does not exist. However, there are log files for each domain, in /var/log/libvirt/qemu which look to be handled by logrotate. server1.example.com.log and tester1.example.com.log are 0 length, so I am attaching server1.example.com.log.1 and tester1.example.com.log.1. ** Attachment added: server1.example.com.log.1 https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2428846/+files/server1.example.com.log.1 -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
** Attachment added: tester1.example.com.log.1 https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2428847/+files/tester1.example.com.log.1 -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
From a quick look at the logs, it looks like the domains I usually started second kept trying to bind to vnc on port 5900, which presumably was already claimed by the first domain. I only set the port during initial installation, so I'm not sure why it doesn't just try port 5901. -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] Re: Unable to start second virtual machine
That was it. Each domain xml file had this line: graphics type 'vnc' port='5900' autoport='no'/ using edit [domain name] in virsh, I changed the line in each to: graphics type='vnc' autoport='yes'/ With that, they both started without complaint. The remaining question is why the domains were configured that way to begin with. I'm not sure if it's a result of my having specified the port for vnc to use during installation, which I assumed was for installation only, or those are set as default in some other way. -- 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/853580 Title: Unable to start second virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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 853580] [NEW] Unable to start second virtual machine
Public bug reported:
Ubuntu 11.04
libvirt-bin 0.8.8-1ubuntu6.5
Whether using virt-manager or virsh, I am unable to start a second
virtual machine while one is already running.
Through virt-manager, I get this:
Error starting domain: operation failed: failed to retrieve chardev info
in qemu with 'info chardev'
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/asyncjob.py, line 45, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File /usr/share/virt-manager/virtManager/engine.py, line 956, in asyncfunc
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 1048, in startup
self._backend.create()
File /usr/lib/python2.7/dist-packages/libvirt.py, line 330, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: operation failed: failed to retrieve chardev info in qemu with
'info chardev'
Through virsh, I get this:
error: Failed to start domain tester1.example.com
error: operation failed: failed to retrieve chardev info in qemu with 'info
chardev'
** 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/853580
Title:
Unable to start second virtual machine
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+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
