Hi! we've been successfully using flashvideo for awhile and recently wanted to switch to Amazon S3 - we created an Amazon S3 account, created a bucket called "soundclips" in Amazon S3, told flashvideo about "soundclips" in the S3 configuration and created a video. We got the "Video Not Available" message, and when we went to Amazon to investigate found that a new bucket had been created with our flv file....
"soundclips_sites_default_files_video_output"
The soundclips bucket was empty.
This bucket name has the file path where the flv file was placed by ffmpeg on our server (sites/default/files/video_output)! Very strange, and apparently drupal flashvideo S3 doesn't know how to find the flv file in this bucket on amazon when it goes to display it, even though it created the bucket and put it there! Please help!
Comments
Comment #1
marita93 commentedwe got it working by blanking out the "bucket" value in the flashvideo S3 settings . When flashvideo creates the bucket, it can find the videos just fine! Yay!
Comment #2
marita93 commentedjust installed the rc3 version of flashvideo, and now things have gotten really strange. Another new bucket was created in Amazon, this one is sites-default-files-video_output, and now we can see the flv files in Amazon, however at the end of the create transaction, a file isn't recorded in the database, sometimes we get a MYSQL went away error, sometimes we don't. Either way, flashvideo is lost and can't find the flv. I increased the mysql.connect_timeout in my .htaccess to 200, so it ran a long time, but still failed.
Comment #3
marita93 commentedthe problem is some sort of timeout, the postop code runs for smaller videos, up to 8M. My .htaccess values are:
max_input_value 1000
max_execution_time 1000
max_input_time 1000
post_max_size 100M
upload_max_filesize 100M
mysql.connect_timeout 100
Anything else I am missing?
Comment #4
marita93 commentedThis is a really strange problem. The upload, the conversion with ffmpeg from mov to flv works. The storage on Amazon works. What fails is the update to the database! And it works if the flv files are small, and fails if the flv files are large. Why would flv file size affect updating the database?
Comment #5
marita93 commentedfixed by changing the mysql wait_time out, increased from 20 to 100 (works for up to 14 Meg, havn't tested above )
Could you add the mysql wait_timeout value of at least 100 to your documentation?
Comment #6
attheshow commentedWhere do you change the mysql wait_timeout? Can that be done in either the .htaccess or in php.ini? Could you post the code you used here?
Comment #7
marita93 commentedIt has to be changed in the my.ini file, the option file for mysql. My hosting provider (infrenion.com) was kind enough to change it for me.
Comment #8
marita93 commentedI'm sorry! it's the my.cnf file:
wait_timeout=100
Comment #9
attheshow commentedNo further response here in two months. Closing issue.