Locked step statuses sticking [#1076960]

So I've been digging through the code and trying to fix some issues with modules like the mm_flvtool2 which wasn't compatible with the new 2.x media mover api.

I thought I had media mover set up and running smoothly when I had two cck files from individual nodes go through my entire configuration to convert from wmv to flv's with injected metadata. Everything ran smoothly without any errors but now that I started uploading and creating more nodes to hand off to media mover I am experiencing issues.

I am still running media mover manually by clicking the "run" link and it seems media mover does some of what it is intended to do but I am still a little confused on how media mover actually works with cron or what the point of drupal queue is since running either of these manually by accessing them directly from a browser doesn't seem to have any influence on whether media mover runs or not and hence why I am still using the "run" link.

I guess what I am really interested in knowing is how steps in a configuration are supposed to be handled by cron. In my current configuration I am having issues with steps getting stuck in the "lock" status and nothing happening afterward. I don't have any errors at all and the one file that does manage to go through the full configuration is created and works perfectly so I'm guessing this is a major bug that stills needs to be fixed in the dev version. I would like to help out but I'm not sure I fully understand the workflow of the module and with the limited documentation available I've been resorting to sticking my nose in the code and just dumping variable output to try and figure out exactly what's going on and guessing what is actually supposed to happen in order to try to hack up some fixes on my own.

Any ideas for what the problem is in this configuration (i've attached an image) :

Comment	File	Size	Author
	media_mover_stall.jpg	77.23 KB	edgji

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

arthurf CreditAttribution: arthurf commented 2 March 2011 at 04:25

I dug into this and figured out that a nice new feature in the API introduced a nasty bug that causes this. The mm_node module has all of its callbacks in include files and the media mover api handles this fine with the file attribute for the specific configuration. When a configuration is loaded, all of these includes are loaded as well.

However, when you're running from cron, the $step object is stored in the db and then is run at some later date. Since these $steps are already loaded the include files are not loaded during the cron/queue run - so when media mover checks to see if the call back exists it does not find it and the process stops.

Should be ready for testing again, sorry!