Pending videos

I have a problem getting the videos to approve status although it is set as auto-approve.
I looked through the forum and set the FFMPEG in the /cc-core/system/ffmpeg but the problem still persists.
The log seem to indicate permission denied
So I set file permission numeric as 0777 but the problem and log remains the same as below log.
Can you help?

H.264 Encoding Command: /home/tanaka1/gestpedia.co/cc-core/system/ffmpeg -i /home/tanaka1/gestpedia.co/cc-content/uploads/temp/x2R1iuf2BkxIAthsFGSa.mp4 -vcodec libx264 -vf "scale=min(640\,iw):trunc(ow/a/2)*2" -vb 800k -acodec libfaac -ab 96k -ar 44100 -f mp4 /home/tanaka1/gestpedia.co/cc-content/uploads/h264/x2R1iuf2BkxIAthsFGSa_temp.mp4 >> /home/tanaka1/gestpedia.co/cc-core/logs/x2R1iuf2BkxIAthsFGSa.log 2>&1
H.264 Encoding Output:


sh: /home/tanaka1/gestpedia.co/cc-core/system/ffmpeg: Permission denied

Comments

  • edited December 2015
    Can you run these four commands and post the output of each:

    ls -l /home/tanaka1/gestpedia.co/cc-core/system/ffmpeg

    ls -l /home/tanaka1/gestpedia.co/cc-content/uploads/temp/x2R1iuf2BkxIAthsFGSa.mp4

    ls -l /home/tanaka1/gestpedia.co/cc-content/uploads/h264

    ls -l /home/tanaka1/gestpedia.co/cc-core/logs
  • *Corrected commands
  • Thank you fro your help.
    here are the outputs

    [ps496832]$ ls -al /home/tanaka1/gestpedia.co/cc-core/system/ffmpeg
    -rwxrwxrwx 1 tanaka1 pg8672748 42009036 12月 19 21:02 /home/tanaka1/gestpedia.co/cc-core/system/ffmpeg

    [ps496832]$ ls -al /home/tanaka1/gestpedia.co/cc-content/uploads/ls -l /home/tanaka1/gestpedia.co/cc-content/uploads/temp/x2R1iuf2BkxIAthsFGSa.mp4
    ls: cannot access /home/tanaka1/gestpedia.co/cc-content/uploads/ls: No such file or directory
    -rw-r--r-- 1 tanaka1 pg8672748 3818437 12月 19 01:41 /home/tanaka1/gestpedia.co/cc-content/uploads/temp/x2R1iuf2BkxIAthsFGSa.mp4

    [ps496832]$ ls -l /home/tanaka1/gestpedia.co/cc-content/uploads/h264
    total 0

    [ps496832]$ ls -l /home/tanaka1/gestpedia.co/cc-core/logs
    total 28
    -rw-r--r-- 1 tanaka1 pg8672748 1881 12月 18 22:39 5yoFq9GY0Io87dgsBsP8.log
    -rw-r--r-- 1 tanaka1 pg8672748 593 12月 20 04:22 L309ApjOZCYmEx0DYXYj.log
    -rw-r--r-- 1 tanaka1 pg8672748 1469 12月 18 21:39 QlmuqRsk5ERY6yf8uhx3.log
    -rw-r--r-- 1 tanaka1 pg8672748 315 12月 20 04:22 converter.log
    -rw-r--r-- 1 tanaka1 pg8672748 3386 12月 20 04:27 gestureProperties.log
    -rw-r--r-- 1 tanaka1 pg8672748 593 12月 19 15:55 p03Bnof5JkfGXJ5onCGI.log
    -rw-r--r-- 1 tanaka1 pg8672748 665 12月 19 01:41 x2R1iuf2BkxIAthsFGSa.log
    [ps496832]$
  • Sorry let me repost correct results.

    [ps496832]$ ls -al /home/tanaka1/gestpedia.co/cc-core/system/ffmpeg
    -rwxrwxrwx 1 tanaka1 pg8672748 42009036 12月 19 21:02 /home/tanaka1/gestpedia.co/cc-core/system/ffmpeg

    [ps496832]$ ls -l /home/tanaka1/gestpedia.co/cc-content/uploads/temp/x2R1iuf2BkxIAthsFGSa.mp4
    -rw-r--r-- 1 tanaka1 pg8672748 3818437 12月 19 01:41 /home/tanaka1/gestpedia.co/cc-content/uploads/temp/x2R1iuf2BkxIAthsFGSa.mp4

    [ps496832]$ ls -l /home/tanaka1/gestpedia.co/cc-content/uploads/h264
    total 0

    [ps496832]$ ls -l /home/tanaka1/gestpedia.co/cc-core/logs
    total 28
    -rw-r--r-- 1 tanaka1 pg8672748 1881 12月 18 22:39 5yoFq9GY0Io87dgsBsP8.log
    -rw-r--r-- 1 tanaka1 pg8672748 593 12月 20 04:22 L309ApjOZCYmEx0DYXYj.log
    -rw-r--r-- 1 tanaka1 pg8672748 1469 12月 18 21:39 QlmuqRsk5ERY6yf8uhx3.log
    -rw-r--r-- 1 tanaka1 pg8672748 315 12月 20 04:22 converter.log
    -rw-r--r-- 1 tanaka1 pg8672748 3386 12月 20 04:27 gestureProperties.log
    -rw-r--r-- 1 tanaka1 pg8672748 593 12月 19 15:55 p03Bnof5JkfGXJ5onCGI.log
    -rw-r--r-- 1 tanaka1 pg8672748 665 12月 19 01:41 x2R1iuf2BkxIAthsFGSa.log
  • Sorry, one of the commands I posted was incorrect. Try this one, please post the entire output:

    ls -la /home/tanaka1/gestpedia.co/cc-content/uploads
  • here it is
    [ps496832]$ ls -la /home/tanaka1/gestpedia.co/cc-content/uploads
    total 0
    drwxr-xr-x 9 tanaka1 pg8672748 124 12月 18 21:08 .
    drwxr-xr-x 7 tanaka1 pg8672748 120 12月 18 21:08 ..
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 avatars
    drwxr-xr-x 2 tanaka1 pg8672748 10 12月 18 21:08 h264
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 mobile
    drwxrwxrwx 2 tanaka1 pg8672748 115 12月 20 04:22 temp
    drwxr-xr-x 2 tanaka1 pg8672748 10 12月 18 21:08 theora
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 thumbs
    drwxr-xr-x 2 tanaka1 pg8672748 10 12月 18 21:08 webm
    [ps496832]$

  • The only thing that I can see is that your h264 directory is 755 instead of 777. That could be the problem. Try this command from the root of your CumulusClips directory:

    cd cc-content/uploads
    find -type d -exec chmod 777 {} \;


    Then try your upload again.
  • Damian-san
    Thank you, but the problem still persists...

    [ps496832]$ cd cc-content/uploads
    [ps496832]$ find -type d -exec chmod 777 {} \;
    [ps496832]$ ls -al
    total 0
    drwxrwxrwx 9 tanaka1 pg8672748 124 12月 18 21:08 .
    drwxrwxrwx 7 tanaka1 pg8672748 120 12月 18 21:08 ..
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 avatars
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 h264
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 mobile
    drwxrwxrwx 2 tanaka1 pg8672748 115 12月 20 04:22 temp
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 theora
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 thumbs
    drwxrwxrwx 2 tanaka1 pg8672748 10 12月 18 21:08 webm
    [ps496832]$
  • edited December 2015
    After looking at the error a bit more I noticed the "sh:" part of the error. This usually means that the shell user, the Apache user doesn't have access to execute the binary. There are a couple reasons for this:

    - The binary is not executable
    - The binary is in a directory the user is not authorized to
    - The user is not authorized to one of the parent directories of the binary

    We know the binary has the right permission. Let's work on the other two possibilities. We'll try two different approaches.

    First:

    1) From the root of the CumulusClips directory run this command:

    cp cc-core/system/ffmpeg /home/tanaka1
    /home/tanaka1/ffmpeg -version


    2) Verify that the version that is output by FFMPEG matches the static version of FFMPEG version that you downloaded and extracted to your server.

    3) Then update the FFMPEG path in the Admin Panel -> Video Settings -> FFMPEG Path to:

    /home/tanaka1/ffmpeg

    4) Purge your logs, and try again.

    Second, if the above doesn't work, try this:

    1) From the root of the CumulusClips directory run this command:

    cp cc-core/system/ffmpeg /tmp
    /tmp/ffmpeg -version


    Repeat steps 2-4. In the Admin Panel use: /tmp/ffmpeg instead.

    Let me know how it goes.
  • I tried both but could not get the video to upload.
    First: Sh: permission denied message disappeared but still no upload.
    Second: Sh: Permission denied

    -------------------------------------------------------------------------------------------------------
    First: Sh: permission denied message disappeared but still no upload.
    [ps496832]$ cp cc-core/system/ffmpeg /home/tanaka1
    [ps496832]$ /home/tanaka1/ffmpeg -version
    Segmentation fault (core dumped)
    [ps496832]$ cd ..
    [ps496832]$ ls -al
    total 41056
    drwxrwxrwx 7 tanaka1 adm 4096 12月 21 13:39 .
    drwxr-xr-x 6 root root 104 12月 17 16:25 ..
    -rw-r--r-- 1 tanaka1 pg8672748 260 3月 23 2012 .alias
    -rw------- 1 tanaka1 pg8672748 551 12月 17 19:58 .bash_history
    -rw-r--r-- 1 tanaka1 pg8672748 81 3月 23 2012 .bash_profile
    -rw-r--r-- 1 tanaka1 pg8672748 55 3月 23 2012 .bashrc
    drwxrwxrwx 2 tanaka1 pg8672748 41 12月 17 18:01 .cache
    -rw-r--r-- 1 tanaka1 pg8672748 417 3月 23 2012 .cshrc
    drwxrwxrwx 3 tanaka1 pg8672748 24 12月 17 16:57 .php
    drwxrwxrwx 5 tanaka1 pg8672748 52 12月 14 20:19 Maildir
    -rwxrwxr-x 1 tanaka1 pg8672748 42009036 12月 21 13:39 ffmpeg
    drwxrwxrwx 5 tanaka1 pg8672748 4096 12月 18 21:28 gestpedia.co
    drwxrwxrwx 3 tanaka1 dhapache 33 12月 16 21:17 logs
    [ps496832]$ uptime -V
    procps version 3.2.8

    ==================================================================
    H.264 ENCODING
    ==================================================================

    H.264 Encoding Command: /home/tanaka1/ffmpeg -i /home/tanaka1/gestpedia.co/cc-content/uploads/temp/NbcjBvCbzwkffNj8LYji.mp4 -vcodec libx264 -vf "scale=min(640\,iw):trunc(ow/a/2)*2" -vb 800k -acodec libfaac -ab 96k -ar 44100 -f mp4 /home/tanaka1/gestpedia.co/cc-content/uploads/h264/NbcjBvCbzwkffNj8LYji_temp.mp4 >> /home/tanaka1/gestpedia.co/cc-core/logs/NbcjBvCbzwkffNj8LYji.log 2>&1

    H.264 Encoding Output:

    -------------------------------------------------------------------------------------------------------Second: Permission denied
    [ps496832]$ cp cc-core/system/ffmpeg /tmp
    [ps496832]$ /tmp/ffmpeg -version
    -bash: /tmp/ffmpeg: Permission denied
    [ps496832]$
    ==================================================================
    H.264 ENCODING
    ==================================================================

    H.264 Encoding Command: /tmp/ffmpeg -i /home/tanaka1/gestpedia.co/cc-content/uploads/temp/CMWzqnbSBguIj8QebYvz.mp4 -vcodec libx264 -vf "scale=min(640\,iw):trunc(ow/a/2)*2" -vb 800k -acodec libfaac -ab 96k -ar 44100 -f mp4 /home/tanaka1/gestpedia.co/cc-content/uploads/h264/CMWzqnbSBguIj8QebYvz_temp.mp4 >> /home/tanaka1/gestpedia.co/cc-core/logs/CMWzqnbSBguIj8QebYvz.log 2>&1

    H.264 Encoding Output:


    sh: /tmp/ffmpeg: Permission denied

  • Your first attempt actually worked. The process just got killed, that's why you see that segmentation fault error.

    Two questions,

    1) Is this a shared host or a dedicated server? If dedicated, how much RAM is installed?

    2) Which version of FFMPEG did you download? The 32-bit or the 64-bit?
  • here is the ffmpeg version info
    [ps496832]$ ffmpeg -version
    ffmpeg version 0.8.17-4:0.8.17-0ubuntu0.12.04.1, Copyright (c) 2000-2014 the Libav developers
    built on Mar 16 2015 13:26:50 with gcc 4.6.3
    The ffmpeg program is only provided for script compatibility and will be removed
    in a future release. It has been deprecated in the Libav project to allow for
    incompatible command line syntax improvements in its replacement called avconv
    (see Changelog for details). Please use avconv instead.
    ffmpeg 0.8.17-4:0.8.17-0ubuntu0.12.04.1
    libavutil 51. 22. 3 / 51. 22. 3
    libavcodec 53. 35. 0 / 53. 35. 0
    libavformat 53. 21. 1 / 53. 21. 1
    libavdevice 53. 2. 0 / 53. 2. 0
    libavfilter 2. 15. 0 / 2. 15. 0
    libswscale 2. 1. 0 / 2. 1. 0
    libpostproc 52. 0. 0 / 52. 0. 0

  • This is a shared VPS host w/ 4G RAM
    and installed ffmpeg 64-bit.
  • Ok, so you downloaded the 64-bit version of the static FFMPEG binary according to the instructions on the other post. Please run this command and let me know the results:

    uname -a
  • edited December 2015
    We might have to try to download the 32-bit version, and possibly increase the amount of RAM as well.
  • here is the output
    [ps496832]$ uname -a
    Linux ps496832 3.1.9-vs2.3.2.5vs2.3.2.5+ #3 SMP Wed Feb 12 13:51:29 PST 2014 x86_64 x86_64 x86_64 GNU/Linux
  • Go back to the static build website and download the 32-bit version.

    http://johnvansickle.com/ffmpeg/

    Place it in your home directory like you did earlier, make sure you update the path in the Admin panel and make the binary executable (777). Try the command:

    /home/tanaka1/ffmpeg -version

    If you still get a segmentation fault, then you need more RAM. If you don't get the segfault error then proceed to purge your logs and try a video upload.
  • I increase the RAM to 8G which is the max for this service but still get the segmentation fault.
    Is there something that needs to be changed from the host provider to make this work?

    [ps496832]$ /home/tanaka1/ffmpeg -version
    Segmentation fault (core dumped)
  • Segmentation fault errors are caused when an application runs into issues with memory on the machine. From our experience, every time we encounter them it's either because there is either too little RAM available to the OS or there is some type of restriction in place, which is common with shared hosting and VPS hosting.

    I personally would try a cheap cloud server like DigitalOcean, RackSpace Cloud, Amazon EC2. See if you get your site running on one of those servers. You shouldn't run into this problem in those environments because those virtual machines don't have the same restrictions like shared or VPS servers do.
  • Damian-san
    Thank you, I will check w/ the host service on their restrictions.
  • I confirmed with the host service but they do not seem to have any restrictions.
    Any other suggestion?
    they suspect PHP.in which I have already changed via phprc as below:
    pload_max_filesize = 110M
    post_max_size = 110M
    max_execution_time = 1500
    open_basedir = no value
    safe_mode = Off
    register _globals = Off

    ----------------------------------------------------------------------------------
    Thank you. Pls try and reboot as needed.
    The Videos I was trying to upload were 4 ~ 20MB from my website.
    So there are no restrictions in terms of such usage?

    -----------------------------------------------------------------------------------
    No problem! If you're uploading through the site itself, you might run
    into some other limits (depending on how you upload - if you're uploading
    via PHP, for example), but those can be modified by using a php.ini or
    phprc file. You can read more about this at:

    wiki.dreamhost.com/PHP.ini

    Other than that, there aren't limits on standard uploads, for example,
    uploading straight to the machine using FTP/SFTP or SSH. But you can run
    into some issues if you're uploading via the site's upload feature
    itself, with PHP memory or with /tmp directory limits. Even if the /tmp
    directory isn't 100% full of data - for example, if you're uploading a
    video smaller than its 128 MB limit - it can still run out of memory just
    running the scripts themselves that are performing the import.

    I just completed the switch, so any uploads you perform through the site
    itself will store that upload data right on the server - so you won't hit
    that 128 MB limit. Please try again, and if you run into any more
    issues, let us know - we can check to see if PHP memory is running out,
    which would mean that you would want to increase it using that article
    above.
    ---------------------------------------------------------------------------------
  • some updates
    Memory has been raised
    memory_limit =128M to 256M

    The host service ran a full page test, and says issue maybe with some of your theme files:
    http://tools.pingdom.com/
    Two files are causing the delays and issues,
    http://www.gestpedia.co/cc-content/themes/gestpedia-responsive/css/slicknav.css
    http://www.gestpedia.co/cc-content/themes/gestpedia-responsive/js/jquery.min.js

    Any hints?
  • The segfault issue is not related to PHP or CumulusClips. We tried running FFMPEG directly from the command line, independent from the video script or PHP and it still threw the segfault error.

    The restrictions I was referring to are virtual machine restrictions that prevent burstable usage of resources on a machine. This is typically behind the scenes and some vendors don't even know it's happening. This is why we recommend cloud servers or dedicated servers.

    If you like, I can have one of our engineers take a look at this for you to see if they can fix the segfault issue. Please note that we can't promise anything because segfault issues are usually related to resources available to the operating system, i.e. RAM. Send an email to support at cumulusclips dot org with your root SSH credentials and hostname/IP and our engineer will try to resolve it for you.
  • Damian-san
    Thank you, I will send a request to your support team.
  • Hi, we received your email information. I will forward it to our engineers, and let you know what they find.
  • edited December 2015
    Our engineer has fixed your problem. Here are his notes:

    ===============================================
    The FFMPEG version downloaded to the user's server was throwing 'Segmentation Fault' errors. I downloaded the latest Git static FFMPEG build for 64 bit systems and the errors went away. I created an account on the user's site and was able to upload a test video.

    All appears to be working now.
    ===============================================

    So apparently all that was done to fix the segfault error was download the latest static built compatible for your server (64-bit in your case).

    Please open a new thread for any new issues.
  • Thank you you've been a great help!
    I installed the "release" built rather than the "git" this seem to have caused all the problem...
    Thank you for your time and patients.
This discussion has been closed.