Bug 1656517 - [GSS] Gluster client logs filling with 0-glusterfs-socket: invalid port messages
Summary: [GSS] Gluster client logs filling with 0-glusterfs-socket: invalid port messages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1656217
TreeView+ depends on / blocked
 
Reported: 2018-12-05 16:51 UTC by Milind Changire
Modified: 2019-03-25 16:32 UTC (History)
9 users (show)

Fixed In Version: glusterfs-6.0
Clone Of: 1656217
Environment:
Last Closed: 2019-03-25 16:32:33 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21809 0 None Merged core: move invalid port logs to DEBUG log level 2018-12-12 16:00:34 UTC

Comment 1 Worker Ant 2018-12-05 17:00:16 UTC 
REVIEW: https://review.gluster.org/21809 (core: move invalid port logs to DEBUG log level) posted (#1) for review on master by Milind Changire
Comment 2 Milind Changire 2018-12-05 17:01:12 UTC 
Problem:
[2018-11-26 20:08:55.501738] W [MSGID: 101082] [common-utils.c:3380:gf_ports_reserved] 0-glusterfs-socket: invalid port 8366

The above logs cause spamming if a large number of ports are reserved via
/proc/sys/net/ipv4/ip_local_reserved_ports
Comment 4 Worker Ant 2018-12-12 16:00:34 UTC 
REVIEW: https://review.gluster.org/21809 (core: move invalid port logs to DEBUG log level) posted (#4) for review on master by Amar Tumballi
Comment 5 Shyamsundar 2019-03-25 16:32:33 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.

glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/
Note You need to log in before you can comment on or make changes to this bug.