I'm working through setting up a private server within our network, connected via REST/HTTP to an AWS instance of the server (both 3_1_13). They seem to be talking to each other, and when I upload a video file through our frontend server it goes through encoding on the backend, but fails when it comes to "Storing file". In the logs (backend server) I get
2012-01-25 18:30:48 /home/moviemasher/script/moviemasher
RECEIVING Request: <?xml version="1.0" encoding="UTF-8"?>
2012-01-25 18:32:30 /home/moviemasher/script/moviemasher
MovieMasher_File::put waiting 30 seconds after error 1: Could not post file: http://steve:firstname.lastname@example.org/example/server/media/php/encoded.php?id=928ae10285d9a140cd31e4fbad3ed559
2012-01-25 18:33:05 /home/moviemasher/script/moviemasher
MovieMasher_File::put waiting 30 seconds after error 2: Could not post file: http://steve:email@example.com/example/server/media/php/encoded.php?id=928ae10285d9a140cd31e4fbad3ed559
2012-01-25 18:33:39 /home/moviemasher/script/moviemasher
MovieMasher_File::put waiting 30 seconds after error 3: Could not post file: http://steve:firstname.lastname@example.org/example/server/media/php/encoded.php?id=928ae10285d9a140cd31e4fbad3ed559
2012-01-25 18:34:14 /home/moviemasher/script/moviemasher
exception 'RuntimeException' with message 'Problem transfering file to: http://steve:email@example.com/example/server/media/php/encoded.php?id=928ae10285d9a140cd31e4fbad3ed559' in /home/moviemasher/private/MovieMasher/Daemon.php:141
#0 /home/moviemasher/private/MovieMasher/Daemon/Local.php(39): MovieMasher_Daemon->_codeJob()
#1 /home/moviemasher/private/MovieMasher/Daemon.php(393): MovieMasher_Daemon_Local->_processJob()
#2 /home/moviemasher/private/MovieMasher/Daemon.php(68): MovieMasher_Daemon->__peek()
#3 /home/moviemasher/script/moviemasher(10): MovieMasher_Daemon->start()
(domain blanked…) Not finding any other errors/clues anywhere else for the next step. I can access the frontend server from the AWS instance via it's public dns. Any pointers would be much appretiated!
First check the web server log on your machine for evidence that the URL was actually requested. If not, it's often a network error reaching your machine from the instance - try SSH into the instance and using wget to hit your server until that works. If so, check the Movie Masher log on your machine which may have an error about the POST request.
Thanks for the rapid response! access.log on the frontend server shows…
xxxx.xxxx.xxx:80 18.104.22.168 - steve "POST /example/server/media/php/encoded.php?id=928ae10285d9a140cd31e4fbad3ed559 HTTP/1.1" 400 269 "-" "-"
So it's hitting the server, and the frontend is returning a 400 I presume.
Just below this I got (later attempt)
Could not extract to /tmp/moviemasher/5a528a24f1baab33d573f67447937165/media/
and I realized I hadn't created tmp/moviemasher (relative to web root). So I did that and made sure it was writable by the webserver, but I still got the same error message when I tried it again…
The log ends with
2012-01-25 20:41:12 /example/server/media/php/encoding.php?job=6357660daec943ae0ccf3a22d938e68c&id=e8015c91f0038535146b5c4b91bb54ee&start=0
Thanks for you help!
Do you have PEAR's Archive_TAR class installed?
Yes, I had it installed, but I hadn't set the include_path correctly to include the PEAR files! Once I fixed that it uploaded successfully and appeared in the editor - thanks for the pointers!
Side question… so it looks as though the videos are stored on the frontend server, the backend just transcodes and sends them right back? I'm wondering about storage size and thinking I'll need more storage capacity on the front end?
Thanks again for the help…
Glad to hear it was simple to get going. Your side question is marked as such, but it's really a statement I'm not in a position to agree or disagree with. Certainly the front end is where things are really stored - the transcoder only caches files and the cache will be dumped when full.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.