Network error: Software caused connection abort during copying on linux

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0















On my remote, I have a recursive directory 'dir'. I try to copy all the files in 'dir' into a folder in another location on the remote on Linux. It copies and an hour later or so on the terminal I get;



Session stopped
- Press <return> to exit tab
- Press R to restart session
- Press S to save terminal output to file

Network error: Software caused connection abort


This happens each time. I don`t know if it stopped after it copied everything or before. I compared the size of the two files using;



du -sh file_path


They are 71G and 70G.Does anyone know why this network error occurs, and how can I prevent it? I use mobaXterm, and although I didn`t watch every minute of it but I didn't see internet disconnection during the copying.
thanks










share|improve this question






















  • Try turning on the Enable SSH keepalive setting on mobaxterm.

    – Mark Plotnick
    Jan 30 at 20:56











  • I had no idea such an option exist, thank you very much, i just checked, it was unchecked in settings.

    – kutlus
    Jan 30 at 20:59















0















On my remote, I have a recursive directory 'dir'. I try to copy all the files in 'dir' into a folder in another location on the remote on Linux. It copies and an hour later or so on the terminal I get;



Session stopped
- Press <return> to exit tab
- Press R to restart session
- Press S to save terminal output to file

Network error: Software caused connection abort


This happens each time. I don`t know if it stopped after it copied everything or before. I compared the size of the two files using;



du -sh file_path


They are 71G and 70G.Does anyone know why this network error occurs, and how can I prevent it? I use mobaXterm, and although I didn`t watch every minute of it but I didn't see internet disconnection during the copying.
thanks










share|improve this question






















  • Try turning on the Enable SSH keepalive setting on mobaxterm.

    – Mark Plotnick
    Jan 30 at 20:56











  • I had no idea such an option exist, thank you very much, i just checked, it was unchecked in settings.

    – kutlus
    Jan 30 at 20:59













0












0








0








On my remote, I have a recursive directory 'dir'. I try to copy all the files in 'dir' into a folder in another location on the remote on Linux. It copies and an hour later or so on the terminal I get;



Session stopped
- Press <return> to exit tab
- Press R to restart session
- Press S to save terminal output to file

Network error: Software caused connection abort


This happens each time. I don`t know if it stopped after it copied everything or before. I compared the size of the two files using;



du -sh file_path


They are 71G and 70G.Does anyone know why this network error occurs, and how can I prevent it? I use mobaXterm, and although I didn`t watch every minute of it but I didn't see internet disconnection during the copying.
thanks










share|improve this question














On my remote, I have a recursive directory 'dir'. I try to copy all the files in 'dir' into a folder in another location on the remote on Linux. It copies and an hour later or so on the terminal I get;



Session stopped
- Press <return> to exit tab
- Press R to restart session
- Press S to save terminal output to file

Network error: Software caused connection abort


This happens each time. I don`t know if it stopped after it copied everything or before. I compared the size of the two files using;



du -sh file_path


They are 71G and 70G.Does anyone know why this network error occurs, and how can I prevent it? I use mobaXterm, and although I didn`t watch every minute of it but I didn't see internet disconnection during the copying.
thanks







linux






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 30 at 16:59









kutluskutlus

686




686












  • Try turning on the Enable SSH keepalive setting on mobaxterm.

    – Mark Plotnick
    Jan 30 at 20:56











  • I had no idea such an option exist, thank you very much, i just checked, it was unchecked in settings.

    – kutlus
    Jan 30 at 20:59

















  • Try turning on the Enable SSH keepalive setting on mobaxterm.

    – Mark Plotnick
    Jan 30 at 20:56











  • I had no idea such an option exist, thank you very much, i just checked, it was unchecked in settings.

    – kutlus
    Jan 30 at 20:59
















Try turning on the Enable SSH keepalive setting on mobaxterm.

– Mark Plotnick
Jan 30 at 20:56





Try turning on the Enable SSH keepalive setting on mobaxterm.

– Mark Plotnick
Jan 30 at 20:56













I had no idea such an option exist, thank you very much, i just checked, it was unchecked in settings.

– kutlus
Jan 30 at 20:59





I had no idea such an option exist, thank you very much, i just checked, it was unchecked in settings.

– kutlus
Jan 30 at 20:59










1 Answer
1






active

oldest

votes


















2














I can't really help you on the disconnection issue, but if the problem still exists and/or annoys you, you could copy the files with the nohup command. This would keep the copy process alive even if you get disconnected.



To synchronize your source and destination directory using rsync, you could use



