Load errors when upgrading from 6.3 to 6.4

Help
1

Enonic version: 6.3
OS: Debian Jessie

We get several errors when performing load (after upgrade from 6.3 to 6.4) into 6.4, they all take the form

[/SOME/PATH] Missing node source, expected at /SOME/PATH

Any idea what the problem could be ?

2

Enonic XP 6.3.0 has a problem with the export/dump of manually sorted content.
If you are using 6.3.0, you should first upgrade to 6.3.1 (No need to dump & load between 6.3.0 and 6.3.1).

1 Like
3

I still get error when running upgrade command:

Unexpected error: Failed to get children of path ./dump_23.02/cms-repo/draft/content/[SOME_PATH]]

The upgraded folder is one third in size of the original. Upgraded folder also gets named [ORIGINAL_NAME]_upgraded_6.0.0 even though the original dump is from 6.3.1.

4

Hi Petter,

You don’t need to do the dump/upgrade, only use the export feature of the 6.3.1 toolbox (important, 6.3.0 had major errors in export format). Then go to 6.4 and import it (6.4.0 had some minor issues, a 6.4.1 will soon be released, no need to upgrade between these two though).

  1. Do export - http://xp.readthedocs.org/en/6.3/operations/export.html
  2. Do import - http://xp.readthedocs.org/en/6.4/operations/export.html#import
5

Any reason why you describe dump/load as preferred upgrade steps in your doc ?

Is there a way to make the export command export all repos, or do I have to export each one (I only know of cms-repo and system-repo, are there more ?) separately ?

6

Dump is an export of all repos

  1. First switch your installation from 6.3.0 to 6.3.1
  2. Dump the data
  3. Go to your clean 6.4.0 installation and upgrade the dump using this 6.4.0 installation (You will see that the folder will have a name [ORIGINAL_NAME]_upgraded_6.4.0 and not [ORIGINAL_NAME]_upgraded_6.0.0)
  4. On your 6.4.0 installation, load the upgraded dump

More detailled steps: http://xp.readthedocs.org/en/6.4/appendix/upgrade/index.html

But I am interested by your error “Failed to get children of path ./dump_23.02/cms-repo/draft/content/[SOME_PATH]]”. What it means is that it fails to read the children files of the mentioned directory (Unfortunately it is not verbose enough, we do not see there reason of the failure). Could be some missing access permissions for example

1 Like
7

Nevermind my comment, I was not updated on the changes to the upgrade process between 6.3 and 6.4. Listen to gri =)