Error: spawn ENOENT while using GM in node

Question

When I try to resize an image like this:

 gm('public/uploads/1710410635.jpg') .resize(240, 240) .noProfile() .write('public/uploads/1710410635_t.jpg', function (err) { if (!err) console.log('done'); });

I get this error:

events.js:72 throw er; // Unhandled 'error' event ^ Error: spawn ENOENT at errnoException (child_process.js:945:11) at Process.ChildProcess._handle.onexit (child_process.js:736:34)

My file structure is as follows:

enter image description here

The code is executed in the postnewsitem.js file

why is this error occurring & how do I solve it ?

edit: GraphicsMagick works, proof:

enter image description here

Did you install GraphicsMagick? Also, what platform are you using? GM is only tested on Mac OS X and Ubuntu. — robertklep
– robertklep, Commented Apr 25, 2013 at 18:37
yes I have graphicsmagic 1.3.18 working on Lion OS X . ( Though it says: "imagemagick-6.8.0-10 already installed, it's just not linked", when trying to see if it is really installed.) — Olivier_s_j
– Olivier_s_j, Commented Apr 25, 2013 at 18:42
GraphicsMagick isn't the same as ImageMagick. You need to configure gm to get it to work with ImageMagick. It looks like the gm module can't find the GM/IM binaries, they have to be somewhere in your $PATH I think. — robertklep
– robertklep, Commented Apr 25, 2013 at 18:48
I installed graphicsmagic instead now, though the error remains. ( If I type gm in the terminal I see that it is installed.) — Olivier_s_j
– Olivier_s_j, Commented Apr 25, 2013 at 18:53
off topic: @ojtwist , what IDE is the screenshot taken from ? — epeleg
– epeleg, Commented Jun 28, 2013 at 8:25

Spudley · Accepted Answer · 2013-10-08 16:00:35Z

67

Install ImageMagick and use subClass imageMagick.

Install ImageMagick
```
sudo apt-get install imagemagick 
```

using subClass imagemagick:

var gm = require('gm').subClass({ imageMagick: true });

edited Oct 8, 2013 at 16:00

Spudley

169k39 gold badges240 silver badges309 bronze badges

answered Oct 8, 2013 at 15:44

Quỳnh Lê

6715 silver badges2 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Devesh Over a year ago

Thanks, This resolved issue of my nodejs app on heroku.

cespon Over a year ago

GM also requires GraphicsMagick like in GM's Readme file is mentioned. When I installed it, the issue disappeared. In Mac OS X, brew install graphicsmagick.

yangsibai Over a year ago

To CentOS guys : yum install ImageMagick

jwanglof Over a year ago

This should be be marked as the correct answer. Thanks a bunch!

user3014311 Over a year ago

sudo apt-get install imagemagick + sudo apt-get install graphicsmagick worked for me

Matiss · Accepted Answer · 2013-08-27 10:36:12Z

I'm running nodejs on windows 7 with installed gm and imagemagick and seems that there was conflict between both modules so i googled a bit and found out how to avoit that. I added this line and that solved my ENOENT problem: var imageMagick = gm.subClass({ imageMagick: true }); so the code now looks like this:

var gm = require('gm'); var imageMagick = gm.subClass({ imageMagick: true }); imageMagick('test/pig.jpg').rotate('green', 45).write('test/crazy_pig.jpg', function (err) { if (!err) console.log('crazy pig has arrived'); else console.log(err); })

OR you can do that when requiring gm, like so:

var gm = require('gm').subClass({ imageMagick: true });

I can confirm that this solved my problem on OSX Mountain Lion. I installed it using macports instead of brew, In case this can help someone

user2620800 · Accepted Answer · 2014-02-21 17:52:53Z

4

Had the same problem with Node.js application running on Windows using IIS. Problem has gone when I set "Load User Profile" option in "Advanced settings" of appropriate AppPool to "True"

answered Feb 21, 2014 at 17:52

user2620800

1611 gold badge2 silver badges7 bronze badges

1 Comment

TYRONEMICHAEL Over a year ago

OMG! Thank you sooooo much. Spent so long trying to figure this out. How you figured it out is beyond me, but thank you!

Surya Purohit · Accepted Answer · 2015-09-10 11:18:08Z

I faced the same problem and solved it in the given way.

var gm = require('gm'); gm('public/uploads/1710410635.jpg').options({imageMagick: true}).resize(240,240).write('public/uploads/1710410635.jpg', function (err) { if (!err) console.log('Done'); else console.log(err); })

Note: If you haven't installed imageMagick. Please install that first

epeleg · Accepted Answer · 2013-06-28 08:23:27Z

1

Another scenario where this might happen (when using windows) is if you try to run your code from a UNC Path. mapping a drive letter and running over the mapped drive letter solves this problem as well.

answered Jun 28, 2013 at 8:23

epeleg

11.1k19 gold badges112 silver badges161 bronze badges

2 Comments

Matiss Over a year ago

Can you give example? What do you mean with running over?

epeleg Over a year ago

maybe "running over" is not the right term. I meant that your node.exe should be run from something like n:\node\node.exe and not from something like \\myserver\myshare\node\node.exe

MiKlacko · Accepted Answer · 2015-03-06 21:01:07Z

I have the same issue as you and this was SOLUTION. ImageMagick was working correctly in terminal/console but not in nodejs (gm module). After 2 days of losing hair i fixed it by adding PATH variable to environment variables process.env.PATH There should be path to your imagemagick and other executables. Node.js has some PATH from system but for some reasone GM is ignoring it and using process.env.PATH

I created environment variable PATH(process.env.PATH) and set value to bin:node_modules/.bin:/usr/local/bin:/usr/bin:/bin I'm using MAC OS X

I got imageMagick installed with brew (brew install imagemagick)

Community · Accepted Answer · 2017-05-23 12:01:34Z

Because I found this problem many times here on stackoverflow, I want to share this answer: https://stackoverflow.com/a/25461564/3970623

The "spawn ENOENT" seems to be caused by a valid unix tools installation which is accessible using PATH environment variable.

Gregor · Accepted Answer · 2016-02-15 15:29:22Z

In my case it was very simple. It ocurred rigth after instalation of GraphicsMagick in windows 10: I tryed using a console that was yet open before installing GraphicsMagick. Therefore it used old path information and didn´t found GraphicsMagick. Solution: I had to open a new console for running the node for using gm.

Naji Amer · Accepted Answer · 2016-07-09 11:36:27Z

/gm/lib/command.js have an option where you can set the appPath, if gm is already working through the terminal, you can get the path to gm and pass it via the subClass function,In my case gm was installed in /usr/local/bin/ using brew on MacOsx.

var gm = require('gm').subClass({ appPath: "/usr/local/bin/" });

Chris Livdahl · Accepted Answer · 2019-02-11 22:29:21Z

Just in case someone is finding this error while on macOS, this worked for me:

$ brew install graphicsmagick

Collectives™ on Stack Overflow

Error: spawn ENOENT while using GM in node

10 Answers 10

5 Comments

1 Comment

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

10 Answers 10

5 Comments

1 Comment

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Linked

Related