Configuration problem about pageflow HOT 4 CLOSED

Do you have the resque worker and scheduler running? These run the backgound-jobs to resize the images and process videos and audios.

We will try update the docs later.

For now, the discussion in this issue may help: #11

from pageflow.

Yes, I had a closer look on #11, but my worker and scheduler are both started and I think the processing works fine - to some part at least...

I get the properly resized images (thumbnail / medium / print / ...) in what I suspect to be the right folders, e.g.:

..amazonaws.com/testapp/mmm.local/image_files/processed_attachments/000/000/039/v1/thumbnail/2013-03-12_14.40.44.JPG

So it all looks pretty good from my point of view, only the image processing stops with "Fehler beim Verarbeiten" and no images show up in front- or backend.

I tried to figure out what this Fehler might be, but all I found in the development.log was:

E, [2014-05-13T00:02:12.127763 #2595] ERROR -- : Pageflow::ProcessImageFileJob - exception for Pageflow::ImageFile 39: 
#ActiveRecord::StatementInvalid: SQLite3::SQLException: cannot rollback - no transaction is active: rollback transaction

So I scanned through my server output and found this one

  SQL (4935.1ms)  UPDATE "pageflow_edit_locks" SET "updated_at" = '2014-05-12 21:59:22.034859' WHERE "pageflow_edit_locks"."id" = 24
SQLite3::BusyException: database is locked: UPDATE "pageflow_edit_locks" SET "updated_at" = '2014-05-12 21:59:22.034859' WHERE "pageflow_edit_locks"."id" = 24
Completed 500 Internal Server Error in 4946ms

ActiveRecord::StatementInvalid (SQLite3::BusyException: database is locked: UPDATE "pageflow_edit_locks" SET "updated_at" = '2014-05-12 21:59:22.034859' WHERE "pageflow_edit_locks"."id" = 24)

from pageflow.

Maybe the problem is with SQLite? It seems to have problems with concurrent writes.

We're using MySQL in production as well as development so we don't have much experience with SQLite errors, sorry.

I have updated the Getting started guide to use MySQL instead.

from pageflow.

Thanks a lot, that fixed it! As soon as I switched to MySQL, all problem are gone and it works like a charm.

from pageflow.