I'm having trouble with UI imports failing when one migration is too big to finish in one batch, after the first batch we get a useless Batch API error:

An AJAX HTTP request terminated abnormally. Debugging information follows. Path: /batch?id=901&op=do StatusText: ResponseText: ReadyState: 4

Debugging Batch API is a royal PITA...

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

Running with Javascript disabled works just fine. And it works fine with migrate_example_baseball. Where I'm seeing is importing WordPress WXR files using wordpress_migrate, so maybe the problems there (or the problem is with XML imports...). Is #1508154: An AJAX HTTP request terminated abnormally. Debugging information follows. Path: /batch?id=22&op=do StatusText: ResponseText: Re just a coincidence?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Postponed (maintainer needs more info)

Anyone else having this? It doesn't happen on another environment I have, so maybe I've got something funky going on in my local dev environment...

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
ioanmar’s picture

ioanmar commented
Version: 7.x-2.x-dev » 7.x-2.4
Status: Closed (cannot reproduce) » Postponed (maintainer needs more info)

That's exactly what I'm also facing.

After fixing the exported WP XML I start the mogration process but only author, categories and tags are imported. As soon as node import begins, the process is interrupted and I get the exact error you mention.

Changed php.ini configurations (max_execution_time etc etc) and tried the mogration with js disabled but it seems to me that the process is not yet initialized.

Were you able to fix this problem and migrate successfully?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Late response - no. At the moment I don't have any reproducible cases, and even when I did have a semi-reproducible case I could not track down the cause, the Batch API Javascript just will not yield any useful information on why it failed.

sause’s picture

sause commented

That's the same problem with me.
I tried set wordpress_migrate_import_method, disable javascript, change $base_url, import from file. None of these worked.
Does anyone have any other suggestion for this?

kenyan’s picture

kenyan commented

So then it is a batch API issue?
I'm having the same problem doing feeds import of a very basic csv file for node creatiion. There are no errors etc in the partially imported content but I've now resorted to importing in batches. Should this not be the function of batch though I wonder to myself....

scottatdrake’s picture

scottatdrake commented

I'm getting the same error when trying to migrate 300,000 users on our DEV server (source is a legacy MySQL db).... but I can't reproduce locally. It was working just the other day. Not sure what changed. We have other migrations defined that will run forever without error.

Migrate 7.x-2.5
Drupal 7.16

It was doing 50-60 records before throwing the error. Increased the max_execution_time... now pulling 110-ish records before error.