nohup rsync -av /path_to/source_directory/ /path_to/destination_directory &


This would copy all remaining files and directories (if any) from the source to the destination directory and would also make sure that no "partly" copied files are left in the destination directory.



Another possibility to check if both directories contain the same files is the use of diff:



# compare dirs and watch result in terminal
diff -r /path_to/source_directory /path_to/destination_directory
# compare dirs and write result to diff.log (disconnection failsafe)
nohup diff -r /path_to/source_directory /path_to/destination_directory > diff.log &


The second command would create a logfile diff.log of all files only existing in one of both directories as well as all files with differences (partly copied) and thus help you find out at which point the copy process was aborted.






share|improve this answer























  • I was searching how I could use rsync instead and got your answer, very helpful, many thanks!

    – kutlus
    Jan 30 at 18:52











  • Thanks! Make sure you add the trailing slash "/" to the source directory, otherwise you will copy your source directory as subdirectory to the destination dir. If you previously did a cp -r /home/user/dir1 /tmp/dir2 you will need rsync -av /home/user/dir1/ /tmp/dir2.

    – Freddy
    Jan 30 at 18:57












  • Hi, yes, I do put "/". Also I have just tried 'diff -r command and saw the difference between two folders. Learned two things today from you, thank you!

    – kutlus
    Jan 30 at 19:14










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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497738%2fnetwork-error-software-caused-connection-abort-during-copying-on-linux%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














I can't really help you on the disconnection issue, but if the problem still exists and/or annoys you, you could copy the files with the nohup command. This would keep the copy process alive even if you get disconnected.



To synchronize your source and destination directory using rsync, you could use



nohup rsync -av /path_to/source_directory/ /path_to/destination_directory &


This would copy all remaining files and directories (if any) from the source to the destination directory and would also make sure that no "partly" copied files are left in the destination directory.



Another possibility to check if both directories contain the same files is the use of diff:



# compare dirs and watch result in terminal
diff -r /path_to/source_directory /path_to/destination_directory
# compare dirs and write result to diff.log (disconnection failsafe)
nohup diff -r /path_to/source_directory /path_to/destination_directory > diff.log &


The second command would create a logfile diff.log of all files only existing in one of both directories as well as all files with differences (partly copied) and thus help you find out at which point the copy process was aborted.






share|improve this answer























  • I was searching how I could use rsync instead and got your answer, very helpful, many thanks!

    – kutlus
    Jan 30 at 18:52











  • Thanks! Make sure you add the trailing slash "/" to the source directory, otherwise you will copy your source directory as subdirectory to the destination dir. If you previously did a cp -r /home/user/dir1 /tmp/dir2 you will need rsync -av /home/user/dir1/ /tmp/dir2.

    – Freddy
    Jan 30 at 18:57












  • Hi, yes, I do put "/". Also I have just tried 'diff -r command and saw the difference between two folders. Learned two things today from you, thank you!

    – kutlus
    Jan 30 at 19:14















2














I can't really help you on the disconnection issue, but if the problem still exists and/or annoys you, you could copy the files with the nohup command. This would keep the copy process alive even if you get disconnected.



To synchronize your source and destination directory using rsync, you could use



nohup rsync -av /path_to/source_directory/ /path_to/destination_directory &


This would copy all remaining files and directories (if any) from the source to the destination directory and would also make sure that no "partly" copied files are left in the destination directory.



Another possibility to check if both directories contain the same files is the use of diff:



# compare dirs and watch result in terminal
diff -r /path_to/source_directory /path_to/destination_directory
# compare dirs and write result to diff.log (disconnection failsafe)
nohup diff -r /path_to/source_directory /path_to/destination_directory > diff.log &


The second command would create a logfile diff.log of all files only existing in one of both directories as well as all files with differences (partly copied) and thus help you find out at which point the copy process was aborted.






share|improve this answer























  • I was searching how I could use rsync instead and got your answer, very helpful, many thanks!

    – kutlus
    Jan 30 at 18:52











  • Thanks! Make sure you add the trailing slash "/" to the source directory, otherwise you will copy your source directory as subdirectory to the destination dir. If you previously did a cp -r /home/user/dir1 /tmp/dir2 you will need rsync -av /home/user/dir1/ /tmp/dir2.

    – Freddy
    Jan 30 at 18:57












  • Hi, yes, I do put "/". Also I have just tried 'diff -r command and saw the difference between two folders. Learned two things today from you, thank you!

    – kutlus
    Jan 30 at 19:14













2












2








