On 06/13/2014 03:23 PM, Ivano Talamo wrote:
On 6/12/14 7:58 PM, Vijay Bellur wrote:
Btw, I have problems starting the VM. the "virsh start <vm-name>"
command remains waiting forever on a futex call.
The xml relevant section is:
<disk type='network' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source protocol='gluster'
name='vol1/vms/disks/cmsrm-ui01.qcow2'>
<host name='141.108.36.19' port='24007'/>
</source>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
</disk>
Do you happen to notice any errors in the glusterd and glusterfsd logs?
I see this in vol1.log and glusterhd.log files:
[2014-06-13 09:44:11.247944] I [rpc-clnt.c:1685:rpc_clnt_reconfig]
0-vol1-client-0: changing port to 49152 (from 0)
[2014-06-13 09:44:11.252518] E [socket.c:2161:socket_connect_finish]
0-vol1-client-0: connection to 141.108.36.19:49152 failed (Connection
refused)
but they appear always, not only when trying the virsh start. Should I
worry about these?
Looks like clients are not able to connect to port 49152. Can you please
check if "gluster volume status" lists all processes as online and that
there are no firewall rules blocking packets to 49152 on this node?
-Vijay
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
