[lxc-users] Trying out migration, getting "error: checkpoint failed"

Tycho Andersen tycho.andersen at canonical.com
Fri May 15 17:59:53 UTC 2015


On Fri, May 15, 2015 at 06:30:05PM +0100, Giles Thomas wrote:
> Hi Tycho,
> 
> On 08/05/15 17:03, Tycho Andersen wrote:
> >Sorry for the delay.
> 
> Likewise!
> 
> >On Thu, May 07, 2015 at 12:32:58PM +0100, Giles Thomas wrote:
> >>On 06/05/15 16:29, Tycho Andersen wrote:
> >>>Sorry, I did just find one notable exception with the current git master:
> >>>liblxc doesn't complain when excing criu fails. Do you have criu installed
> >>>in a place where liblxc can find it? I posted a patch to fix this
> >>>particular case, but it seems likely that's where your problem is. Tycho
> >>It's installed in /usr/sbin/criu -- the lxc monitor is running as root, so
> >>that should be OK, right?
> >I think so, but obviously something is wrong :). If you cat
> >/proc/`pidof lxd`/environ, is /usr/sbin in its path?
> 
> Yes, it is.
> 
> >It may be worth
> >upgrading to the lxd/lxd-client from git master; I wrote a patch a few
> >days ago so you can do:
> >
> >lxc info migratee --show-log
> >
> >and get the lxc log output, which should have the error you're
> >experiencing.
> 
> I built lxd from source and re-ran the test; here's what I got from the
> --show-log:
> 
> 
> root at XXXXXXX:~# $GOPATH/bin/lxc info migratee --show-log
> Name: migratee
> Status: RUNNING
> Init: 1647
> Ips:
> (none)
> 
> Log:
> 
>             lxc 1431710609.087 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710609.091 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710609.097 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710609.102 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710802.699 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710802.703 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710802.709 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710802.715 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710803.578 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710804.702 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710884.178 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710884.181 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710884.188 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710884.194 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710885.058 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710886.166 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710895.481 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710895.485 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710895.492 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
>             lxc 1431710895.498 DEBUG    lxc_commands -
> commands.c:lxc_cmd_get_state:574 - 'migratee' is in 'RUNNING' state
> 
> 
> Any clues there?

Unfortunately not. I suspect it still can't find criu and it just
isn't finding the binary. Can you symlink it into /bin just to be
sure?

Tycho

> 
> All the best,
> 
> Giles
> 
> -- 
> Giles Thomas <giles at pythonanywhere.com>
> 
> PythonAnywhere: Develop and host Python from your browser
> <https://www.pythonanywhere.com/>
> 
> A product from PythonAnywhere LLP
> 17a Clerkenwell Road, London EC1M 5RD, UK
> VAT No.: GB 893 5643 79
> Registered in England and Wales as company number OC378414.
> Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
> 
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users


More information about the lxc-users mailing list