Bug 761872 (GLUSTER-140) - use appropriate loglevel to log in case of failure to bind to privileged socket
Summary: use appropriate loglevel to log in case of failure to bind to privileged socket
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-140
Product: GlusterFS
Classification: Community
Component: protocol
Version: 2.0.3
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-15 06:44 UTC by Raghavendra G
Modified: 2009-11-23 09:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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.)


Note You need to log in before you can comment on or make changes to this bug.