rails paperclip and passenger `is not recognized by the 'identify' command`

Question

When I upload a photo, my model fails validation, err well even without any validations I'm returned this error:

/tmp/stream20100103-13830-ywmerx-0 is not recognized by the 'identify' command. and     
/tmp/stream20100103-13830-ywmerx-0 is not recognized by the 'identify' command.

I'm confident this is not related to ImageMagick because I've removed any image processing from the uploading, also I've tried uploading different mime types, like .txt files and the such.

Additionally, I found something that may work. A blog post claims that putting the following in my environment (in this case development.rb)

Paperclip.options[:command_path] = "/opt/local/bin"

reinstalling ImageMagick... just to see if that remedies anything. — JP Silvashy, Jan 03 '10 at 19:59
This is related to ImageMagick, but could you also include the paperclip statements that you have in your model? The `command_path` option needs to point ot the location where `identify` is installed. From the command line, you can determine this with `which identify`. — Ryan McGeary, Jan 03 '10 at 20:11
Bleh, you are right Ryan (again), if you want to answer you get a big green checkmark. — JP Silvashy, Jan 03 '10 at 20:34

score 49 · Accepted Answer · answered Jan 03 '10 at 21:45

49

This is related to ImageMagick. The command_path option needs to point to the location where identify is installed. From the command line, you can determine this with which identify.

$ which identify
/some/path/to/identify

Afterwards, set command_path to that path (in config/environments/development.rb):

Paperclip.options[:command_path] = "/some/path/to"

answered Jan 03 '10 at 21:45

Ryan McGeary

235,892
13
95
104

I have almost exactly this problem, except for one thing: the error just appears when I'm trying to attach videos! Any ideas? :( – Erik Escobedo Aug 31 '10 at 19:14
hmm... which identify doesn't work for me. Any reason why it wouldn't? – sscirrus Nov 02 '10 at 03:13
sscirrus, Make sure ImageMagick is installed and in your PATH. – Ryan McGeary Nov 03 '10 at 00:31

score 15 · Answer 2 · edited Nov 15 '12 at 00:35

15

This can also be caused by using fairly old versions of Paperclip (for example, version 2.4.x) with newer, incompatible versions of the Cocaine gem.

edited Nov 15 '12 at 00:35

greeness

15,956
5
50
80

answered Nov 15 '12 at 00:05

Bill Lipa

2,039
1
19
11

Thanks, that was a BIG help! – Zubin Apr 24 '13 at 04:23
3

Adding gem "cocaine", "~> 0.3.2" in the Gemfile, and running bundle update cocaine solved the issue for me – Shai Coleman Jun 13 '13 at 09:31
paperclip 2.3.4 exactly with cocaine 0.4.2. paperclip 2.3.16 fails. – TomDunning Aug 26 '13 at 16:24

score 6 · Answer 3 · edited Jun 14 '13 at 21:26

6

I was able to resolve this by doing the following:

brew uninstall imagemagick
brew install imagemagick

edited Jun 14 '13 at 21:26

wisew

2,672
3
23
30

answered Sep 04 '12 at 22:24

Mark Ross

61
1
1

score 4 · Answer 4 · answered Jul 23 '11 at 23:10

This happened to me when I upgraded OS X to Lion.

Solved it by...

