Hyperledger fabric Error: 14 UNAVAILABLE: TCP Write failed
0
When chaincode container remains idle for some time then it stops with error:
ERROR [lib/handler.js] Chat stream with peer - on error: "Error: 14 UNAVAILABLE: EOFn at createStatusError (/usr/local/src/node_modules/grpc/src/client.js:64:15)n at ClientDuplexStream._emitStatusIfDone (/usr/local/src/node_modules/grpc/src/client.js:270:19)n at ClientDuplexStream._receiveStatus (/usr/local/src/node_modules/grpc/src/client.js:248:8)n at /usr/local/src/node_modules/grpc/src/client.js:804:12"
And when the first request comes after idle time it gives an error of
Error: 14 UNAVAILABLE: TCP Write failed
After that for second request error changes to following:
Error: SERVICE_UNAVAILABLE
at ClientDuplexStream.broadcast.on (/app/node_modules/fabric-client/lib/Orderer.js:172:22)
at emitOne (events.js:116:13)
at ClientDuplexStream.emit (events.js:211:7)
at ClientDuplexStream._emitStatusIfDone (/app/node_modules/grpc/src/client.js:236:12)
at ClientDuplexStream._receiveStatus (/app/node_modules/grpc/src/client.js:213:8)
at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1290:15)
at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:564:42)
at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:614:8)
at /app/node_modules/grpc/src/client_interceptors.js:1110:18
From third request onwards all works fine.
I was using fabric-shim 1.2.0 but after upgrading it to 1.3.0 the error appears randomly.
I am using fabric 1.3.0.
hyperledger-fabric hyperledger hyperledger-fabric-sdk-js
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
add a comment |
0
When chaincode container remains idle for some time then it stops with error:
ERROR [lib/handler.js] Chat stream with peer - on error: "Error: 14 UNAVAILABLE: EOFn at createStatusError (/usr/local/src/node_modules/grpc/src/client.js:64:15)n at ClientDuplexStream._emitStatusIfDone (/usr/local/src/node_modules/grpc/src/client.js:270:19)n at ClientDuplexStream._receiveStatus (/usr/local/src/node_modules/grpc/src/client.js:248:8)n at /usr/local/src/node_modules/grpc/src/client.js:804:12"
And when the first request comes after idle time it gives an error of
Error: 14 UNAVAILABLE: TCP Write failed
After that for second request error changes to following:
Error: SERVICE_UNAVAILABLE
at ClientDuplexStream.broadcast.on (/app/node_modules/fabric-client/lib/Orderer.js:172:22)
at emitOne (events.js:116:13)
at ClientDuplexStream.emit (events.js:211:7)
at ClientDuplexStream._emitStatusIfDone (/app/node_modules/grpc/src/client.js:236:12)
at ClientDuplexStream._receiveStatus (/app/node_modules/grpc/src/client.js:213:8)
at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1290:15)
at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:564:42)
at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:614:8)
at /app/node_modules/grpc/src/client_interceptors.js:1110:18
From third request onwards all works fine.
I was using fabric-shim 1.2.0 but after upgrading it to 1.3.0 the error appears randomly.
I am using fabric 1.3.0.
hyperledger-fabric hyperledger hyperledger-fabric-sdk-js
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
For fabric 1.3, try using fabric-shim 1.3.1 or higher version of 1.3 (if available)
– david_k
Nov 23 '18 at 11:34
Okay. I will try by that but is it okay to use fabric-shim 1.3.1 with fabric 1.3.0?
– Honey Shah
Nov 23 '18 at 11:55
Yes, its fine to use that version
– david_k
Nov 23 '18 at 13:20
I tried by using fabric-shim 1.3.1 but the error is still persist
– Honey Shah
Nov 24 '18 at 9:12
add a comment |
0
0
0
When chaincode container remains idle for some time then it stops with error:
ERROR [lib/handler.js] Chat stream with peer - on error: "Error: 14 UNAVAILABLE: EOFn at createStatusError (/usr/local/src/node_modules/grpc/src/client.js:64:15)n at ClientDuplexStream._emitStatusIfDone (/usr/local/src/node_modules/grpc/src/client.js:270:19)n at ClientDuplexStream._receiveStatus (/usr/local/src/node_modules/grpc/src/client.js:248:8)n at /usr/local/src/node_modules/grpc/src/client.js:804:12"
And when the first request comes after idle time it gives an error of
Error: 14 UNAVAILABLE: TCP Write failed
After that for second request error changes to following:
Error: SERVICE_UNAVAILABLE
at ClientDuplexStream.broadcast.on (/app/node_modules/fabric-client/lib/Orderer.js:172:22)
at emitOne (events.js:116:13)
at ClientDuplexStream.emit (events.js:211:7)
at ClientDuplexStream._emitStatusIfDone (/app/node_modules/grpc/src/client.js:236:12)
at ClientDuplexStream._receiveStatus (/app/node_modules/grpc/src/client.js:213:8)
at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1290:15)
at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:564:42)
at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:614:8)
at /app/node_modules/grpc/src/client_interceptors.js:1110:18
From third request onwards all works fine.
I was using fabric-shim 1.2.0 but after upgrading it to 1.3.0 the error appears randomly.
I am using fabric 1.3.0.
hyperledger-fabric hyperledger hyperledger-fabric-sdk-js
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
When chaincode container remains idle for some time then it stops with error:
ERROR [lib/handler.js] Chat stream with peer - on error: "Error: 14 UNAVAILABLE: EOFn at createStatusError (/usr/local/src/node_modules/grpc/src/client.js:64:15)n at ClientDuplexStream._emitStatusIfDone (/usr/local/src/node_modules/grpc/src/client.js:270:19)n at ClientDuplexStream._receiveStatus (/usr/local/src/node_modules/grpc/src/client.js:248:8)n at /usr/local/src/node_modules/grpc/src/client.js:804:12"
And when the first request comes after idle time it gives an error of
Error: 14 UNAVAILABLE: TCP Write failed
After that for second request error changes to following:
Error: SERVICE_UNAVAILABLE
at ClientDuplexStream.broadcast.on (/app/node_modules/fabric-client/lib/Orderer.js:172:22)
at emitOne (events.js:116:13)
at ClientDuplexStream.emit (events.js:211:7)
at ClientDuplexStream._emitStatusIfDone (/app/node_modules/grpc/src/client.js:236:12)
at ClientDuplexStream._receiveStatus (/app/node_modules/grpc/src/client.js:213:8)
at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1290:15)
at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:564:42)
at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:614:8)
at /app/node_modules/grpc/src/client_interceptors.js:1110:18
From third request onwards all works fine.
I was using fabric-shim 1.2.0 but after upgrading it to 1.3.0 the error appears randomly.
I am using fabric 1.3.0.
hyperledger-fabric hyperledger hyperledger-fabric-sdk-js
hyperledger-fabric hyperledger hyperledger-fabric-sdk-js
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
asked Nov 23 '18 at 10:58
Honey ShahHoney Shah
3169
3169
For fabric 1.3, try using fabric-shim 1.3.1 or higher version of 1.3 (if available)
– david_k
Nov 23 '18 at 11:34
Okay. I will try by that but is it okay to use fabric-shim 1.3.1 with fabric 1.3.0?
– Honey Shah
Nov 23 '18 at 11:55
Yes, its fine to use that version
– david_k
Nov 23 '18 at 13:20
I tried by using fabric-shim 1.3.1 but the error is still persist
– Honey Shah
Nov 24 '18 at 9:12
add a comment |
For fabric 1.3, try using fabric-shim 1.3.1 or higher version of 1.3 (if available)
– david_k
Nov 23 '18 at 11:34
Okay. I will try by that but is it okay to use fabric-shim 1.3.1 with fabric 1.3.0?
– Honey Shah
Nov 23 '18 at 11:55
Yes, its fine to use that version
– david_k
Nov 23 '18 at 13:20
I tried by using fabric-shim 1.3.1 but the error is still persist
– Honey Shah
Nov 24 '18 at 9:12
For fabric 1.3, try using fabric-shim 1.3.1 or higher version of 1.3 (if available)
– david_k
Nov 23 '18 at 11:34
For fabric 1.3, try using fabric-shim 1.3.1 or higher version of 1.3 (if available)
– david_k
Nov 23 '18 at 11:34
Okay. I will try by that but is it okay to use fabric-shim 1.3.1 with fabric 1.3.0?
– Honey Shah
Nov 23 '18 at 11:55
Okay. I will try by that but is it okay to use fabric-shim 1.3.1 with fabric 1.3.0?
– Honey Shah
Nov 23 '18 at 11:55
Yes, its fine to use that version
– david_k
Nov 23 '18 at 13:20
Yes, its fine to use that version
– david_k
Nov 23 '18 at 13:20
I tried by using fabric-shim 1.3.1 but the error is still persist
– Honey Shah
Nov 24 '18 at 9:12
I tried by using fabric-shim 1.3.1 but the error is still persist
– Honey Shah
Nov 24 '18 at 9:12
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445400%2fhyperledger-fabric-error-14-unavailable-tcp-write-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445400%2fhyperledger-fabric-error-14-unavailable-tcp-write-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
For fabric 1.3, try using fabric-shim 1.3.1 or higher version of 1.3 (if available)
– david_k
Nov 23 '18 at 11:34
Okay. I will try by that but is it okay to use fabric-shim 1.3.1 with fabric 1.3.0?
– Honey Shah
Nov 23 '18 at 11:55
Yes, its fine to use that version
– david_k
Nov 23 '18 at 13:20
I tried by using fabric-shim 1.3.1 but the error is still persist
– Honey Shah
Nov 24 '18 at 9:12