Caught exception: Error: spawn ENOENT

[ahmad]

I keep getting the following exception every time I submit a job to the transcoder. From a little research that I did the ENOENT exception is supposed to be a URL access error but if I was to do a wget to the URL from the server itself it returns the correct page which tells me that the URL is accessible from the server.

Has anyone seen this before?

8 May 23:48:33 - Job 48f6465a1475b7a3b1e7da79b7af8990c614f0a6 accepted with opts: "{ source_file: '/path/to/source/uploads/original/1c6ab_MVI_1380.MOV', destination_file: '/path/to/destination/uploads/transcoded/1c6ab_MVI_1380.webm', encoder_options: '-vcodec libvpx -acodec libvorbis -ar 110000 -f webm -g 30 -b 75M -s 1280x720', callback_urls: [ 'http://example.com/user/notify/status/id/21/tid/41/' ] }" 8 May 23:48:33 - Caught exception: Error: spawn ENOENT

[tieleman]

It appears the transcoder can't locate your ffmpeg binary. Make sure that ffmpeg is in your $PATH or specify an absolute path to the ffmpeg binary in your config file. Can you verify this?

BTW, I'll open a separate issue for that fact that the transcoder is accepting jobs when it can't spawn ffmpeg. That seems to be a bug. (#19)

[ahmad]

Thank you. You are correct, the issue I was having was because of the path.

Thanks again for your help.