-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRIU hang on dump or restore #2032
Comments
Run it under strace and attach logs here:
|
Could you try out with this patch?
|
Hi, now it is working! Thank you! |
A friendly reminder that this issue had no activity for 30 days. |
Please, could I help with this? |
A friendly reminder that this issue had no activity for 30 days. |
I am seeing this too, but only on the first checkpoint after boot. This is with
the process isn't hung, it continues after 40 seconds,
|
This reproduces with the latest CRIU version and the fix to add '-n' to the iptables command worked. |
@adrianreber - is there anything against submitting the patch in #2032 (comment) ? |
Resolving service names can be slow and it isn't needed here. Fixes checkpoint-restore#2032 Signed-off-by: Andrei Vagin <avagin@google.com>
When CRIU checks if the iptables command supports xtables locks, it triggers hostname resolution, and this causes the dump/restore commands to hang. Fixes: checkpoint-restore#2032 Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
Resolving service names can be slow and it isn't needed here. Fixes #2032 Signed-off-by: Andrei Vagin <avagin@google.com>
I am trying to dump or restore any process (even a process that no exists) using sudo or root access:
kernel:
No error msg. It only hangs.
The text was updated successfully, but these errors were encountered: