Hello,
I have used yamm module to migrate a bunch of content from a Drupal server to another one.
It worked pretty flawlessly except in two respects: content location was not handled correctly and the job is perpetually in state "running".

On the command line (on the yamm client side) I see the php process running and a defunct father project (don't know if it's correct):
# ps -ef | grep php
www-data 9503 1 0 16:32 ? 00:00:02 php sites/all/modules/datasync/datasync_run.php www.localtest.hamatole
www-data 9907 9503 7 17:03 ? 00:00:00 [php]

This is the result for job's monitoring page (on the yamm client side) :

Job ID Job type Job status Job phase Next job phase Time phase started Time phase completed
3 yamm_sync Running syncAllContent datasync_next 01/12/2010 - 11:29

I've enabled debugging and I saw many usefull messages on the watchdog that shows how location information were handled by yamm:

workflow 01/12/2010 - 11:30 State of Events Visiones set to need to reviews admin view
location 01/12/2010 - 11:30 Conserving lid 8465 due to uniqueness. admin
yamm 01/12/2010 - 11:30 Entity parser got 0 dependencies admin
yamm 01/12/2010 - 11:30 Insert node 10326 admin
workflow 01/12/2010 - 11:30 State of Events Piemonte Industria. ... admin view
location 01/12/2010 - 11:30 Conserving lid 8466 due to uniqueness. admin
yamm 01/12/2010 - 11:30 Entity parser got 0 dependencies admin
yamm 01/12/2010 - 11:30 Insert node 10325 admin
.... (continues)

Looking at location and location_instance tables I found that yamm was able to create the correct location_instance entries (to create acoorelation between a location and a node) but didn't insert the location itself.
Fortunately I was able to create the location table entries using sql import on the db and everything worrked in the end.
However I seems that location module poses some problems to YAMM.

Hope it can help you.

I think the module is very promising.

Regards.

Comments

pounard’s picture

Thanks for reporting the bug.

We actually run the module on production sites, and we don't have the perpetual running state bug. Is there any fatal error or exception that happens during the sync job run?

Also, what version of DataSync module do you use? We actually patched it a lot, and submit the patches to module maintener, but we could actually have forgotten some (I don't think so, but this is a eventuality). It would also help if you gives us what database layer you are using, we know that DataSync can't work with 'mysqli' we had to force all mysql databases to use the 'mysql' layer.

Another question about this, after sync is done, is there some php processes in 'defunct' state? It seems that we had a lot of them using DataSync (we don't have anymore but thanks to some patches again).

For the content location module, I'll test it as soon as I have time, but it'll help a lot to know a bit more about your Drupal site configuration and the steps to reproduce the bug.

pounard’s picture

Status: Active » Postponed (maintainer needs more info)
pounard’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Very outdated module.