Recherche avancée

Sur d’autres sites (2697)

• FFmpeg output to textfile causing 500 Internal Server Error in PHP

  27 mars 2018, par user3080392

  I have a PHP script with two FFmpeg commands. The first command combines a list of .ts files into a single .ts file and logs the output information into a textfile. The second command converts the combined .ts file into an mp4 file and logs the output information into a textfile.

  Here’s the PHP :

  <?php
  
  error_reporting(E_ALL);
  
  ini_set('display_errors', 'On');
  
  
  
  $ffmpeg = "/usr/local/bin/ffmpeg";
  
  $vidClips = 'my_vids/vidClipslist.txt';
  
  $combinedFileTs = 'my_vids/combinedFileTs.ts';
  
  $logFileCombine = 'my_vids/logFileCombine.txt';
  
  $logFileConvert = 'my_vids/logFileConvert.txt';
  
  $combinedFileMp4 = 'my_vids/combinedFileMp4.mp4';
  
  
  
  shell_exec("$ffmpeg -f concat -safe 0 -i $vidClips -c copy $combinedFileTs 1> $logFileCombine 2>&1");
  
  
  
  shell_exec("$ffmpeg -i $combinedFileTs -f mpegts -codec:v mpeg1video -bf 0 -codec:a mp2 -q 12 $combinedFileMp4 1> $logFileConvert 2>&1");
  
  
  
  echo "Video finished.";
  
  ?>

  When I run this, my 500.shtml file message is shown on the page. However, I get no other error message echoed to the page nor are there any errors in my Cpanel error log. I also have a php error log set up, but it doesn’t show any errors.
  Oddly, both of the FFmpeg commands do what they’re supposed to, i.e., the "combinedFileTs.ts", "logFileCombine.txt", "combinedFileMp4.mp4", and "logFileConvert.txt" are all created. It’s just that I’m getting the 500 error and the PHP script following the two FFmpeg commands is not being run, i.e., echo "video finished."

  When I remove the output directive on the first FFmpeg command, i.e., "1> $logFileCombine 2>&1", everything works. All the files are created, the proceeding PHP script is run, and I don’t get the 500 error.

  <?php
  
  error_reporting(E_ALL);
  
  ini_set('display_errors', 'On');
  
  
  
  $ffmpeg = "/usr/local/bin/ffmpeg";
  
  $vidClips = 'my_vids/vidClipslist.txt';
  
  $combinedFileTs = 'my_vids/combinedFileTs.ts';
  
  $logFileCombine = 'my_vids/logFileCombine.txt';
  
  $logFileConvert = 'my_vids/logFileConvert.txt';
  
  $combinedFileMp4 = 'my_vids/combinedFileMp4.mp4';
  
  
  
  shell_exec("$ffmpeg -f concat -safe 0 -i $vidClips -c copy $combinedFileTs");
  
  
  
  shell_exec("$ffmpeg -i $combinedFileTs -f mpegts -codec:v mpeg1video -bf 0 -codec:a mp2 -q 12 $combinedFileMp4 1> $logFileConvert 2>&1");
  
  
  
  echo "Video finished.";
  
  ?>    

  Also, the first FFmpeg command takes about 2 min to run. Thinking that the problem was due to the PHP script being killed, I increased the max_execution_time to 600 and the memory_limit to 512M in my php.ini file but that did not fix the problem.

  I need both FFmpeg commands to produce an output log textfile and I need the proceeding PHP code to run.

• PHP stops after exactly 46 seconds

  12 octobre 2012, par Lisa

  I have seen many topics with a similar question, but not a similar situation, because the php settings do not seem to be the problem.

  The current php.ini settings are :

  max_execution_time = 600
  
  max_input_time = 600
  
  memory_limit = 512M
  
  post_max_size = 192M
  
  upload_max_filesize = 192M

  These settings cannot be overwritten by the local .htaccess

  The script
  The script is PHP and does the following :

  User uploads a movie file (using uploadify).
  Once the upload is finished a script uses ffmpeg to convert it in to a lower quality 480p flv file.

  The problem
  This script has always worked and since the upgrade from php 5.3.9 to 5.3.17 it has stopped working.
  The upload part works fine. I have tried it with 1Mb to 190mb files.
  Once uploaded the conversion starts and the script always stops at exactly 46 seconds. I have no clue why, but it is always 46 seconds.

  The server
  The server is a xeon quad-core 16Gb ram and a load average of 0.62 (8 = 100% cpu usage)

  I truly have no idea what the problem seems to be. The script worked fine and has not changed. So it must be something to do with the new PHP or perhaps Apache, but I have no clue.

  Does anyone have a suggestion regarding what the problem could be ?

• Revision 30164 : Code mort bis

  24 juillet 2009, par kent1@… — Log

  Code mort bis