<div dir="ltr"><div class="gmail_default" style="font-size:small">I must assume that LXC is not ready for production yet. Am I wrong?<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 9, 2015 at 9:54 AM, Tycho Andersen <span dir="ltr"><<a href="mailto:tycho.andersen@canonical.com" target="_blank">tycho.andersen@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Nov 06, 2015 at 08:43:33AM +0000, Jamie Brown wrote:<br>
> I’ve just discovered a new failure on a different container too;<br>
><br>
> # lxc move host2:nexus host1:nexus<br>
> error: Error transferring container data: checkpoint failed:<br>
> (00.355457) Error (files-reg.c:422): Can't dump ghost file /usr/local/sonatype-work/nexus/tmp/jar_cache5838699621686145685.tmp of 1177738 size, increase limit<br>
> (00.355477) Error (cr-dump.c:1255): Dump files (pid: 22072) failed with -1<br>
> (00.357100) Error (cr-dump.c:1617): Dumping FAILED.<br>
<br>
</span>So this is actually an error because a default limit in criu is not<br>
high enough. You can set this via the --ghost-limit in criu, but LXC<br>
currently exposes no way to set this, although I'm hoping to add a new<br>
API call to allow people to set stuff like this in the near future.<br>
<br>
Thanks,<br>
<br>
Tycho<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
><br>
> On 06/11/2015, 08:40, "lxc-users on behalf of Jamie Brown" <<a href="mailto:lxc-users-bounces@lists.linuxcontainers.org">lxc-users-bounces@lists.linuxcontainers.org</a> on behalf of <a href="mailto:Jamie.Brown@mpec.co.uk">Jamie.Brown@mpec.co.uk</a>> wrote:<br>
><br>
> >Tycho,<br>
> ><br>
> >Thanks for your help.<br>
> ><br>
> >The kernels were in fact different versions, though I’m not sure how I got into that state! So they’re now both running 3.19.0.<br>
> ><br>
> >Now, I at least receive the same error when migrating in both directions;<br>
> ># lxc move host2:test host1:test2<br>
> >error: Error transferring container data: restore failed:<br>
> >(00.008103) 1: Error (mount.c:2030): Can't mount at ./dev/.lxd-mounts: No such file or directory<br>
> ><br>
> ># lxc move host1:test1 host2:test1<br>
> >error: Error transferring container data: restore failed:<br>
> >(00.008103) 1: Error (mount.c:2030): Can't mount at ./dev/.lxd-mounts: No such file or directory<br>
> ><br>
> ><br>
> ><br>
> ><br>
> >The backing store is the default (directory based). However, on host2 the /var/lib/lxd/containers directory is a symlink to an ext3 mount. On host1 they’re on ext4, is that likely to cause any issues?<br>
> ><br>
> >The strange thing is, [randomly] the live move DOES succeed. I’ve definitely migrated a clean [running] container about 3 times from host2 to host1, but then when I try again with a new container it fails. This even worked before I updated the kernel. However, I can’t seem to find specific steps to replicate the successful move. I’ve never succeeded in migrating the same container back from host1 to host2 without stopping it. This is what is concerning me the most, I would expect either permanent failure or permanent success. I keep gaining false hope because the first time I migrated a container after updating the kernel it worked, so I thought, problem solved! But then I couldn’t migrate another :(<br>
> ><br>
> >-- Jamie<br>
> ><br>
> ><br>
> ><br>
> >05/11/2015, 16:58, "lxc-users on behalf of Tycho Andersen" <<a href="mailto:lxc-users-bounces@lists.linuxcontainers.org">lxc-users-bounces@lists.linuxcontainers.org</a> on behalf of <a href="mailto:tycho.andersen@canonical.com">tycho.andersen@canonical.com</a>> wrote:<br>
> ><br>
> >>Hi Jamie,<br>
> >><br>
> >>Thanks for trying it out.<br>
> >><br>
> >>On Thu, Nov 05, 2015 at 11:39:43AM +0000, Jamie Brown wrote:<br>
> >>> Hello again,<br>
> >>><br>
> >>> Oddly, I've now re-installed the old server and configured it identically to before (except now using RAID) and tried migrating a container back and I am getting a different failure;<br>
> >>><br>
> >>> # lxc move host2:test host1:test<br>
> >>><br>
> >>> error: Error transferring container data: restore failed:<br>
> >>> (00.007414) 1: Error (mount.c:2030): Can't mount at ./dev/.lxd-mounts: No such file or directory<br>
> >>> (00.026443) Error (cr-restore.c:1939): Restoring FAILED.<br>
> >>><br>
> >>> The container appears in the remote container list whilst moving, but then after failure it is deleted and it is in the STOPPED state on the source host.<br>
> >><br>
> >>Right, the restore failed, so the container had already been stopped<br>
> >>from the dump, so it was stopped on the target. What we should really<br>
> >>do is leave it in a frozen state after the dump, and once the restore<br>
> >>succeeds then we can kill it. Hopefully that's something I can<br>
> >>implement this cycle.<br>
> >><br>
> >>As for the actual error, sounds like the target LXD didn't have<br>
> >>shmounts but the source one did. Are they using different backing<br>
> >>stores? What version of LXD are they?<br>
> >><br>
> >>><br>
> >>> Here's the output from the log, not sure how much is relevant to the migration attempt.<br>
> >>><br>
> >>> # lxc info --show-log test<br>
> >>> ...<br>
> >>> lxc 1446723150.396 DEBUG lxc_start - start.c:__lxc_start:1210 - unknown exit status for init: 9<br>
> >>> lxc 1446723150.396 DEBUG lxc_start - start.c:__lxc_start:1215 - Pushing physical nics back to host namespace<br>
> >>> lxc 1446723150.396 DEBUG lxc_start - start.c:__lxc_start:1218 - Tearing down virtual network devices used by container<br>
> >>> lxc 1446723150.396 WARN lxc_conf - conf.c:lxc_delete_network:2939 - failed to remove interface '(null)'<br>
> >>> lxc 1446723150.396 INFO lxc_error - error.c:lxc_error_set_and_log:55 - child <10499> ended on signal (9)<br>
> >>> lxc 1446723150.396 WARN lxc_conf - conf.c:lxc_delete_network:2939 - failed to remove interface '(null)'<br>
> >>> lxc 1446723295.520 WARN lxc_cgmanager - cgmanager.c:cgm_get:993 - do_cgm_get exited with error<br>
> >>> lxc 1446723295.522 WARN lxc_cgmanager - cgmanager.c:cgm_get:993 - do_cgm_get exited with error<br>
> >>><br>
> >>><br>
> >>> If I try to migrate a container in the reverse direction, I get a similar error;<br>
> >>><br>
> >>> # lxc move host1:test1 host2:test1<br>
> >>> error: Error transferring container data: restore failed:<br>
> >>> (00.001093) Error (cgroup.c:1204): cg: Can't mount controller dir .criu.cgyard.aOuQtF/net_cls: No such file or directory<br>
> >><br>
> >>This is probably because the kernel on host1 is newer than the<br>
> >>kernel on host2 and has net_cls cgroup support where as host2's<br>
> >>doesn't.<br>
> >><br>
> >>Tycho<br>
> >><br>
> >>><br>
> >>><br>
> >>><br>
> >>> Any ideas?<br>
> >>><br>
> >>> -- Jamie<br>
> >>><br>
> >>><br>
> >>><br>
> >>> On 05/11/2015, 08:05, "lxc-users on behalf of Jamie Brown" <<a href="mailto:lxc-users-bounces@lists.linuxcontainers.org">lxc-users-bounces@lists.linuxcontainers.org</a> on behalf of <a href="mailto:Jamie.Brown@mpec.co.uk">Jamie.Brown@mpec.co.uk</a>> wrote:<br>
> >>><br>
> >>> >Thanks Tycho, installing CRIU solved the problem;<br>
> >>> ><br>
> >>> ># apt-get install criu<br>
> >>> ><br>
> >>> >Should this package not be included as a dependency for LXD, or at least provide a meaningful warning if the package isn’t available? It seems odd to advertise out-the-box live migration in LXD, but then have to install another package to provide it.<br>
> >>> ><br>
> >>> >Is this in the documentation anywhere?<br>
> >>> ><br>
> >>> >Thanks again.<br>
> >>> ><br>
> >>> >-- Jamie<br>
> >>> ><br>
> >>> ><br>
> >>> ><br>
> >>> ><br>
> >>> >On 04/11/2015, 16:47, "lxc-users on behalf of Tycho Andersen" <<a href="mailto:lxc-users-bounces@lists.linuxcontainers.org">lxc-users-bounces@lists.linuxcontainers.org</a> on behalf of <a href="mailto:tycho.andersen@canonical.com">tycho.andersen@canonical.com</a>> wrote:<br>
> >>> ><br>
> >>> >>On Wed, Nov 04, 2015 at 01:48:44PM +0000, Jamie Brown wrote:<br>
> >>> >>> Greetings all.<br>
> >>> >>><br>
> >>> >>> I’ve been using LXD in a development environment for a few weeks and so far very impressed,<br>
> >>> >>> I can see a really bright future for this technology!<br>
> >>> >>><br>
> >>> >>> However, today I thought I’d try out the live migration, based on the following guide;<br>
> >>> >>> <a href="https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/" rel="noreferrer" target="_blank">https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/</a><br>
> >>> >>><br>
> >>> >>> I believe I have followed the steps correctly, however when I run the move command, I<br>
> >>> >>> receive the following output;<br>
> >>> >>><br>
> >>> >>> # lxc move host1:test host2:test<br>
> >>> >>> error: Error transferring container data: checkpoint failed:<br>
> >>> >>> Problem accessing CRIU log: open /tmp/lxd_migration_899480871/dump.log: no such file or directory<br>
> >>> >>><br>
> >>> >>> The file it is referring to above doesn't exist. However, there are other lxd_migration_*<br>
> >>> >>> directories with different numbers appended. Each time I attempt the migration a new directory<br>
> >>> >>> is created (e.g. lxd_migration_192965652), but there is no dump.log in there.<br>
> >>> >>><br>
> >>> >>> The migration doesn't create a log file as per the guide above in;<br>
> >>> >>> /var/log/lxd/test/migration_{dump|restore}_.log<br>
> >>> >>><br>
> >>> >>> Steps I've taken;<br>
> >>> >>><br>
> >>> >>> - Copied all profiles from host1 to host2<br>
> >>> >>> - Added the migratable profile to the container<br>
> >>> >>> - Removed lxcfs package (on both hosts)<br>
> >>> >>> - Added the remote HTTPS hosts for both the local and remote hosts<br>
> >>> >>><br>
> >>> >>> Both hosts are running Ubuntu 14.04.3 LTS (x64) with LXD version 0.21.<br>
> >>> >>><br>
> >>> >>> The only difference I can tell between my hosts and the guide is that the 'migratable'<br>
> >>> >>> profile (which came out-the-box with my LXD installation) doesn't contain the autostart<br>
> >>> >>> entries as in the guide above;<br>
> >>> >>><br>
> >>> >>> # lxc profile show migratable<br>
> >>> >>> name: migratable<br>
> >>> >>> config:<br>
> >>> >>> raw.lxc: |-<br>
> >>> >>> lxc.console = none<br>
> >>> >>> lxc.cgroup.devices.deny = c 5:1 rwm<br>
> >>> >>> lxc.seccomp =<br>
> >>> >>> security.privileged: "true"<br>
> >>> >>> devices: {}<br>
> >>> >>><br>
> >>> >>><br>
> >>> >>> Any help would be much appreciated!<br>
> >>> >><br>
> >>> >>Have you installed CRIU? lxc info --show-log test probably has more<br>
> >>> >>info about what failed, but my guess is that it can't find CRIU if you<br>
> >>> >>haven't installed it.<br>
> >>> >><br>
> >>> >>Tycho<br>
> >>> >><br>
> >>> >>> Thank you,<br>
> >>> >>><br>
> >>> >>> Jamie<br>
> >>> >>><br>
> >>> >>> _______________________________________________<br>
> >>> >>> lxc-users mailing list<br>
> >>> >>> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> >>> >>> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
> >>> >>_______________________________________________<br>
> >>> >>lxc-users mailing list<br>
> >>> >><a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> >>> >><a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
> >>> >_______________________________________________<br>
> >>> >lxc-users mailing list<br>
> >>> ><a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> >>> ><a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
> >>> _______________________________________________<br>
> >>> lxc-users mailing list<br>
> >>> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> >>> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
> >>_______________________________________________<br>
> >>lxc-users mailing list<br>
> >><a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> >><a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
> >_______________________________________________<br>
> >lxc-users mailing list<br>
> ><a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> ><a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
> _______________________________________________<br>
> lxc-users mailing list<br>
> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a></div></div></blockquote></div><br></div>