SCP gets broken pipe, but meanwhile ssh works well
I've searched around and solutions to other similar questions cannot solve my problem.
I'm using Mac to ssh and scp to multiple servers (after I VPN into my company's network from my Mac at home).
I can ssh from Mac via VPN to servers (I call them server A, B, and C), all the time without any problem, no broken pipe, no idle, no kicked out, etc. Based on this, I assume my Mac ssh settings are okay, and server A/B/C settings are also okay for me to ssh in (via VPN) all the time.
After I ssh from Mac via VPN to any of A/B/C, and then scp from any of A/B/C to any of A/B/C without any problem, no matter how big the files are. Based on this, I assume settings on servers A/B/C have are okay.
However, sometimes, I have scp problem, but not always. My usual working style is like this: after VPN is connected, I have a terminal X that ssh into A all the time, another terminal Y scp files to A from occasionally. Although X ssh is always connected, Y may be able to scp files to A in the morning, but may not be able to do so in the afternoon, with errors like:
packet_write_wait: Connection to 192.168.xxx.xxx port 22: Broken pipe
Once it gets the kind of "Broken pipe", it won't be able to scp for hours. I then usually switch to scp to B (and do scp from B to A if A is my final destination). This switch usually works for a day. Next day or so, I may be able to scp to A again, particularly when files are small (because 81920 bytes of file will be transferred before pipe gets broken).
I have edited ~/.ssh/config in my Mac with
Host *
ServerAliveInterval 30
ServerAliveCountMax 5
TCPKeepAlive yes
and /etc/ssh/sshd_config on A/B/C with
ServerAliveInterval 120
ClientAliveInterval 600
ClientAliveCountMax 0
However this does not help.
How can I fix the problem? Thank you in advance!
ssh scp
asked 1 hour ago
Tony XuTony Xu
1011
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I've searched around and solutions to other similar questions cannot solve my problem.
I'm using Mac to ssh and scp to multiple servers (after I VPN into my company's network from my Mac at home).
I can ssh from Mac via VPN to servers (I call them server A, B, and C), all the time without any problem, no broken pipe, no idle, no kicked out, etc. Based on this, I assume my Mac ssh settings are okay, and server A/B/C settings are also okay for me to ssh in (via VPN) all the time.
After I ssh from Mac via VPN to any of A/B/C, and then scp from any of A/B/C to any of A/B/C without any problem, no matter how big the files are. Based on this, I assume settings on servers A/B/C have are okay.
However, sometimes, I have scp problem, but not always. My usual working style is like this: after VPN is connected, I have a terminal X that ssh into A all the time, another terminal Y scp files to A from occasionally. Although X ssh is always connected, Y may be able to scp files to A in the morning, but may not be able to do so in the afternoon, with errors like:
packet_write_wait: Connection to 192.168.xxx.xxx port 22: Broken pipe
Once it gets the kind of "Broken pipe", it won't be able to scp for hours. I then usually switch to scp to B (and do scp from B to A if A is my final destination). This switch usually works for a day. Next day or so, I may be able to scp to A again, particularly when files are small (because 81920 bytes of file will be transferred before pipe gets broken).
I have edited ~/.ssh/config in my Mac with
Host *
ServerAliveInterval 30
ServerAliveCountMax 5
TCPKeepAlive yes
and /etc/ssh/sshd_config on A/B/C with
ServerAliveInterval 120
ClientAliveInterval 600
ClientAliveCountMax 0
However this does not help.
How can I fix the problem? Thank you in advance!
ssh scp
asked 1 hour ago
Tony XuTony Xu
1011
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I've searched around and solutions to other similar questions cannot solve my problem.
I'm using Mac to ssh and scp to multiple servers (after I VPN into my company's network from my Mac at home).
I can ssh from Mac via VPN to servers (I call them server A, B, and C), all the time without any problem, no broken pipe, no idle, no kicked out, etc. Based on this, I assume my Mac ssh settings are okay, and server A/B/C settings are also okay for me to ssh in (via VPN) all the time.
After I ssh from Mac via VPN to any of A/B/C, and then scp from any of A/B/C to any of A/B/C without any problem, no matter how big the files are. Based on this, I assume settings on servers A/B/C have are okay.
However, sometimes, I have scp problem, but not always. My usual working style is like this: after VPN is connected, I have a terminal X that ssh into A all the time, another terminal Y scp files to A from occasionally. Although X ssh is always connected, Y may be able to scp files to A in the morning, but may not be able to do so in the afternoon, with errors like:
packet_write_wait: Connection to 192.168.xxx.xxx port 22: Broken pipe
Once it gets the kind of "Broken pipe", it won't be able to scp for hours. I then usually switch to scp to B (and do scp from B to A if A is my final destination). This switch usually works for a day. Next day or so, I may be able to scp to A again, particularly when files are small (because 81920 bytes of file will be transferred before pipe gets broken).
I have edited ~/.ssh/config in my Mac with
Host *
ServerAliveInterval 30
ServerAliveCountMax 5
TCPKeepAlive yes
and /etc/ssh/sshd_config on A/B/C with
ServerAliveInterval 120
ClientAliveInterval 600
ClientAliveCountMax 0
However this does not help.
How can I fix the problem? Thank you in advance!
ssh scp
asked 1 hour ago
Tony XuTony Xu
1011
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I've searched around and solutions to other similar questions cannot solve my problem.
I'm using Mac to ssh and scp to multiple servers (after I VPN into my company's network from my Mac at home).
I can ssh from Mac via VPN to servers (I call them server A, B, and C), all the time without any problem, no broken pipe, no idle, no kicked out, etc. Based on this, I assume my Mac ssh settings are okay, and server A/B/C settings are also okay for me to ssh in (via VPN) all the time.
After I ssh from Mac via VPN to any of A/B/C, and then scp from any of A/B/C to any of A/B/C without any problem, no matter how big the files are. Based on this, I assume settings on servers A/B/C have are okay.
However, sometimes, I have scp problem, but not always. My usual working style is like this: after VPN is connected, I have a terminal X that ssh into A all the time, another terminal Y scp files to A from occasionally. Although X ssh is always connected, Y may be able to scp files to A in the morning, but may not be able to do so in the afternoon, with errors like:
packet_write_wait: Connection to 192.168.xxx.xxx port 22: Broken pipe
Once it gets the kind of "Broken pipe", it won't be able to scp for hours. I then usually switch to scp to B (and do scp from B to A if A is my final destination). This switch usually works for a day. Next day or so, I may be able to scp to A again, particularly when files are small (because 81920 bytes of file will be transferred before pipe gets broken).
I have edited ~/.ssh/config in my Mac with
Host *
ServerAliveInterval 30
ServerAliveCountMax 5
TCPKeepAlive yes
and /etc/ssh/sshd_config on A/B/C with
ServerAliveInterval 120
ClientAliveInterval 600
ClientAliveCountMax 0
However this does not help.
How can I fix the problem? Thank you in advance!
ssh scp
ssh scp
asked 1 hour ago
Tony XuTony Xu
1011
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
Tony XuTony Xu
1011
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
Tony XuTony Xu
1011
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
Tony XuTony Xu
1011
asked 1 hour ago
Tony XuTony Xu
1011
1011
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Tony Xu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
Tony Xu is a new contributor. Be nice, and check out our Code of Conduct.
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%2funix.stackexchange.com%2fquestions%2f504022%2fscp-gets-broken-pipe-but-meanwhile-ssh-works-well%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
Tony Xu is a new contributor. Be nice, and check out our Code of Conduct.
Tony Xu is a new contributor. Be nice, and check out our Code of Conduct.
Tony Xu is a new contributor. Be nice, and check out our Code of Conduct.
Tony Xu is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
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%2funix.stackexchange.com%2fquestions%2f504022%2fscp-gets-broken-pipe-but-meanwhile-ssh-works-well%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
