[CRIU] Dump LXC with error

[Pavel Emelyanov]

On 04/13/2015 04:30 PM, 陈晓 wrote:
> yes, the command is: criu dump --tree 2349 --tcp-established --file-locks --link-remap
> --force-irmap --manage-cgroups --images-dir dump/ -o /tmp/dump.log -v4

OK, but you'd better use the native LXC checkpoint action for this.

> At 2015-04-13 21:26:30, "Pavel Emelyanov" <xemul at parallels.com> wrote:
>> On 04/13/2015 03:32 PM, 陈晓 wrote:
>>>
>>> Hi,Pavel Emelyanov:
>>> *    When I dump lxc whith criu, some error happen? The error message is as follows:*
>>
>> Do you use criu or lxc tools for that?
>>
>>>    *(09.446495) Dumping path for 48 fd via self 132 [/home/ubuntu/jdk1.8.0_40/jre/lib/ext/sunjce_provider.jar]*
>>> *(09.446503) fdinfo: type: 0x 1 flags: 0100000/01 pos: 0x   369ea fd: 48*
>>> *(09.446517) 18490 fdinfo 49: pos: 0x               0 flags:                2/0*
>>> *(09.446526) Searching for socket 16972c (family 10)*
>>> *(09.446535) Error (sk-inet.c:134): In-flight connection (l) for 16972c*
>>
>> That's the reason -- there's an half-opened TCP connection. We cannot C/R such
>> things right now. You can wait for a while and try to checkpoint the container
>> again.

-- Pavel