[FFmpeg-user] 500 Internal Server Error
h.reindl at thelounge.net
Tue Apr 30 15:01:49 CEST 2013
Am 30.04.2013 14:55, schrieb Trupti Thakkar:
> However , i need this functionality while adding video from my CMS , so to
> create cron -job here not possible and also not useful and right thing
then your cms is broken by design
been there, done that, doing it as daily business
it's easy to submit task-lists and file-uploads which are
proceeded by cron-scripts without open security leaks
on the webserver
> So , i need to write shell_exec() in php code only , and as soon as this
> code run , i redirect this page to one my file on server
this idea is broken by design
even if it would work basically you will run in timeouts
on the webserver if the ffmpeg-process takes longer
> But, the problem is shell_exec() command working well , it creating all
> required things , and after that it redirect to 500Internal Server Error.
> Also note that, i am using Hostgator Shared Server (Window server).
> Also , note that this issue is not happening on Linux Hostgator Server.
this issue has clearly nothing to do with ffmpeg
ask the support of Hostgator
ask in specific mailing-lists for PHP on windows
if this is a shared-server and shell_exec() would work
the admin of your hoster should be fired as the one
from a linux machine which allows shell_exec fro httpd
any sane php-setup for a webserver has this config:
disable_functions "popen, pclose, exec, passthru, shell_exec, system, proc_open, proc_close, proc_nice,
proc_terminate, proc_get_status, pcntl_exec, apache_child_terminate, posix_kill, posix_mkfifo, posix_setpgid,
posix_setsid, posix_setuid, mail, symlink, link"
> On Tue, Apr 30, 2013 at 6:07 PM, Reindl Harald <h.reindl at thelounge.net>wrote:
>> Am 30.04.2013 14:34, schrieb Trupti Thakkar:
>>> While using ffmpeg with shell_exce , as soon as command run , browser
>>> redirect to 500 Internal Server Error instead of page that is given.
>>> Is there any settings required in ffmpeg configurations ?
>> i assume you mean shell_exec() from PHP
>> no smart admin out there will enable shell commands on a webserver
>> because they break any open_basedir configuration and the 500 status
>> code is a PHP "Fatal error" on a correctly configured webserver which
>> does not open a info-leak by spit errors to the browser
>> so you neeed to run ffmpeg via cron-jobs and PHP needs different
>> "php.ini" for httpd and cli, you need shell access and finally
>> you need a dedicated server for what you are trying
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 263 bytes
Desc: OpenPGP digital signature
More information about the ffmpeg-user