You can try activating ImageMagick warning definitions so you know what's going on with those error codes. There isn't any list of error codes for ImageMagick unfortunately.
Put this in your root .bashrc or whichever shell config you're using:
alias convert='convert -regard-warnings'
Or put that option -regard-warnings in the ezpublish config for ImageMagick (I'm not sure if this will work, but the previous way will definitely work).
Btw it could be that ImageMagick is using way too much memory/disk and bombs out as a result. You may want to try setting the limits with this: http://www.imagemagick.org/script/command-line-options.php#limit
Thanks for that. I don't think the problem is with size limitation, but with clustering. Images stored in the database are not found by imagemagick because it's trying to open the image on the filesystem, rather than through a http request (which would be caught by the Apache config).
I imagine this has been resolved in 4.0? We're currently on 3.9.
In my case it was caused by a clash of ownership after copying image files from one server to another. In the new install I noticed that any new images uploaded were owned by daemon.
I changed the existing images (which were not loading) to daemon:daemon and the problem went away.
Asking the dumb questions for your benefit
You must be logged in to post messages in this topic!