<div dir="ltr"><div><div>Hello;<br></div><div><br></div>I have done new tests on my old container and the same problem:<br><br>restore.log<br>Warn (cr-restore.c:1029): Set CLONE_PARENT | CLONE_NEWPID but it might cause restore problem,because not all kernels support such clone flags combinations!<br>RTNETLINK answers: File exists<br>RTNETLINK answers: File exists<br>RTNETLINK answers: File exists<br> 920: Error (sk-inet.c:610): Can't bind inet socket: Invalid argument<br><br><br>root@g-23:/tmp# lxc-ls -f<br>^CTraceback (most recent call last):<br> File "/usr/bin/lxc-ls", line 432, in <module><br> containers = get_containers(root=True)<br> File "/usr/bin/lxc-ls", line 261, in get_containers<br> if container.controllable:<br>KeyboardInterrupt<br><br><br><i>Do you have a way to reproduce this? I'm not sure what it means<br>
exactly, perhaps Pavel can elaborate. However, it would be nice to<br>
have a small testcase so I can try and fix it.<br><br><br></i></div><div><br></div><div>In this old container,i have (lxc bridge network, jdk, some other libraries, i have modified /etc/sudoers, etc... )<br></div><div>i can't understand the source of the problem ! <br><br></div><div>Best Regards. <br></div><div><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-15 14:45 GMT+01:00 Tycho Andersen <span dir="ltr"><<a href="mailto:tycho.andersen@canonical.com" target="_blank">tycho.andersen@canonical.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sun, Jun 14, 2015 at 02:02:13PM +0100, Thouraya TH wrote:<br>
> Hello all;<br>
><br>
> I have done two tests: (criu 1.6)<br>
><br>
</span>> 1- *Test 1:*<br>
<span class="">> I have created a new container using:<br>
> lxc-create -t ubuntu -n worker2 http_proxy=True<br>
><br>
</span>> *I have not installed any tool in this container.*<br>
<span class="">><br>
> lxc-checkpoint -s -D /tmp/dire -n worker2<br>
> lxc-checkpoint -r -D /tmp/dire -n worker2<br>
><br>
> root@localhost:~# lxc-ls -f<br>
> NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> ----------------------------------------------------<br>
> worker STOPPED - - - NO<br>
</span>> *worker2* RUNNING 10.0.3.48 - - NO<br>
><br>
> 2- *Test 2: *<br>
<span class="">><br>
> lxc-start -n worker (it is an old worker: i have installed many tools in<br>
> this container, jdk, etc ......)<br>
> root@localhost:/tmp# lxc-ls -f<br>
> NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> -----------------------------------------------------<br>
> worker RUNNING 10.0.3.109 - - NO<br>
> worker2 RUNNING 10.0.3.48 - - NO<br>
><br>
> lxc-checkpoint -s -D /tmp/direworker -n worker<br>
> lxc-checkpoint -r -D /tmp/direworker -n worker<br>
><br>
> lxc-ls -f<br>
> ^CTraceback (most recent call last):<br>
> File "/usr/bin/lxc-ls", line 432, in <module><br>
> containers = get_containers(root=True)<br>
> File "/usr/bin/lxc-ls", line 261, in get_containers<br>
> if container.controllable:<br>
> KeyboardInterrupt<br>
<br>
</span>This means that the restore failed and lxc-checkpoint didn't<br>
understand that it failed, and is still waiting. I think we recently<br>
fixed a bug (there is a patch about SIGCHLD) that will cause this not<br>
to hang here.<br>
<span class=""><br>
> dump.log:<br>
> Warn (fsnotify.c:188): fsnotify: Handle 800003:3c605 cannot be opened<br>
> Warn (fsnotify.c:188): fsnotify: Handle 800003:4a4ba cannot be opened<br>
> Warn (arch/x86/crtools.c:132): Will restore 4271 with interrupted system<br>
> call<br>
> Warn (arch/x86/crtools.c:132): Will restore 4454 with interrupted system<br>
> call<br>
> Warn (arch/x86/crtools.c:132): Will restore 4455 with interrupted system<br>
> call<br>
> Warn (arch/x86/crtools.c:132): Will restore 4460 with interrupted system<br>
> call<br>
> Warn (arch/x86/crtools.c:132): Will restore 4461 with interrupted system<br>
> call<br>
> Warn (arch/x86/crtools.c:132): Will restore 4463 with interrupted system<br>
> call<br>
><br>
> restore.log:<br>
> Warn (cr-restore.c:1029): Set CLONE_PARENT | CLONE_NEWPID but it might<br>
> cause restore problem,because not all kernels support such clone flags<br>
> combinations!<br>
> RTNETLINK answers: File exists<br>
> RTNETLINK answers: File exists<br>
> RTNETLINK answers: File exists<br>
><br>
><br>
> Can you please explain to me what is the problem? is it because of some<br>
> tools installed in the container?<br>
<br>
</span>Do you have a way to reproduce this? I'm not sure what it means<br>
exactly, perhaps Pavel can elaborate. However, it would be nice to<br>
have a small testcase so I can try and fix it.<br>
<br>
Thanks,<br>
<br>
Tycho<br>
<span class=""><br>
><br>
> Thanks a lot for help.<br>
> Best regards.<br>
<br>
</span>> _______________________________________________<br>
> CRIU mailing list<br>
> <a href="mailto:CRIU@openvz.org">CRIU@openvz.org</a><br>
> <a href="https://lists.openvz.org/mailman/listinfo/criu" rel="noreferrer" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
<br>
</blockquote></div><br></div>