2







I can't really help you on the disconnection issue, but if the problem still exists and/or annoys you, you could copy the files with the nohup command. This would keep the copy process alive even if you get disconnected.



To synchronize your source and destination directory using rsync, you could use



nohup rsync -av /path_to/source_directory/ /path_to/destination_directory &


This would copy all remaining files and directories (if any) from the source to the destination directory and would also make sure that no "partly" copied files are left in the destination directory.



Another possibility to check if both directories contain the same files is the use of diff:



# compare dirs and watch result in terminal
diff -r /path_to/source_directory /path_to/destination_directory
# compare dirs and write result to diff.log (disconnection failsafe)
nohup diff -r /path_to/source_directory /path_to/destination_directory > diff.log &


The second command would create a logfile diff.log of all files only existing in one of both directories as well as all files with differences (partly copied) and thus help you find out at which point the copy process was aborted.






share|improve this answer













I can't really help you on the disconnection issue, but if the problem still exists and/or annoys you, you could copy the files with the nohup command. This would keep the copy process alive even if you get disconnected.



To synchronize your source and destination directory using rsync, you could use



nohup rsync -av /path_to/source_directory/ /path_to/destination_directory &


This would copy all remaining files and directories (if any) from the source to the destination directory and would also make sure that no "partly" copied files are left in the destination directory.



Another possibility to check if both directories contain the same files is the use of diff:



# compare dirs and watch result in terminal
diff -r /path_to/source_directory /path_to/destination_directory
# compare dirs and write result to diff.log (disconnection failsafe)
nohup diff -r /path_to/source_directory /path_to/destination_directory > diff.log &


The second command would create a logfile diff.log of all files only existing in one of both directories as well as all files with differences (partly copied) and thus help you find out at which point the copy process was aborted.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 30 at 18:48









FreddyFreddy

3898




3898












  • I was searching how I could use rsync instead and got your answer, very helpful, many thanks!

    – kutlus
    Jan 30 at 18:52











  • Thanks! Make sure you add the trailing slash "/" to the source directory, otherwise you will copy your source directory as subdirectory to the destination dir. If you previously did a cp -r /home/user/dir1 /tmp/dir2 you will need rsync -av /home/user/dir1/ /tmp/dir2.

    – Freddy
    Jan 30 at 18:57












  • Hi, yes, I do put "/". Also I have just tried 'diff -r command and saw the difference between two folders. Learned two things today from you, thank you!

    – kutlus
    Jan 30 at 19:14

















  • I was searching how I could use rsync instead and got your answer, very helpful, many thanks!

    – kutlus
    Jan 30 at 18:52











  • Thanks! Make sure you add the trailing slash "/" to the source directory, otherwise you will copy your source directory as subdirectory to the destination dir. If you previously did a cp -r /home/user/dir1 /tmp/dir2 you will need rsync -av /home/user/dir1/ /tmp/dir2.

    – Freddy
    Jan 30 at 18:57












  • Hi, yes, I do put "/". Also I have just tried 'diff -r command and saw the difference between two folders. Learned two things today from you, thank you!

    – kutlus
    Jan 30 at 19:14
















I was searching how I could use rsync instead and got your answer, very helpful, many thanks!

– kutlus
Jan 30 at 18:52





I was searching how I could use rsync instead and got your answer, very helpful, many thanks!

– kutlus
Jan 30 at 18:52













Thanks! Make sure you add the trailing slash "/" to the source directory, otherwise you will copy your source directory as subdirectory to the destination dir. If you previously did a cp -r /home/user/dir1 /tmp/dir2 you will need rsync -av /home/user/dir1/ /tmp/dir2.

– Freddy
Jan 30 at 18:57






Thanks! Make sure you add the trailing slash "/" to the source directory, otherwise you will copy your source directory as subdirectory to the destination dir. If you previously did a cp -r /home/user/dir1 /tmp/dir2 you will need rsync -av /home/user/dir1/ /tmp/dir2.

– Freddy
Jan 30 at 18:57














Hi, yes, I do put "/". Also I have just tried 'diff -r command and saw the difference between two folders. Learned two things today from you, thank you!

– kutlus
Jan 30 at 19:14





Hi, yes, I do put "/". Also I have just tried 'diff -r command and saw the difference between two folders. Learned two things today from you, thank you!

– kutlus
Jan 30 at 19:14

















draft saved

draft discarded
















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497738%2fnetwork-error-software-caused-connection-abort-during-copying-on-linux%23new-answer', 'question_page');

);

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






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?