Bug 761872 (GLUSTER-140)

Summary: use appropriate loglevel to log in case of failure to bind to privileged socket
Product: [Community] GlusterFS Reporter: Raghavendra G <raghavendra>
Component: protocolAssignee: Raghavendra G <raghavendra>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 2.0.3CC: gluster-bugs, vinayak
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Raghavendra G 2009-07-15 06:44:01 UTC 
reported by Duc Le Minh <duclm.vn> on gluster-devel.

[2009-07-15 01:03:02] W [client-protocol.c:6010:init] unify_1: WARNING: Failed to set 'ulimit -n 1M': Operation not permitted
[2009-07-15 01:03:02] W [client-protocol.c:6010:init] unify_3: WARNING: Failed to set 'ulimit -n 1M': Operation not permitted
[2009-07-15 01:03:02] W [client-protocol.c:6010:init] unify_4: WARNING: Failed to set 'ulimit -n 1M': Operation not permitted
[2009-07-15 01:03:02] W [client-protocol.c:6010:init] unify_2: WARNING: Failed to set 'ulimit -n 1M': Operation not permitted
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_1: cannot bind inet socket (46) to port less than 1024 (Permission denied)
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_1: cannot bind inet socket (47) to port less than 1024 (Permission denied)
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_3: cannot bind inet socket (48) to port less than 1024 (Permission denied)
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_3: cannot bind inet socket (49) to port less than 1024 (Permission denied)
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_4: cannot bind inet socket (50) to port less than 1024 (Permission denied)
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_4: cannot bind inet socket (51) to port less than 1024 (Permission denied)
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_2: cannot bind inet socket (52) to port less than 1024 (Permission denied)
[2009-07-15 01:03:02] E [name.c:420:client_bind] unify_2: cannot bind inet socket (53) to port less than 1024 (Permission denied)
[2009-07-15 01:03:13] E [name.c:420:client_bind] unify_1: cannot bind inet socket (46) to port less than 1024 (Permission denied)
[2009-07-15 01:03:13] E [name.c:420:client_bind] unify_1: cannot bind inet socket (46) to port less than 1024 (Permission denied)
[2009-07-15 01:03:13] E [name.c:420:client_bind] unify_3: cannot bind inet socket (46) to port less than 1024 (Permission denied)
[2009-07-15 01:03:13] E [name.c:420:client_bind] unify_3: cannot bind inet socket (46) to port less than 1024 (Permission denied)
[2009-07-15 01:03:13] E [name.c:420:client_bind] unify_4: cannot bind inet socket (46) to port less than 1024 (Permission denied)
[2009-07-15 01:03:13] E [name.c:420:client_bind] unify_2: cannot bind inet socket (46) to port less than 1024 (Permission denied)

Not able to bind to privileged socket is not an error condition. Applications like lighttpd can bind to non-privileged socket and use login based authentication and continue normally.
Comment 1 Raghavendra G 2009-07-30 10:36:24 UTC 
A patch has been submitted for review at
http://patches.gluster.com/patch/837/
Comment 2 Anand Avati 2009-07-31 17:11:35 UTC 
PATCH: http://patches.gluster.com/patch/842 in master (client-protocol: log messages at WARNING loglevel when client_bind on privileged port fails.)