-
Notifications
You must be signed in to change notification settings - Fork 35
Error: spawn php-cgi ENOENT #17
Comments
Install php-cgi (usually part of php package)
…On 17 Dec 2016 12:20, "Ind" ***@***.***> wrote:
I am getting this error message when I tried run a php script with this;
{ Error: spawn php-cgi ENOENT
at exports._errnoException (util.js:1026:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
at onErrorNT (internal/child_process.js:348:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
code: 'ENOENT',
errno: 'ENOENT',
syscall: 'spawn php-cgi',
path: 'php-cgi',
spawnargs: [] }
Appreciate if one has an idea what cause this error. :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#17>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AERqiYHEnb0VHQ3THDfKMNo2PgKO8MOOks5rI8V4gaJpZM4LP3QO>
.
|
I am getting this same error, I am trying to use this module to serve a wordpress site locally on mac osx.
|
Yea same here, I have PHP installed via homebrew on Mac but still get the same error. |
I've got the same error while running the example.js on linux, and php-cgi is installed (npm install --save php-cgi) `/node_modules/sphp$ node example.js Error: spawn php-cgi ENOENT |
For what its worth, I was able to get the error to go away by doing
|
Ive solved this error on my MacOS High Sierra, simply appending a full-path to php-cgi: I think this error is cause the node-php\main.js[child.spawn] isnt finding the php-cgi by $PATH Note: i have tried all kind of installations of php and different versions, but the error has persist, then i solved with the full-path(solution of image) in node-php version 0.0.1 |
Cool this worked.
|
On a second thought it will be nice to get the paths for php/cgi dynamic from a config file with a default for system, if not specified. |
I am getting this error message when I tried run a php script with this;
Appreciate if one has an idea what cause this error. :)
The text was updated successfully, but these errors were encountered: