I see in libglusterfs/src/common-utils.c code that should cause gluster to observe values written to ip_local_reserved_ports (http://review.gluster.org/#/c/4131/)
Since the fuse client uses bind(), when you run it as root it will attempt to bind to a port in the standard range allocated to root, being < 1024. This follows convention. So, you’ve probably got two options here, either mount as non-root or provide ranges you want the client to exclude in ip_local_reserved_ports. -t > On Apr 9, 2016, at 11:43 AM, [email protected] wrote: > > Tom, this appears to be the same issue. I can’t seem to find any reported > bugs that relate directly to this issue, but others are having the same > problem. > > http://www.gluster.org/pipermail/gluster-users/2012-June/010380.html > > GlusterFS Clients does not appear to be properly using the > /proc/sys/net/ipv4/ip_local_port_range > > This issue has been incorrectly identified this issue with glusterfs not > properly using /proc/sys/net/ipv4/ip_local_reserved_ports > http://www.gluster.org/pipermail/gluster-users/2012-June/010383.html > > Referring to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=762989 > > But this is not the same. Glusterfs should leverage the ip_local_port_range, > and it’s not. > > I don’t want to have to register every port I’m using as reserved, I want to > just have glusterfs use ip_local_port_range properly. > > Ryan > > From: [email protected] [mailto:[email protected]] > Sent: Saturday, April 09, 2016 11:20 AM > To: Wyler, Ryan J. > Cc: [email protected] > Subject: Re: [Gluster-users] GlusterFS Mounts at startup consuming needed > local ports for host services > > Ryan, > > What's /proc/sys/net/ipv4/ip_local_port_range set to on the client? > > -t > > On Apr 9, 2016, at 8:00 AM, [email protected] wrote: > > Is there any way to configure glusterfs to avoid using specific local ports > when mounting filesystems? > > Ryan Wyler > > From: [email protected] > [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Friday, April 08, 2016 9:31 AM > To: [email protected] > Subject: [Gluster-users] GlusterFS Mounts at startup consuming needed local > ports for host services > > Glusterfs mounts are squashing ports I need available for services, > specifically on port 1002. > > How can I configure glusterfs mount points to avoid specific local ports for > the connections? > > A potential workaround I thought of is removing the mounts from starting > automatically at startup and create an rc.d startup script to mount the > glusterfs filesystems after all the host services have started to avoid those > ports. > > Is there a different option? > > The local port range is using 1000-1023 as seen in the information below for > client.domain.com. > > # lsof | grep glusterfs | grep IPv4 > glusterfs 2893 root 9u IPv4 15373 0t0 > TCP client.domain.com:1023->server1.domain.com:24007 (ESTABLISHED) > glusterfs 2893 root 10u IPv4 15447 0t0 > TCP client.domain.com:1015->server2.domain.com:49171 (ESTABLISHED) > glusterfs 2893 root 11u IPv4 15446 0t0 > TCP client.domain.com:1016->server3.domain.com:49171 (ESTABLISHED) > glusterfs 2893 root 13u IPv4 15422 0t0 > TCP client.domain.com:1020->server1.domain.com:49171 (ESTABLISHED) > glusterfs 2893 root 15u IPv4 15439 0t0 > TCP client.domain.com:1018->server4.domain.com:49171 (ESTABLISHED) > glusterfs 2998 root 9u IPv4 15523 0t0 > TCP client.domain.com:1014->server1.domain.com:24007 (ESTABLISHED) > glusterfs 2998 root 10u IPv4 15588 0t0 > TCP client.domain.com:1006->server2.domain.com:49157 (ESTABLISHED) > glusterfs 2998 root 11u IPv4 15576 0t0 > TCP client.domain.com:1007->server3.domain.com:49157 (ESTABLISHED) > glusterfs 2998 root 14u IPv4 15549 0t0 > TCP client.domain.com:1012->server1.domain.com:49157 (ESTABLISHED) > glusterfs 2998 root 16u IPv4 15569 0t0 > TCP client.domain.com:1009->server4.domain.com:49157 (ESTABLISHED) > glusterfs 46813 root 10u IPv4 342418 0t0 > TCP client.domain.com:1019->server1.domain.com:24007 (ESTABLISHED) > glusterfs 46813 root 11u IPv4 342445 0t0 > TCP client.domain.com:busboy->server2.domain.com:49152 (ESTABLISHED) > glusterfs 46813 root 15u IPv4 342428 0t0 > TCP client.domain.com:surf->server1.domain.com:49152 (ESTABLISHED) > glusterfs 46813 root 16u IPv4 342434 0t0 > TCP client.domain.com:1002->server4.domain.com:49152 (ESTABLISHED) > glusterfs 46813 root 17u IPv4 342440 0t0 > TCP client.domain.com:cadlock2->server3.domain.com:49152 (ESTABLISHED) > > > Glusterfs RPMs installed: > > glusterfs-libs-3.6.0.54-1 > glusterfs-api-3.6.0.54-1 > glusterfs-fuse-3.6.0.54-1 > glusterfs-3.6.0.54-1 > > > > Ryan Wyler > [email protected] > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
