I'm using the latest .dev version.

I tried uploading a 62 MB .xml file, but that failed with a nondescript error message, so I tried using drush, using the same xml file I'd uploaded via the interface: drush wordpress-migrate-import private://wordpress/blog-export-filename-goes-here.xml

That went through the authors, categories, and tags okay, but blog entries were another story.

Memory usage is 255.01 MB (85% of limit 300 MB), resetting statics [warning]
Memory usage is now 208.7 MB (70% of limit 300 MB), reclaimed enough, continuing [warning]
Memory usage is 255.02 MB (85% of limit 300 MB), resetting statics [warning]
Memory usage is now 244.67 MB (82% of limit 300 MB), not enough reclaimed, starting new batch [warning]
Imported 0 in 1779.8 sec (276/min) - continuing with 'BlogEntry' [ok]
Segmentation fault

Should I really need more than 300 MB for this, or is something else going on here?

Comments

mikeryan’s picture

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

It shouldn't be using that much memory, I suspect a memory leak in some contrib module you're using (something's caching stuff in static variables rather than using drupal_static()) - are you using anything out of the ordinary?

mikeryan’s picture

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

spacegoat1701 commented

I am using Rules to assign some fields upon import. I'll try disabling them and then report back.

spacegoat1701’s picture

spacegoat1701 commented

I think I addressed the memory issue, but now I'm getting this error a bunch of times:

WD node: PDOException: SQLSTATE[23000]: Integrity constraint [error]
violation: 1062 Duplicate entry '' for key 'uri': INSERT INTO
{file_managed} (filesize, status, timestamp) VALUES
(:db_insert_placeholder_0, :db_insert_placeholder_1,
:db_insert_placeholder_2); Array
(
[:db_insert_placeholder_0] => 0
[:db_insert_placeholder_1] => 1
[:db_insert_placeholder_2] => 1344207656
)
in drupal_write_record() (line 7013 of
/www/includes/common.inc).

Afterward, I received this error a few times:

WD node: MigrateException: array_flip(): Can only flip STRING and [error]
INTEGER values!
File /www/catodev2/htdocs/includes/entity.inc, line 178 in
MigrationBase->errorHandler() (line 519 of
/www/sites/all/modules/migrate/includes/base.inc).

And then the process ended with

File size limit exceeded.

Although, the new items seemed to import okay, except for Attachment, which was stuck at importing.

The post and upload max sizes are 200 MB in php.ini.

spacegoat1701’s picture

spacegoat1701 commented

I don't know whether this is related, but trying to import via the GUI just doesn't seem to work for me. Each time, I get an error like this:

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

I'm fine with using drush, but then I can't tell the command I want to update existing items as well.

Is there any way to get more detailed error messages? "File size limit exceeded." doesn't help anything, because as far as I know, no files are anywhere near 200 MB; why not tell me which file and blog post triggered the error? And that Ajax message is completely useless.

Edit: I checked Apache error logs; nothing there.

spacegoat1701’s picture

spacegoat1701 commented

Okay, I figured out the drush command to use for updating; I had to look in the migrate drush file instead of appending an option to the Wordpress Migrate command as seemed intuitive to me: drush migrate-import BlogEntry --update

I received a Segmentation Fault error at the end but it still completed.

So I guess even though Wordpress Migrate is a bit like a noisy baby, at least for me, it's basically working if I use drush for everything (even though I know you're "supposed" to use the GUI).

mikeryan’s picture

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

muschpusch commented
Status: Closed (cannot reproduce) » Active

I get the same error like in #4 but on command line my dblog shows:

Unable to render media from {"type":"media","view_mode":"media_large","fid":"13220","attributes":[{"class":"media-image","typeof":"foaf:Image","style":"","width":"500","height":"704"}]}. Error: Could not load media object

On admin/content/migrate/*BlogAttachment i get this warning:

'"path" was used as destination field in "" mapping but is not in list of destination fields'

I tried multiple versions of media and wordpress_migrate.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Closed (cannot reproduce)

In the future, please don't reopen old closed issues, particularly when not on-topic - you're asking about different messages, which deserve a distinct issue.

In the first case were you rolling back (please open a fresh issue to continue this)? These messages can occur because attachments get rolled back first, then when nodes are loaded to be deleted the dangling references to the deleted attachments cause errors. Everything should end up properly deleted.

In the second case, it sounds like you don't have the path module enabled. No harm done, the field mapping simply won't be used.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Issue summary: View changes

fixed standin exported xml name