Unfortunately, I don't know of a good place to point you for documentation.
glusterfs keeps files under /var/lib/glusterfs and I have had problems in the past where /var/log/glusterfs will fill up /var and then some files under /var/lib/glusterfs would be missing or empty and cause glusterfsd not to start. Unfortunately, I don't think it has ever been exactly the same thing twice but I have been able to reconstruct the missing/empty files using from the other gluster servers and get gluster to start.
I'm certainly no expert... I just seemed to recall seeing the no-privileged port issue come up before and solving it with the volume setting.
On Fri, Jan 31, 2014 at 10:39 AM, Hariharan Thantry <thantry@xxxxxxxxx> wrote:
Thanks Mark.I also see random issues with not being able to start my gluster daemon, or the gluster daemon "dying" mysteriously. I have a feeling that it might have been because of an incorrect cluster shutdown. Are there any docs on the different files that glusterd cares about, or looks for, and mechanisms to get rid of "stale" state?Thanks,HariOn Fri, Jan 31, 2014 at 11:28 AM, Mark Morlino <mark@xxxxxxxxxxxxxxx> wrote:
I think setting nfs.ports-insecure on the volume will resolve this.On Fri, Jan 31, 2014 at 9:53 AM, Hariharan Thantry <thantry@xxxxxxxxx> wrote:
_______________________________________________Hi,
I have random errors sometimes when I try to peer probe a host on my gluster cluster."Connection failed. Please check if gluster daemon is operational"When looking at the logs on the machine initiating the probe and the remote machine, I see the following errorE [rpcsvc.c:521:rpcsvc_handle_rpc_call] 0-glusterd: Request recieved from non-privileged port. Failing requestWhy would this happen?Thanks,Hari
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
