<div dir="ltr"><div>Hello,<br><br></div><div>I understand that i have to access the contenair with ssh for example (<span class="im">ssh ubuntu@$(sudo lxc-info -n worker -H -i)), from the begining, before the dumping process ?<br></span></div><div><span class="im">instead of lxc-start ? <br><br></span></div>Thanks a lot for help. <br>Bests.<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-20 12:43 GMT+01:00 Andrew Vagin <span dir="ltr"><<a href="mailto:avagin@parallels.com" target="_blank">avagin@parallels.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 Mon, Jan 19, 2015 at 06:09:47PM +0100, Thouraya TH wrote:<br>
> Hello :) thanks a lot for help.<br>
><br>
> How do you enter into CT? Do you use screen or ssh?<br>
><br>
> Before the Dumping Process:<br>
><br>
> root@g-2:~# lxc-ls -f<br>
> NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> -----------------------------------------------<br>
> worker STOPPED - - - NO<br>
> root@g-2:~# lxc-start -n worker<br>
> root@g-2:~# lxc-attach -n worker<br>
<br>
</span>I've understood the problem and its causes. If you execute a process in<br>
CT, it lives in CT's pid namespaces, but it belongs to another process<br>
tree, becuase its parent is outside of the CT.<br>
<br>
Currently CRIU is able to dump only one process tree. I am not sure that<br>
we will fix this problem in a near future. I can suggest you to use<br>
screen or tmux, they have to workaround your problem.<br>
<br>
Thanks,<br>
Andrew Vagin<br>
<div class="HOEnZb"><div class="h5"><br>
> root@worker:/home# cat > test.sh <<-EOF<br>
> > #!/bin/sh<br>
> > while :; do<br>
> > sleep 1<br>
> > date<br>
> > done<br>
> > EOF<br>
> root@worker:/home# chmod +x test.sh<br>
> root@worker:/home# ./test.sh<br>
> Mon Jan 19 17:58:57 CET 2015<br>
> Mon Jan 19 17:58:58 CET 2015<br>
> ..........................<br>
> After Restart, i have used ssh.<br>
><br>
><br>
> dump.log:<br>
> Warn (fsnotify.c:183): fsnotify: Handle 800003:9db17 cannot be opened<br>
> Warn (fsnotify.c:183): fsnotify: Handle 800003:9db1d cannot be opened<br>
> tar: ./udev/control: socket ignored<br>
><br>
> restore.log"<br>
> Warn (cr-restore.c:996): Set CLONE_PARENT | CLONE_NEWPID but it might cause<br>
> 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>
><br>
> Thank you so much for help.<br>
> Best Regards.<br>
><br>
> 2015-01-16 12:29 GMT+01:00 Andrew Vagin <<a href="mailto:avagin@parallels.com">avagin@parallels.com</a>>:<br>
><br>
> On Thu, Jan 15, 2015 at 02:02:56PM +0100, Thouraya TH wrote:<br>
> > Hello,<br>
><br>
> Hello,<br>
><br>
> Add Tycho into CC.<br>
><br>
> ><br>
> > Please,i have a question about the restarting process of a LXC container.<br>
> > i run this script <a href="http://criu.org/Simple_loop" target="_blank">http://criu.org/Simple_loop</a> in a container:<br>
> ><br>
> > 1)<br>
> > ubuntu@worker:/home$ ./test.sh<br>
> > Wed Jan 14 22:30:23 CET 2015<br>
> > Wed Jan 14 22:30:24 CET 2015<br>
> > Wed Jan 14 22:30:25 CET 2015<br>
> > Wed Jan 14 22:30:26 CET 2015<br>
> > Wed Jan 14 22:30:35 CET 2015<br>
> > .......................<br>
><br>
> How do you enter into CT? Do you use screen or ssh?<br>
><br>
><br>
> > 2) i have done the dumping process:<br>
> > root@g-3:/home# lxc-checkpoint -s -D /home/ImGLXC1Worker -n worker<br>
> > 3) i have restart the container:<br>
> > root@g-3:/home/ImGLXC1Worker# lxc-checkpoint -r -D /home/<br>
> ImGLXC1Worker -n<br>
> > worker<br>
> > # lxc-ls -f<br>
> > NAME STATE IPV4 IPV6 GROUPS AUTOSTART<br>
> > -----------------------------------------------------<br>
> > worker RUNNING 10.0.3.109 - - NO<br>
><br>
> Thouraya, Could you increase verbose level for criu and show us dump and<br>
> restore<br>
> logs? Tycho, could you explain how to do this with lxc-checkpoint?<br>
><br>
> Thanks,<br>
> Andrew<br>
><br>
> ><br>
> > 4) ssh ubuntu@$(sudo lxc-info -n worker -H -i)<br>
> > 5) ubuntu@worker:/home$ ps<br>
> > PID TTY TIME CMD<br>
> > 304 pts/0 00:00:00 bash<br>
> > 318 pts/0 00:00:00 ps<br>
> ><br>
> > The process "test" didn't restart!<br>
> ><br>
> > i have done another test : ubuntu@worker:/home$ ./test.sh > Results.txt /<br>
> > Dumping the container / Restarting the container/ The process "test"<br>
> didn't<br>
> > restart! and the file Results.txt didn't change !<br>
> ><br>
> > Have you an idea please ?<br>
> ><br>
> > Thanks a lot.<br>
> > Best Regards.<br>
><br>
> > _______________________________________________<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" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
><br>
><br>
><br>
</div></div></blockquote></div><br></div>