Application in container does not work after migration or restoration from backup.

Refers to:

  • Plesk for Linux

Created:

2016-11-16 12:41:59 UTC

Modified:

2016-12-21 19:00:19 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Application in container does not work after migration or restoration from backup.

Symptoms

  1. An application does not work inside container.

  2. Application was installed using application template.

  3. There are broken links to the files required for the correct work of the application, for example:

    ~# ls -la /vz/private/107/fs/root/usr/share/mysql-common/
    total 16
    drwsr-xr-x 3 root root 4096 Jun 11 2012 .
    drwxr-xr-x 145 root root 4096 Sep 24 13:35 ..
    drwxr-xr-x 2 root root 4096 Jun 11 2012 internal-use-only
    lrwxrwxrwx 1 root root 87 Sep 5 15:20 ._vzlnk_. -> ////ubuntu/10.04/x86_64/mysql-common_5.1.62-0ubuntu0.10.04.1_all/usr/share/mysql-common

    When listing from inside the container:

    ~# ls -al
    ...
    drwxr-xr-x 2 root root 4096 Sep 24 12:20 mime-info
    drwxr-xr-x 2 root root 4096 Jun 11 2012 misc
    d????????? ? ? ? ? ? mysql-common
    drwxr-xr-x 2 root root 4096 Feb 2 2010 nano
    drwxr-xr-x 2 root root 4096 Nov 6 2009 ncat

Cause

Application template version is mismatched:

    ~# ls /vz/template/ubuntu/10.04/x86_64/
...
mysql-common_5.1.67-0ubuntu0.10.04.1_all
...

while the link points to version 5.1.62 :

    lrwxrwxrwx   1 root root   87 Sep  5 15:20 ._vzlnk_. -> ////ubuntu/10.04/x86_64/mysql-common_5.1.62-0ubuntu0.10.04.1_all/usr/share/mysql-common

Resolution

The described situation can arise only in 2 cases:

  • when the container is migrated

    In order to avoid the problem when migrating containers, please use the this article to prepare containers for migration.If all instructions from the article are implemented, all necessary templates will be migrated as well.

  • when the container is restored from the backup on a different node

    If this situation arises after a backup restore on another node, the situation can be fixed using either of the following ways:

    • restore the container on the initial node, then follow the migration procedure;
    • try to repair the container (step 3 from this article).

    Do not forget to make sure to add the necessary repositories (for example, ubuntu 10.04 has reached End-of-Life, it is no longer officially supported, and the packages for EOL releases are moved from official repositories to http://old-releases.ubuntu.com/ ).

Have more questions? Submit a request
Please sign in to leave a comment.