Actions
Bug #39367
closedprint client IP in default debug_ms log level when "bad crc in {front|middle|data}" occurs
% Done:
0%
Source:
Tags:
Backport:
luminous,mimic,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
From https://bugzilla.redhat.com/show_bug.cgi?id=1696227
Ceph is checking the message from client in "Message *decode_message", there are few crc errors that can occur:
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.
Updated by Greg Farnum about 5 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 27658
Updated by Neha Ojha about 5 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #39463: luminous: print client IP in default debug_ms log level when "bad crc in {front|middle|data}" occurs added
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #39464: mimic: print client IP in default debug_ms log level when "bad crc in {front|middle|data}" occurs added
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #39465: nautilus: print client IP in default debug_ms log level when "bad crc in {front|middle|data}" occurs added
Updated by Nathan Cutler almost 5 years ago
- Status changed from Pending Backport to Resolved
Actions