A request for a quick clarification Atin.. The bind-insecure and allow-insecure seem to be turned on by default from 3.7.3 so if I install 3.7.13, then can I safely use samba/gfapi-vfs without modifying any parameters?
On Mon, Jul 25, 2016 at 9:53 AM, Atin Mukherjee <[email protected]> wrote: > This doesn't look like abnormal given you are running gluster 3.6.1 > version. In 3.6 "allow-insecure" option is turned off by default which > means glusterd will only entertain requests received on privileged ports > and this node has exhausted all the privileged ports by that time. If you > are willing to turn on bind-insecure option, then I do see this problem > going away. > > P.S : This option is been turned on by default in 3.7. > > ~Atin > > On Sun, Jul 24, 2016 at 8:51 PM, Atin Mukherjee <[email protected]> > wrote: > >> Will have a look at the logs tomorrow. >> >> >> On Sunday 24 July 2016, B.K.Raghuram <[email protected]> wrote: >> >>> Some issues seem to have cropped up at a remote location and I'm trying >>> to make sense of what the issues are. Could someone help in throwing some >>> light on the potential issues here? I notice that something happened at >>> 2016-07-20 06:33:09.621556 after which a host of issues are being reported >>> (around line 29655). After that there seem to be a host of communication >>> issues. >>> >>> Also does the line "0-rpc-service: Request received from non-privileged >>> port. Failing request" mean that potentially the samba access through the >>> gfapi vfs module was failed? >>> >> >> >> -- >> --Atin >> > > > > -- > > --Atin >
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
