You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to checkpoint restore a pretty complicate program that involves R and something else. Sometimes I hit the Can't restore not-sent send queue data (-1), want (0-592:2427144:592): Broken pipe error after some run time. Could anyone please give some idea in what situation this error could happen? I am using the --tcp-establish flag for both checkpoint and restore. Any other option I should try? Thanks!
Steps to reproduce the issue:
Unfortunately, I haven't found a way to reproduce this stable.
Describe the results you received:
Restore failed with Can't restore not-sent send queue data (-1), want (0-592:2427144:592): Broken pipe.
Describe the results you expected:
Restore success.
Additional information you deem important (e.g. issue happens only occasionally):
Description
I'm trying to checkpoint restore a pretty complicate program that involves R and something else. Sometimes I hit the
Can't restore not-sent send queue data (-1), want (0-592:2427144:592): Broken pipe
error after some run time. Could anyone please give some idea in what situation this error could happen? I am using the--tcp-establish
flag for both checkpoint and restore. Any other option I should try? Thanks!Steps to reproduce the issue:
Unfortunately, I haven't found a way to reproduce this stable.
Describe the results you received:
Restore failed with
Can't restore not-sent send queue data (-1), want (0-592:2427144:592): Broken pipe
.Describe the results you expected:
Restore success.
Additional information you deem important (e.g. issue happens only occasionally):
CRIU logs and information:
restore_log.txt
CRIU full dump/restore logs:
Output of `criu --version`:
Version: 3.19 (gitid v3.19) ``` (paste your output here) ```
Output of `criu check --all`:
Additional environment details:
Running on Kernel
Linux 5.14.0-58.el9.x86_64
.The text was updated successfully, but these errors were encountered: