[CRIU] Dumping lxc container failed - CRIU 1.6

[Pavel Emelyanov]

On 06/24/2015 06:42 PM, Thouraya TH wrote:
> Hello all,
> 
> Here is my situation.
> 
> 
> I have three containers on my host.
> 
> 
> 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:_

Does it happen always? What if you try to dump this container again without restart?

> 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.
> 
> 
> I have done:
> 
> crit decode --pretty < inetsk.img  > output.txt

But dumping failed, this image doesn't contain full picture.

-- Pavel