Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name v-2-VM -S -M rhel6.5.0 -enable-kvm -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid e36968ea-2ef2-4046-a1a8-59947e929d08 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/v-2-VM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/8964d2eb-e9c8-3d55-b0b7-30c20078cf5e/779f4f62-0853-4a4c-9579-73097a6f635b,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:00:10,bus=pci.0,addr=0x3 -netdev tap,fd=31,id=hostnet1,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=06:d8:dc:00:00:03,bus=pci.0,addr=0x4 -netdev tap,fd=33,id=hostnet2,vhost=on,vhostfd=34 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:6f:e8:00:00:75,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/v-2-VM.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=v-2-VM.vport -device usb-tablet,id=input0 -vnc 192.168.0.2:1,password -vga cirrus Domain id=4 is tainted: high-privileges char device redirected to /dev/pts/2 On Mon, Apr 21, 2014 at 4:24 AM, Giri Prasad wrote: > > > Thanks for the comment. The details are as: > > virsh -c qemu+tcp://192.XXX.XX.X/system > Welcome to virsh, the virtualization interactive terminal. > > Type: 'help' for help with commands >'quit' to quit > > virsh # list --all > IdName State > > 1 v-1-VM running > 2 s-185-VM running > > virsh # exit > > > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl-n > v-1-VM -p > %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 > . > ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - > Connection refused > > > /var/log/libvirt/qemu/v-1-VM.log > > 2014-04-21 07:43:50.503+: starting up > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none > /usr/libexec/qemu-kvm -name v-1-VM -S -M rhel6.5.0 -enable-kvm -m 1024 > -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid > 50cc182f-f4d3-4658-bdd0-ecfc688711d9 -nodefconfig -nodefaults -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/v-1-VM.monitor,server,nowait > -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown > -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive > file=/mnt/b30c0f37-8876-3003-a552-61bcce73ea4c/6733480c-13f6-4967-98ad-79503a98c376,if=none,id=drive-virtio-disk0,format=qcow2,cache=none > -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 > -drive > file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none > -device > ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 > -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device > virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:01:ae,bus=pci.0,addr=0x3 > -netdev tap,fd=28,id=hostnet1,vhost=on,vhostfd=29 -device > virtio-net-pci,netdev=hostnet1,id=net1,mac=06:3a:4c:00:00:01,bus=pci.0,addr=0x4 > -netdev tap,fd=30,id=hostnet2,vhost=on,vhostfd=31 -device > virtio-net-pci,netdev=hostnet2,id=net2,mac=06:6f:ac:00:00:0e,bus=pci.0,addr=0x5 > -chardev pty,id=charserial0 -device > isa-serial,chardev=charserial0,id=serial0 -chardev > socket,id=charchannel0,path=/var/lib/libvirt/qemu/v-1-VM.agent,server,nowait > -device > virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=v-1-VM.vport > -device usb-tablet,id=input0 -vnc 192.XXX.XX.5:0,password -vga cirrus > Domain id=1 is tainted: high-privileges > char device redi
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
Thanks for the comment. The details are as: virsh -c qemu+tcp://192.XXX.XX.X/system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # list --all Id Name State 1 v-1-VM running 2 s-185-VM running virsh # exit /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n v-1-VM -p %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 . ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - Connection refused /var/log/libvirt/qemu/v-1-VM.log 2014-04-21 07:43:50.503+: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name v-1-VM -S -M rhel6.5.0 -enable-kvm -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 50cc182f-f4d3-4658-bdd0-ecfc688711d9 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/v-1-VM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/b30c0f37-8876-3003-a552-61bcce73ea4c/6733480c-13f6-4967-98ad-79503a98c376,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:01:ae,bus=pci.0,addr=0x3 -netdev tap,fd=28,id=hostnet1,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=06:3a:4c:00:00:01,bus=pci.0,addr=0x4 -netdev tap,fd=30,id=hostnet2,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:6f:ac:00:00:0e,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/v-1-VM.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=v-1-VM.vport -device usb-tablet,id=input0 -vnc 192.XXX.XX.5:0,password -vga cirrus Domain id=1 is tainted: high-privileges char device redirected to /dev/pts/2 qemu: terminating on signal 15 from pid 2893 2014-04-21 08:02:12.453+: shutting down 2014-04-21 08:02:18.195+: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name v-1-VM -S -M rhel6.5.0 -enable-kvm -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 50cc182f-f4d3-4658-bdd0-ecfc688711d9 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/v-1-VM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/b30c0f37-8876-3003-a552-61bcce73ea4c/6733480c-13f6-4967-98ad-79503a98c376,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/usr/share/cloudstack-common/vms/systemvm.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=0e:00:a9:fe:02:a1,bus=pci.0,addr=0x3 -netdev tap,fd=28,id=hostnet1,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=06:bb:aa:00:00:01,bus=pci.0,addr=0x4 -netdev tap,fd=30,id=hostnet2,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet2,id=net2,mac=06:6f:ac:00:00:0e,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/v-1-VM.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=v-1-VM.vport -device usb-tablet,id=input0 -vnc 192.XXX.XX.5:0,password -vga cirrus Domain id=3 is tainted: high-privileges char device redirected to /dev/pts/2 /var/log/libvirt/qemu/s-185-VM.log Domain id=10 is tainted: high-privileges char devic
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
Sorry, actually I see the 'connection refused' is just your own test after the fact. By that time the vm may be shut down, so connection refused would make sense. What happens if you do this: 'virsh dumpxml v-1-VM > /tmp/v-1-VM.xml' while it is running stop the cloudstack agent 'virsh destroy v-1-VM' 'virsh create /tmp/v-1-VM.xml' Then try connecting to that VM via VNC to watch it boot up, or running that command manually, repeatedly? Does it time out? In the end this may not mean much, because in CentOS 6.x that command is retried over and over while the system vm is coming up anyway (in other words, some failures are expected). It could be related, but it could also be that the system vm is failing to come up for any other reason, and this is just the thing you noticed. On Sun, Apr 20, 2014 at 11:25 PM, Marcus wrote: > You may want to look in the qemu log of the vm to see if there's > something deeper going on, perhaps the qemu process is not fully > starting due to some other issue. /var/log/libvirt/qemu/v-1-VM.log, or > something like that. > > On Sun, Apr 20, 2014 at 11:22 PM, Marcus wrote: >> No, it has nothing to do with ssh or libvirt daemon. It's the literal >> unix socket that is created for virtio-serial communication when the >> qemu process starts. The question is why the system is refusing access >> to the socket. I assume this is being attempted as root. >> >> On Sat, Apr 19, 2014 at 9:58 AM, Nux! wrote: >>> On 19.04.2014 15:24, Giri Prasad wrote: >>> >>>> >>>> # grep listen_ /etc/libvirt/libvirtd.conf >>>> listen_tls=0 >>>> listen_tcp=1 >>>> #listen_addr = "192.XX.XX.X" >>>> listen_addr = "0.0.0.0" >>>> >>>> # >>>> /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl >>>> -n v-1-VM -p >>>> >>>> %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 >>>> . >>>> ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - >>>> Connection refused >>> >>> >>> Do you have "-l" or "--listen" as LIBVIRTD_ARGS in /etc/sysconfig/libvirtd? >>> >>> (kind of stabbing in the dark) >>> >>> >>> -- >>> Sent from the Delta quadrant using Borg technology! >>> >>> Nux! >>> www.nux.ro
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
You may want to look in the qemu log of the vm to see if there's something deeper going on, perhaps the qemu process is not fully starting due to some other issue. /var/log/libvirt/qemu/v-1-VM.log, or something like that. On Sun, Apr 20, 2014 at 11:22 PM, Marcus wrote: > No, it has nothing to do with ssh or libvirt daemon. It's the literal > unix socket that is created for virtio-serial communication when the > qemu process starts. The question is why the system is refusing access > to the socket. I assume this is being attempted as root. > > On Sat, Apr 19, 2014 at 9:58 AM, Nux! wrote: >> On 19.04.2014 15:24, Giri Prasad wrote: >> >>> >>> # grep listen_ /etc/libvirt/libvirtd.conf >>> listen_tls=0 >>> listen_tcp=1 >>> #listen_addr = "192.XX.XX.X" >>> listen_addr = "0.0.0.0" >>> >>> # >>> /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl >>> -n v-1-VM -p >>> >>> %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 >>> . >>> ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - >>> Connection refused >> >> >> Do you have "-l" or "--listen" as LIBVIRTD_ARGS in /etc/sysconfig/libvirtd? >> >> (kind of stabbing in the dark) >> >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
No, it has nothing to do with ssh or libvirt daemon. It's the literal unix socket that is created for virtio-serial communication when the qemu process starts. The question is why the system is refusing access to the socket. I assume this is being attempted as root. On Sat, Apr 19, 2014 at 9:58 AM, Nux! wrote: > On 19.04.2014 15:24, Giri Prasad wrote: > >> >> # grep listen_ /etc/libvirt/libvirtd.conf >> listen_tls=0 >> listen_tcp=1 >> #listen_addr = "192.XX.XX.X" >> listen_addr = "0.0.0.0" >> >> # >> /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl >> -n v-1-VM -p >> >> %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 >> . >> ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - >> Connection refused > > > Do you have "-l" or "--listen" as LIBVIRTD_ARGS in /etc/sysconfig/libvirtd? > > (kind of stabbing in the dark) > > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
On 19.04.2014 15:24, Giri Prasad wrote: # grep listen_ /etc/libvirt/libvirtd.conf listen_tls=0 listen_tcp=1 #listen_addr = "192.XX.XX.X" listen_addr = "0.0.0.0" # /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n v-1-VM -p %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 . ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - Connection refused Do you have "-l" or "--listen" as LIBVIRTD_ARGS in /etc/sysconfig/libvirtd? (kind of stabbing in the dark) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
>>> I am trying to trying to setup cloudstack 4.3 on centos 6.5. After > >>> all the installation steps are over, and upon pressing the >>> button in the cloudstack gui, the following error comes out >>> repeatedly. Any comments as to why is this happening? > >> Hi, > >> Is Selinux off or in permissive mode? > >> Also, what does "virsh dumpxml v-1-VM | grep agent" say? > > Hi, > > Thanks for your comment. > > virsh dumpxml v-1-VM | grep agent > > SELINUX=permissive >One thing that caught me by surprise - though the error does not >indicate anything like this - is missing openssh-clients package >installed. Can you make sure you have that installed? # rpm -qa | grep openssh openssh-clients-5.3p1-94.el6.x86_64 openssh-5.3p1-94.el6.x86_64 openssh-askpass-5.3p1-94.el6.x86_64 openssh-server-5.3p1-94.el6.x86_64 # grep listen_ /etc/libvirt/libvirtd.conf listen_tls=0 listen_tcp=1 #listen_addr = "192.XX.XX.X" listen_addr = "0.0.0.0" # /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n v-1-VM -p %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 . ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - Connection refused
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
On 19.04.2014 14:40, Giri Prasad wrote: I am trying to trying to setup cloudstack 4.3 on centos 6.5. After all the installation steps are over, and upon pressing the button in the cloudstack gui, the following error comes out repeatedly. Any comments as to why is this happening? Hi, Is Selinux off or in permissive mode? Also, what does "virsh dumpxml v-1-VM | grep agent" say? Hi, Thanks for your comment. virsh dumpxml v-1-VM | grep agent SELINUX=permissive One thing that caught me by surprise - though the error does not indicate anything like this - is missing openssh-clients package installed. Can you make sure you have that installed? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
>> I am trying to trying to setup cloudstack 4.3 on centos 6.5. After >> all the installation steps are over, and upon pressing the >> button in the cloudstack gui, the following error comes out >> repeatedly. Any comments as to why is this happening? > Hi, > Is Selinux off or in permissive mode? > Also, what does "virsh dumpxml v-1-VM | grep agent" say? Hi, Thanks for your comment. virsh dumpxml v-1-VM | grep agent SELINUX=permissive
Re: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
On 19.04.2014 13:12, Giri Prasad wrote: Hello All, I am trying to trying to setup cloudstack 4.3 on centos 6.5. After all the installation steps are over, and upon pressing the button in the cloudstack gui, the following error comes out repeatedly. Any comments as to why is this happening? Hi, Is Selinux off or in permissive mode? Also, what does "virsh dumpxml v-1-VM | grep agent" say? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent
] (Cluster-Heartbeat-1:ctx-bcbccc64) Trying to connect to 192.XXX.XX.X 2014-04-19 14:48:07,933 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-bcbccc64) Management node 2 is detected inactive by timestamp but is pingable 2014-04-19 14:48:09,435 DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-45236a49) Detected management node left, id:2, nodeIP:192.XXX.XX.X 2014-04-19 14:48:09,435 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-45236a49) Trying to connect to 192.XXX.XX.X 2014-04-19 14:48:09,436 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-45236a49) Management node 2 is detected inactive by timestamp but is pingable 2014-04-19 14:48:09,729 DEBUG [c.c.a.ApiServlet] (catalina-exec-1:ctx-5750245e) ===START=== 192.XXX.XX.X -- GET command=listSystemVms&response=json&sessionkey=o4rxuG%2BgVnMwrfFXkNjHfnaNGe4%3D&_=1397899089726 2014-04-19 14:48:09,898 DEBUG [c.c.a.ApiServlet] (catalina-exec-1:ctx-5750245e ctx-6bcad27e) ===END=== 192.XXX.XX.X -- GET command=listSystemVms&response=json&sessionkey=o4rxuG%2BgVnMwrfFXkNjHfnaNGe4%3D&_=1397899089726 2014-04-19 14:48:10,920 DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-c76d5680) Detected management node left, id:2, nodeIP:192.XXX.XX.X 2014-04-19 14:48:10,920 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-c76d5680) Trying to connect to 192.XXX.XX.X 2014-04-19 14:48:10,920 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-c76d5680) Management node 2 is detected inactive by timestamp but is pingable 2014-04-19 14:48:11,363 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-b3be8305) Resetting hosts suitable for reconnect 2014-04-19 14:48:11,365 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-b3be8305) Completed resetting hosts suitable for reconnect 2014-04-19 14:48:11,366 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-b3be8305) Acquiring hosts for clusters already owned by this management server 2014-04-19 14:48:11,366 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-b3be8305) Completed acquiring hosts for clusters already owned by this management server 2014-04-19 14:48:11,367 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-b3be8305) Acquiring hosts for clusters not owned by any management server 2014-04-19 14:48:11,367 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-b3be8305) Completed acquiring hosts for clusters not owned by any management server 2014-04-19 14:48:12,448 DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-a25c3541) Detected management node left, id:2, nodeIP:192.XXX.XX.X 2014-04-19 14:48:12,449 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-a25c3541) Trying to connect to 192.XXX.XX.X 2014-04-19 14:48:12,449 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-a25c3541) Management node 2 is detected inactive by timestamp but is pingable 2014-04-19 14:48:13,931 DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-7cdc85ae) Detected management node left, id:2, nodeIP:192.XXX.XX.X 2014-04-19 14:48:13,931 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-7cdc85ae) Trying to connect to 192.XXX.XX.X 2014-04-19 14:48:13,931 INFO [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-7cdc85ae) Management node 2 is detected inactive by timestamp but is pingable 2014-04-19 14:48:14,728 DEBUG [c.c.a.ApiServlet] (catalina-exec-10:ctx-5e99529e) ===START=== 192.XXX.XX.X -- GET command=listSystemVms&response=json&sessionkey=o4rxuG%2BgVnMwrfFXkNjHfnaNGe4%3D&_=1397899094725 2014-04-19 14:48:14,895 DEBUG [c.c.a.ApiServlet] (catalina-exec-10:ctx-5e99529e ctx-3d105d7f) ===END=== 192.XXX.XX.X -- GET command=listSystemVms&response=json&sessionkey=o4rxuG%2BgVnMwrfFXkNjHfnaNGe4%3D&_=1397899094725 2014-04-19 14:48:15,432 DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-76b37f47) Detected management node left, id:2, nodeIP:192.XXX.XX.X # /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n v-1-VM -p %template=domP%type=consoleproxy%host=192.XXX.XX.5%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.XXX.XX.173%eth2mask=255.255.255.0%gateway=192.XXX.XX.1%eth0ip=169.254.0.173%eth0mask=255.255.0.0%eth1ip=192.XXX.XX.166%eth1mask=255.255.255.0%mgmtcidr=192.XXX.XX.0/24%localgw=192.XXX.XX.1%internaldns1=192.XXX.XX.1%dns1=192.XXX.XX.1 . ERROR: unable to connect to /var/lib/libvirt/qemu/v-1-VM.agent - Connection refused # virsh list --all Id Name State 15 v-1-VM running 16 s-5-VM running /etc/libvirt/libvirtd.conf listen_tls=0 listen_tcp=1
