[CRIU] Dumping lxc container failed - CRIU 1.6
Thouraya TH
thouraya87 at gmail.com
Sat Sep 26 06:54:25 PDT 2015
Hello everyone,
I am sorry if I go back to an old discussion.
One detail that I forgot to mention
The two containers communicate through message exchange at the moment of
dumping.
*Is the that the cause of the failed dumping ?*
*I have done the dumping process of the first container as follows:*
*lxc-checkpoint -s -D /tmp/dire -n worker1*
*Then I restart it as follows:*
*lxc-checkpoint -r -D /tmp/dire -n worker1*
*worker 1 restarts well. (lxc-ls -f display that worker1 is RUNNING)*
*I wanted to test the dumping process of the second container as follows:*
*lxc-checkpoint -s -D /tmp/dire4 -n worker2 ( P.S: worker1 and worker2 are
cloned of the same container workerTest)*
*but Dumping failed:*
*Warn (fsnotify.c:188): fsnotify: Handle 800003:38916 cannot be
opened*
*Warn (fsnotify.c:188): fsnotify: Handle 800003:56662 cannot be
opened*
*Warn (arch/x86/crtools.c:132): Will restore 3420 with interrupted system
call*
*Error (sk-inet.c:188): Name resolved on unconnected socket*
*Error (cr-dump.c:1584): Dump files (pid: 10592) failed with -1*
*Error (cr-dump.c:1947): Dumping FAILED.*
Thank you so much.
Best Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150926/9d131024/attachment.html>
More information about the CRIU
mailing list