[CRIU] CRIU user question

[Cyrill Gorcunov]

On Thu, Apr 24, 2014 at 11:32:41AM -0400, J F wrote:
>    Here is the crtools logging information requested. The status error
>    changed after I increased the file handle limit. Let me know if you have
>    any thoughts.A 
>    Hint: Dump/restore works great for this process when I'm not embedding the
>    JVM. So, something about embedding the JVM into this c code app....
>    ubuntu at ip-10-118-238-44:/mnt/mydata$ lsb_release -a
>    No LSB modules are available.
>    Distributor ID: Ubuntu
>    Description: A  A Ubuntu 14.04 LTS
>    Release: A  A  A  A 14.04
>    Codename: A  A  A  trusty
>    ubuntu at ip-10-118-238-44:/mnt/mydata$ sudo ./criu/criu-1.2/crtools check
>    Warn A (libnetlink.c:53): ERROR -2 reported by netlink
>    Warn A (libnetlink.c:53): ERROR -2 reported by netlink
>    Warn A (sockets.c:620): The current kernel doesn't support packet_diag
>    Warn A (libnetlink.c:53): ERROR -2 reported by netlink
>    Warn A (sockets.c:630): The current kernel doesn't support netlink_diag
>    The sock diag infrastructure is incomplete.
>    Make sure you have:
>    A 1. *_DIAG kernel config options turned on;
>    A 2. *_diag.ko modules loaded (if compiled as modules).
>    ubuntu at ip-10-118-238-44:/mnt/mydata$ sudo ./criu/criu-1.2/crtools dump
>    --tree 2232 --shell-job --images-dir /mnt/mydata/dump
>    Warn A (libnetlink.c:53): ERROR -2 reported by netlink
>    Warn A (libnetlink.c:53): ERROR -2 reported by netlink
>    Warn A (sockets.c:620): The current kernel doesn't support packet_diag
>    Warn A (libnetlink.c:53): ERROR -2 reported by netlink
>    Warn A (sockets.c:630): The current kernel doesn't support netlink_diag
>    Error (sockets.c:240): Sockets (family 1, proto 0) are not collected
>    Error (sk-unix.c:173): Unix socket 0x3327 not found

It looks like the kernel doesn't support DIAG feature (either too old, either
diag modules are not loaded), but application you're checkpointing uses unix
socket and criu fail to proceed because it can't fetch information needed
from the kernel. Could you try to load diag modules? (for unix sockets
it should be something like "modprobe unix_diag").