Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi
Trying to migrate my D6 website to a fresh D8
Got
An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /D8/batch?id=2&op=do_nojs&op=do
StatusText: Internal Server Error
ResponseText:
In my log reports, some lines like
Location http://localhost/D8/batch?_format=json&id=2&op=do&op=do_nojs
and
Referrer http://localhost/D8/batch?id=2&op=start
and
Message Import of Drupal 6 field values failed
Hum. Doesn't help me to understand what's going on :(
Any idea/help ?
Thanks
Best regards.
D.
Comment | File | Size | Author |
---|---|---|---|
#14 | logs-migrate.txt | 24.81 KB | dbourrion |
Comments
Comment #1
mikeryanThat's true, the batch API does not provide much good info when things go wrong (the D7 doc page https://www.drupal.org/node/1806824 will still largely apply in D8). Could you try it in drush instead? Something like
Comment #2
dbourrion CreditAttribution: dbourrion commentedHi
Using drush, I got this
Hum ;)
Seeing that
I remember a detail : my d6 tables are in a database with some other stuff.
The specific D6 tables are using a prefix, that is "drupal"
Where can one put that in the Drush line command ?
Comment #3
mikeryanDon't forget to set the status back to "Active" when responding to a "Postponed (maintainer needs more info)".
Comment #4
mikeryanWe use drush_convert_db_from_db_url() on that URL parameter, and it does not appear to support a way to pass prefixes.
Did you provide the prefix (under Advanced Options) when trying through the UI?
Comment #5
mikeryanComment #6
mikeryanre: drush - looks like the protocol is to have a --db-prefix option in this case.
Comment #7
mikeryanThe prefix option will be added at #2533190: Add prefix option to drush migrate-upgrade.
Comment #8
mikeryan@dbourrion: There's a patch adding --legacy-db-prefix to drush migrate-upgrade at https://www.drupal.org/node/2533190#comment-10117790 - can you give it a try and let me know if it works for you?
Thanks.
Comment #9
dbourrion CreditAttribution: dbourrion commentedHi
Patching looks ok according to that :
Then i launch
I got that error (things are going well before, so I don't put all the logs here)
Comment #10
dbourrion CreditAttribution: dbourrion commentedComment #11
dbourrion CreditAttribution: dbourrion commentedPatch #19 here help the "Error: Call to a member function uuid() on null " disappearing.
Upgrde then stops with
Any help welcome ;)
D.
Comment #12
mikeryanOK, let's start with the first error, since dependency issues tend to cascade:
So, it appears that somehow the d6_field_instance migration did not get created from the template. This implies its source or destination requirements were not fulfilled. On the source side, it requires the "content" module (i.e., CCK) to be enabled in your D6 source database - it tells that by looking status=1 in the system table for that module. I note earlier you said "the specific D6 tables are using a prefix" - perhaps the system table is not using a prefix, thus not visible (although I'd expect more dramatic errors, earlier, if that were the problem...). I'm not seeing an issue with the destination requirements...
Comment #13
mikeryanComment #14
dbourrion CreditAttribution: dbourrion commentedOh. For that error
that's because, like in a D6->D7 migration, I disabled all the D6 Module.
After renabling them, that error disappears but a lot of other errors comes out.
I put the drush output in the join txt files.
And I'm gonna try to understand some of them ;)
Comment #15
dbourrion CreditAttribution: dbourrion commentedComment #16
mikeryanThere's been a lot of rearranging/refactoring in the migrate world the last couple of weeks, could you update both D8 core and migrate_upgrade and try again?
Thanks.
Comment #17
dbourrion CreditAttribution: dbourrion commentedHi :)
I have made a drush up in order to have everything up tp date.
I then had to apply that patch https://www.drupal.org/node/2533190#comment-10117790 to get --legacy-db-prefix
Launching drush migrate-upgrade --legacy-db-url=mysql://root:daniel@localhost/D6database --legacy-db-prefix=drupal --legacy-root=http://localhost/drupal -d
I got
as in that issue https://www.drupal.org/node/2547179
Best regards
D.
Comment #18
dbourrion CreditAttribution: dbourrion commentedComment #19
mikeryan"with message 'You have requested a non-existent service "migrate.migration_builder".' " seems to indicate you don't have the latest code - maybe drush up gets you the latest beta, as opposed to the latest -dev with the builder support? Yes, drush help up does indicate "updating to latest recommended releases"... You need the latest -dev build or pull 8.0.x from git.
Comment #20
dbourrion CreditAttribution: dbourrion commentedHi :)
After updating to the much recent dev version of D8 and other modules, the #17 error was gone but I got again a
error (see inside here, #11)
But the patch I used to apply to correct that error doesn't work anymore, as I tell it there
So I'm stuck again.
Sorry for all that "it is not working" stuff :(
Comment #21
dbourrion CreditAttribution: dbourrion commentedComment #22
dbourrion CreditAttribution: dbourrion commentedHi :)
After applying patch #28 here to solve the
error, the migrate starts again.
But drush crash again, with errors (see below).
I'm gonna try to understand some errors (that D6 to D8 migration stuff doesn't so easy I thought it was, in fact ;) )
Best regards
D.
Comment #23
dbourrion CreditAttribution: dbourrion commentedI've used that patch to try to go further ; looks working until
Still seeking ;)
Comment #24
quindio CreditAttribution: quindio commentedI got the same error using a clone of D8 as of this morning - Thanks
Comment #25
mikeryanI believe the dependency problems this issue was originally about were resolved a while ago. Other problems, if they're still being seen, should have their own issues - most likely in the core queue, since they relate to the actual execution of the migrations rather than the UI.