[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

I keep getting this bug in a random manner. Some times after a restart, the 2 services start properly and other times I have to manually start them. -- eucalyptus-cc and uec-component-listener services are not started https://bugs.launchpad.net/bugs/598182 You received this bug notification

[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

I keep getting this bug in a random manner. Some times after a restart, the 2 services start properly and other times I have to manually start them. -- eucalyptus-cc and uec-component-listener services are not started https://bugs.launchpad.net/bugs/598182 You received this bug notification

[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

Thierry, I installed using the PackageInstall instructions. -- eucalyptus-cc and uec-component-listener services are not started https://bugs.launchpad.net/bugs/598182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu.

[Bug 598186] Re: Unable to register nodes in eucalyptus

@Thiery, I used PackageInstall procedure. -- Unable to register nodes in eucalyptus https://bugs.launchpad.net/bugs/598186 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list

[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

Dave, after a clean reinstall, one time I was able to reboot and raise the bug. But after I rebooted again, the services started up normally on each reboot. I will try to keep an eye out for it. -- eucalyptus-cc and uec-component-listener services are not started

[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

Thierry, I installed using the PackageInstall instructions. -- eucalyptus-cc and uec-component-listener services are not started https://bugs.launchpad.net/bugs/598182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 598186] Re: Unable to register nodes in eucalyptus

@Thiery, I used PackageInstall procedure. -- Unable to register nodes in eucalyptus https://bugs.launchpad.net/bugs/598186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

Dave, after a clean reinstall, one time I was able to reboot and raise the bug. But after I rebooted again, the services started up normally on each reboot. I will try to keep an eye out for it. -- eucalyptus-cc and uec-component-listener services are not started

[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

Yes, I'm able to see it with euca-describe-availability-zones: $ euca-describe-availability-zones verbose AVAILABILITYZONEqa-cluster 10.0.10.6 AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small / 1512 5

[Bug 598182] Re: eucalyptus-cc and uec-component-listener services are not started

Yes, I'm able to see it with euca-describe-availability-zones: $ euca-describe-availability-zones verbose AVAILABILITYZONEqa-cluster 10.0.10.6 AVAILABILITYZONE|- vm types free / max cpu ram disk AVAILABILITYZONE|- m1.small / 1512 5

[Bug 585964] [NEW] Libvirtd -- error: monitor socket did not show up.: Connection refused

Public bug reported: Background on this issue: http://open.eucalyptus.com/forum/libvirt- operation-failed-failed-retrieve-chardev-info-qemu-info-chardev Whenever I try to run VM instance using virsh, I get this error: error: monitor socket did not show up.: Connection refused Error is always

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: /etc/libvirt/libvirtd.conf http://launchpadlibrarian.net/49150961/etc_libvirt_libvirtd.conf -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: /etc/libvirt/qemu.conf http://launchpadlibrarian.net/49151007/etc_libvirt_qemu.conf -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: Installed Packages http://launchpadlibrarian.net/49151047/installed_packages.txt -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: libvirt.xml http://launchpadlibrarian.net/49151051/libvirt.xml -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: Strace of libvirtd http://launchpadlibrarian.net/49151071/strace.txt -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: virsh debug logs http://launchpadlibrarian.net/49151161/virsh_debug_logs.txt -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu Server

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

I was able to reproduce this issue again for the 3rd time on a clean install. I believe that anybody can reproduce this with the following steps: STEP 1: Do a clean Ubuntu Server 10.04 installation. When I installed, I selected OpenSSH server as the only additional installation package. STEP 2:

[Bug 585964] [NEW] Libvirtd -- error: monitor socket did not show up.: Connection refused

Public bug reported: Background on this issue: http://open.eucalyptus.com/forum/libvirt- operation-failed-failed-retrieve-chardev-info-qemu-info-chardev Whenever I try to run VM instance using virsh, I get this error: error: monitor socket did not show up.: Connection refused Error is always

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: /etc/libvirt/libvirtd.conf http://launchpadlibrarian.net/49150961/etc_libvirt_libvirtd.conf -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: /etc/libvirt/qemu.conf http://launchpadlibrarian.net/49151007/etc_libvirt_qemu.conf -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: Installed Packages http://launchpadlibrarian.net/49151047/installed_packages.txt -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: libvirt.xml http://launchpadlibrarian.net/49151051/libvirt.xml -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: Strace of libvirtd http://launchpadlibrarian.net/49151071/strace.txt -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

** Attachment added: virsh debug logs http://launchpadlibrarian.net/49151161/virsh_debug_logs.txt -- Libvirtd -- error: monitor socket did not show up.: Connection refused https://bugs.launchpad.net/bugs/585964 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

I was able to reproduce this issue again for the 3rd time on a clean install. I believe that anybody can reproduce this with the following steps: STEP 1: Do a clean Ubuntu Server 10.04 installation. When I installed, I selected OpenSSH server as the only additional installation package. STEP 2: