Bug 1696227

Summary:	[RFE] print client IP in default debug_ms log level when "bad crc in {front\|middle\|data}" occurs
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Tomas Petr <tpetr>
Component:	RADOS	Assignee:	Greg Farnum <gfarnum>
Status:	CLOSED ERRATA	QA Contact:	Manohar Murthy <mmurthy>
Severity:	low	Docs Contact:	Aron Gunn <agunn>
Priority:	low
Version:	3.2	CC:	agunn, ceph-eng-bugs, ceph-qe-bugs, dzafman, gfarnum, jdurgin, kchai, nojha, tchandra, tserlin, vumrao
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-16.el7cp Ubuntu: ceph_12.2.12-15redhat1xenial	Doc Type:	Enhancement
Doc Text:	.Updated the Ceph debug log to include the source IP address on failed incoming CRC messages Previously, when a failed incoming Cyclic Redundancy Check (CRC) message was getting logged into the Ceph debug log, only a warning about the failed incoming CRC message was logged. With this release, the source IP address is added to this warning message. This helps system administrators identify which clients and daemons might have some networking issues.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-21 15:10:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1726135

Description Tomas Petr 2019-04-04 11:28:00 UTC

Description of problem:
Ceph is checking the message from client in "Message *decode_message", there are few crc errors that can occur:
https://github.com/ceph/ceph/blob/v12.2.8/src/msg/Message.cc#L281
https://github.com/ceph/ceph/blob/master/src/msg/Message.cc#L288

From the default ceph-osd  log level of debug_ms we are not able to see which client has sent such message.
To get the client IP debug_ms=20 is needed.

It would speed up tracking the client, if the client IP would be printed with the "bad crc in {front|middle|data}"  error message in default log level.
Especially when the "bad crc in {front|middle|data}" can happen randomly.

Version-Release number of selected component (if applicable):
RHCS 2.x
RHCS 3.x

Comment 8 errata-xmlrpc 2019-08-21 15:10:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2538