Recherche avancée

Sur d’autres sites (8937)

• Why is "ffmpeg : command not found" in heroku, even with proper buildpack/config ?

  14 novembre 2022, par Jim

  In a node.js app hosted on heroku, ffmpeg is used by spawning processes, but is throwing errors anytime an ffmpeg command runs

  


  the error ffmpeg: command not found is thrown both in cli test heroku run ffmpeg as well as production logs

  


  Ive considered :

  


  

  • buildpack order

  


  • buildpack clearing/re-adding/redeploying

  


  • buildpack required env vars

  


  • heroku-stack-20 conflicts with buildpack#1 somehow ?

  


  


  Buildpack order :

  


  

  1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git

  


  2. https://github.com/heroku/heroku-buildpack-awscli.git

  


  3. https://github.com/timanovsky/subdir-heroku-buildpack.git

  


  4. heroku/nodejs

  


  


  Buildpack configs - from watching build logs, even though i havent set ffmpeg path, a default is found.

  


  beginning build logs (completes successfully, runs successfully - minus ffmpeg) :

  


  -----> Building on the Heroku-20 stack
-----> Using buildpacks:
       1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
       2. https://github.com/xrisk/heroku-opus.git
       3. https://github.com/heroku/heroku-buildpack-awscli.git
       4. https://github.com/timanovsky/subdir-heroku-buildpack.git
       5. heroku/nodejs
-----> ffmpeg app detected
-----> Installing ffmpeg
       Variable FFMPEG_DOWNLOAD_URL isn't set, using default value
       Downloading https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz
       Unpacking the archive
       Installation successful
-----> heroku-opus app detected
       exporting PATH and LIBRARY_PATH
-----> Building in /tmp/build_51b5ac83/opus
-----> Starting opus compilation
       Downloading opus-1.3.1.tar.gz
       Unpacking opus
       Running configure
       Running make install
-----> AWS CLI app detected
-----> Downloading AWS CLI
-----> Installing AWS CLI
       You can now run: /app/.awscli/bin/aws --version
       aws-cli/2.8.12 Python/3.9.11 Linux/4.4.0-1104-aws exe/x86_64.ubuntu.20 prompt/off
-----> Successfully installed AWS CLI
-----> Subdir buildpack app detected
-----> Subdir buildpack in server
       creating cache: /tmp/codon/tmp/cache
       created tmp dir: /tmp/codon/tmp/cache/subdirBuBFb
       moving working dir: server to /tmp/codon/tmp/cache/subdirBuBFb
       cleaning build dir /tmp/build_51b5ac83
       copying preserved work dir from cache /tmp/codon/tmp/cache/subdirBuBFb to build dir /tmp/build_51b5ac83
       cleaning tmp dir /tmp/codon/tmp/cache/subdirBuBFb
-----> Node.js app detected


  


  Any suggestions to further debug this ?

  


• OCI runtime exec failed : exec failed : (...) executable file not found in $PATH" : unknown

  12 octobre 2024, par Uğur Kaya

  I have dockerized an app which has ffmpeg installed in it via libav-tools. The app launches without problem, yet the problem occured when fluent-ffmpeg npm module tried to execute ffmpeg command, which was not found. When I wanted to check the version of the ffmpeg and the linux distro set up in the image, I used sudo docker exec -it c44f29d30753 "lsb_release -a" command, but it gave the following error : OCI runtime exec failed: exec failed: container_linux.go:296: starting container process caused "exec: \"lsb_release -a\": executable file not found in $PATH": unknown

  



  Then I realized that it gives me the same error with all the commands that I try to run inside the image or the container.

  



  OCI runtime exec failed: exec failed: container_linux.go:296: starting container process caused "exec: \"ffmpeg -a\": executable file not found in $PATH": unknown


  



  This is my Dockerfile :

  



  FROM ubuntu:xenial
FROM node
RUN apt-get -y update
RUN apt-get --yes install libav-tools
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
COPY package.json /usr/src/app
RUN npm install
COPY . /usr/src/app
RUN npm run build
ENV NODE_ENV production
EXPOSE 8000
CMD ["npm", "run", "start:prod"]


  



  I would kindly ask for your help. Thank you very much !

  


• How many "Ruby on Rails" sites can be hosted using sub url in apache configuration file on apache4 with passenger4 on Ubuntu server ?

  17 octobre 2013, par user1731249

  Server's Hardware config :
  Ubuntu server 12.04, CPU : dual code (64-bit), RAM : 8GB, Disk : 200GB.

  Server's Software config :
  Apache2, Passenger4, Rails4, ruby2, MySQL.

  I'm developing a Ruby on Rails website which performs following tasks.

  1. Upload a series of images as zip.
  2. Extract zip images to temp directory.
  3. Convert series of images to video using FFMPEG.
  4. updating video info in MySQL db
  5. Viewing the video in HTML5 video tag.

  Maximum length of single video being 1min and on an average there may be 50 videos to be converted per day. I created three copies (Don't ask me why !) of same website and hosting three sites as sub-URLs like "example.com" being the domain and example.com/site1, example.com/site2, example.com/site3. Below is the Apache configuration :
  RailsAutoDetect off

  ServerName 127.0.0.1

      DocumentRoot /home/ubuntuuser/work/public
  
      ErrorDocument 404 /404.html
  
  
  
  RailsBaseURI /site1
  
  
  
      <directory></directory>home/ubuntuuser/work/site1/advisor/public>
  
              Allow from all
  
      Options -MultiViews
  
              RailsEnv production
  
      
  
  
  
  RailsBaseURI /site2
  
  
  
  <directory></directory>home/ubuntuuser/work/site2/advisor/public>
  
              Allow from all
  
      Options -MultiViews
  
              RailsEnv production
  
      
  
  
  
      RailsBaseURI /site3
  
  
  
  <directory></directory>home/ubuntuuser/work/site3/advisor/public>
  
              Allow from all
  
      Options -MultiViews
  
              RailsEnv production
  
      

  How many such sites can I host with sub-URLs without big performance drag ?
  Also please help to do a performance test for all the sub-URLs.