Bug 764167 (GLUSTER-2435) - Not able to send error reply in rpcsvc.
Summary: Not able to send error reply in rpcsvc.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2435
Product: GlusterFS
Classification: Community
Component: transport
Version: 3.1.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gaurav
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 12:01 UTC by Gaurav
Modified: 2011-09-14 08:51 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: master

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Gaurav 2011-02-16 12:01:24 UTC 
[2011-02-16 08:28:35.453234] E [rpcsvc.c:874:rpcsvc_request_create] rpc-service: RPC call decoding failed
[2011-02-16 08:28:35.453247] D [rpcsvc.c:918:rpcsvc_request_create] rpcsvc: failed to queue error reply
[2011-02-16 08:28:35.453255] T [socket.c:1741:socket_event_handler] transport: disconnecting now


We are not initializing req->trans in case of decoding failure, so it failed to send reply. Same is the case with nfs, will open a seperate bug for that.
Comment 1 Anand Avati 2011-03-01 07:06:03 UTC 
PATCH: http://patches.gluster.com/patch/6292 in master (RPC : Sending error reply on decodong failure.)
Comment 2 Rahul C S 2011-09-14 05:51:05 UTC 
Code changes merged. Now, when decoding fails, doesnt disconnect.
Note You need to log in before you can comment on or make changes to this bug.