I use a shared server on Dreamhost.

In shell, 'whereis ffmpeg' and 'whereis vhook' reveal the following:

'/usr/bin/ffmpeg' and '/usr/lib/vhook' respectively.

The vhook path is correct, and the module lists all of the vhook files found on the system.

However, in the "FFmpeg Wrapper Test Conversion" the "Output Format" select box is empty. Also, when trying to add a new configuration in Media Mover, I get the error "Sorry, could not find FFmpeg, please go to: FFmpeg Wrapper".

Obviously, my path to the shared installation of ffmpeg is not resolving. Is this because the module is looking for it in "www.example.com/usr/bin/ffmpeg" instead of the server root?

In the "FFmpeg Wrapper" module, can there be a feature to test this for shared installations?

Comments

arthurf’s picture

arthurf commented
Category: feature » support
Status: Active » Postponed (maintainer needs more info)

The path is your system path, so if whereis ffmpeg states: /usr/bin/ffmpeg that is your path. It could be the case that Apache does not have rights to execute ffmpeg- you might want to do ls -l /usr/bin/ffmpeg to see what its permissions are.

It's possible that ffmpeg_wrapper could check for ffmpeg on install... Probably something to put on the feature list.

Fr0s7’s picture

Fr0s7 commented

Firstly, thanks so much for your work on this series of modules. It's a brilliant concept!

ls -l /usr/bin/ffmpeg

returns -rwxr-xr-x

So User, Group, and Everyone has executable rights to FFmpeg. We've verified that the path is correct, and that the permissions are ok. Are there any other reasons why we'd get the same symptoms?

  • admin/settings/ffmpeg_wrapper/test: The select list 'Output format' only has the default item 'Select output type' showing. No other options are available in this list.
  • admin/build/media_mover/add: The page includes an error message TWICE, like this:
    Sorry, could not find FFmpeg, please go to: FFmpeg Wrapper
    Sorry, could not find FFmpeg, please go to: FFmpeg Wrapper
Fr0s7’s picture

Fr0s7 commented

To be thorough, I've installed a non-shared version of FFmpeg just above my website directory. Now, the absolute paths read as follows:

FFmpeg: /home/shellusername/bin/ffmpeg
vhook: /home/shellusername/lib/vhook

Once again, FFmpeg Wrapper successfully finds the vhook files and lists them fine. But with FFmpeg, I get the same symptoms as above.

I'm beginning to think this is not a path or permissions issue, but rather a configuration problem of some kind. Any ideas?

Fr0s7’s picture

Fr0s7 commented
Status: Postponed (maintainer needs more info) » Active

Nice meeting you yesterday!

I took your advice and created a new node with the php input format and did an if(file_exists('/usr/bin/ffmpeg') and sure enough, it returns true.

But when I go to add a new Media Mover configuration, I get the same error:

# Sorry, could not find FFmpeg, please go to: FFmpeg Wrapper
# Sorry, could not find FFmpeg, please go to: FFmpeg Wrapper

Based on what you said, this could be an FFmpeg Wrapper issue.

Then again, maybe there is another dependency (such as another module) that needs to be enabled? Any suggestions on which modules I absolutely need to get Media Mover to operate?

arthurf’s picture

arthurf commented

Thanks for coming to the talk! I think there must be some kind of restriction that Dreamhost is doing with executables- can you send them an email and ask if that's the situation?

Thanks!

arthurf’s picture

arthurf commented
Status: Active » Closed (fixed)