do a brew list to see all packages you have and save this somewhere
uninstalling homebrew (see 'Uninstallation' on this page https://github.com/mxcl/homebrew/wiki/Installation )
reinstall homebrew with the usual

ruby -e "$(curl -fsSL https://raw.github.com/gist/323731)"
reinstalling all packages brew install ghostscript brew install imagemagick etc for any others you have

Note, before ghostscript would reinstall I had to apply the suggestion found here: https://github.com/mxcl/homebrew/issues/6381

brew edit ghostscript

Then add the def patches block to the bottom of the Ghostscript class:

class Ghostscript < Formula
    .... existing code here ....

    def patches
        { :p0 => 'http://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/print/ghostscript/patches/patch-ak' }
    end
end

The above patch may be merged in by the time you read this.

After that imagemagick detected jpegs correctly again.

TL;DR completely uninstall and reinstall homebrew, ghostscript (with patch for Lion), and imagemagick

score 3 · Answer 5 · edited Sep 01 '21 at 05:45

3

I got it working by installing brew, Link

And then i typed:

brew install imagemagick

and after that

gem install rmagick

Then I just deleted the option paths (Paperclip.options[:command_path] = "...") that I typed in manually in environment/development.rb and initialize/paperclip.rb

Added rmagick to gem file. Restarted the server and it worked like a charm!

edited Sep 01 '21 at 05:45

Glorfindel

21,988
13
81
109

answered Mar 22 '11 at 22:13

Philip

6,827
13
75
104

score 2 · Answer 6 · answered May 13 '10 at 14:11

This worked fromhttp://arglebargle.posterous.com/path-environment-variable-for-rails-using-pas

Put something like this in the VirtualHost (or wherever passenger is set up):

SetEnv PATH /opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/mysql/bin

score 1 · Answer 7 · answered Oct 09 '12 at 21:11

1

You will also get this error message if you try to upload a file that contains colons in it's name as of the latest version.

answered Oct 09 '12 at 21:11

Ninjaxor

876
12
27

score 1 · Answer 8 · answered Jan 16 '13 at 10:41

Usually it helps to specify the path to the identify command with..

Paperclip.options[:command_path] = "/your/path/to/identify"

..as the others mentioned. But the problem can also occur if there is a version mismatch, I recently updated the Ruby-on-Rails Version of an application (to Rails 3.1.10), but forgot to update the paperclip gem. After I updated the paperclip version to 2.8.0 it worked again.

score 1 · Answer 9 · answered Mar 19 '10 at 19:36

To add one more potential solution that I haven't seen discussed much: ldconfig.

I had the same problem that I just spent a day and a half tracking down. I properly reinstalled ImageMagick from source with the additional png and jpeg support, I added LD_LIBRARY_PATH and DYLD_LIBRARY_PATH to the environment variables, I set the :command_path option for Paperclip in my production environment config. Although the ImageMagick commands worked from the command line, nothing fixed my Paperclip problem.

Finally after seeing ldconfig mentioned in passing, I tried that on a whim, and it worked.

sudo ldconfig

I may have been able to accomplish the same thing by restarting apache or the hardware, but I wasn't in a position to do that on my own.

score 0 · Answer 10 · answered Dec 12 '12 at 13:54

Just to say, you can also have this error message for what it means.

In my case the file size was 0 bytes length because I forgot to flush it after writing it from a Zip, and passing this resource to Paperclip.

It might be interesting to check that you can actually open the file with your preferred viewer before reading the other answer from this thread :)

score 0 · Answer 11 · answered Apr 23 '13 at 10:22

If you're a mac user and this has only been a problem since updating your OS to 10.8 then it could be an X11 issue, as outlined here http://support.apple.com/kb/HT5293

identify ~/path/to/image

Was not working for me even after trying all the above fixes. I installed XQuartz from http://xquartz.macosforge.org/landing/ and now it is working again.

May help others out too...

score 0 · Answer 12 · answered May 25 '13 at 03:25

0

that also happened to me, i tried all the method that are mentioned above. I just change the paperclip version , then everything works fine.

answered May 25 '13 at 03:25

user1611237

123
1
5
14

score 0 · Answer 13 · answered Oct 11 '13 at 17:31

I had this issue when using OSX + MAMP + Passenger + Paperclip and after setting the command_path and ensuring imagemagick was properly installed via brew, properly setting the temp and upload directories for passenger to something writable, it still wouldn't work!

The solution was to edit the envvars file for MAMP in /Applications/MAMP/Library/bin/envvars and comment out the export DYLD_LIBRARY_PATH line.

That is, change the line that says

export DYLD_LIBRARY_PATH

to

# export DYLD_LIBRARY_PATH

Then restart MAMP and feel the elation when your images are properly uploading/resizing.

score 0 · Answer 14 · answered May 18 '11 at 18:47

if your are trying to upload a video, then probably, 'identify' tries to delegate the work to ffmpeg. example

   identify Desktop/00-ScalingRails-Introduction.mp4      [alaa@Zero>/home/alaa]
   identify: delegate failed `"ffmpeg" -v -1 -vframes %S -i "%i" -vcodec pam -an -f rawvideo -y "%u.pam" 2> "%Z"' @ error/delegate.c/InvokeDelegate/1061.
   identify: unable to open image `/tmp/magick-XXHF4ImT.pam':  @ error/blob.c/OpenBlob/2498

in this example, installing ffmpeg removed the error message from the list of validation errors

rails paperclip and passenger `is not recognized by the 'identify' command`

14 Answers14

Linked