Re: Gluster 3.5 problems with libgfapi/qemu

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/13/14 11:56 AM, Vijay Bellur wrote:

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

Hi,
for some reason Brick cmsrm-service02:/brick/vol1 was not started. I did a glusterfsd start on cmsrm-service02 and these error messages stopped.

Thanks,
Ivano

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux