[CRIU] I can't dump mysqld

[Andrew Vagin]

On Sat, Jul 30, 2016 at 11:16:45AM +0900, Yohei Kamitsukasa wrote:
> On 7/28/16 15:17, Andrew Vagin wrote:
> 
> > On Thu, Jul 28, 2016 at 09:58:39AM +0900, Yohei Kamitsukasa wrote:
> > > rt_sigaction(SIGCHLD, {0x45b940, [CHLD], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x7f6c58d163d0}, NULL, 8) = 0
> > > ptrace(PTRACE_SETSIGMASK, 8367, 0x8, 0x7ffe72948b30) = 0
> > > ptrace(PTRACE_SETREGSET, 8367, NT_PRSTATUS, [{0x7ffe72948b90, 216}]) = 0
> > > ptrace(PTRACE_CONT, 8367, NULL, SIG_0)  = 0
> > > accept(6,
> > 
> > Could you check that all processes live in the same network namespaces?
> > 
> > "readlink /proc/pid/ns/net" should return the same value for all
> > processes.
> Thank you for teaching how to check to me:)
> I checked the network namespaces of mysqld's processes and they were in same
> network namespace all. (A process of CRIU dumping was in the network
> namespace.)
> 
> In addition, I realized that a version of MySQL might be 5.6 in this
> question (https://lists.openvz.org/pipermail/criu/2014-April/013424.html)
> but I had used 5.7.
> Then I tried to use MySQL(5.6) and CRIU(2.0) but the result was same...

Could you apply the following patch [1] and try again?
[1]: https://patchwork.criu.org/patch/1136/mbox/

This patch will not fix the problem, but it will show more info about an
error in a log file.

Thanks,
Andrew