EC2 & S3 content access problems

[rrlanham]

Steve,

What region is your bucket in?

Richard

[rrlanham]

Steve,

Re-download the package and test. Updates have been made to address issue with buckets outside the US.

Note that in the new MediaCache.xml /s3BucketNameInDomain is set to "true"

Also, we are flipping the AWS Secret key and AWS key in the MediaCache.xml so the secret key is below, because that is where it is expected and noticed some users were transposing.

Richard

[Adamski11]

Hi

Having same sort of issues - can't play content from S3 despite following instructions to the letter and re-trying various setups. When you say "Re-download the package and test. Updates have been made to address issue with buckets outside the US" what do you specifically mean? I have found forum posts saying the tuning/MediaCache.xml needs to be changed like this <BasePath>http://s3-eu-west-1.amazonaws.com/</BasePath>, but your comment above maybe implies that doesn't need to be done? Do the files need to be modified for S3 regions outside the US as the WowzaMediaServerForEC2_UsersGuide doesn't say they need to be. Is there anything else I can check? I'm using the ami-5987bf2d with a startup package and I've tried with protected files and public files with both MediaCache.xml configurations to suit and noting will play. If I watch the wowza log via ssh I get "create stream", "unpublish stream", "destroy stream", disconnect" all in immediate sucession and the players give me a bad data or can't play file. There are no error messages and no file not found, so the file appears to be found but it won't play

Thanks
Adam

[Adamski11]

From trial and error it seems the <BasePath> does need to be modified for use in the EU region (why doesn't the pdf state this?)

I'm now in the situation where I am using the vods3 startup package with only the <BasePath> changed to be <BasePath>http://s3-eu-west-1.amazonaws.com/</BasePath>

If I use this URL:
rtsp://ec2-176-34-166-103.eu-west-1.compute.amazonaws.com/vods3/_definst_/mp4:amazons3/mybucket1/test.mp4

I don't get an error in the wowzamediaserver_error.log file. The file exists and is public in the bucket. If I change the filename in the rtsp URL to test1.mp4 I see lots of "Item does not exist" errors appear, so that comfirms wowza is mangaging to get the file. However it won't play in quicktime or vlc. In the wowzamediaserver_access.log I see events for "create stream", "unpublish stream", "destroy stream", disconnect" in immediate sucession and no errors. The source file is is 20MB and 17 secs long so shouldn't be too small, I've also tried on other mp4 files, all refuse to play. At this point I'm not sure what else I can try?

Thanks
Adam

[rrlanham]

Adam,

Test with the Wowza sample.mp4 file, which is in the /content folder. Copy it to your bucket and test with vods3. If that works, take a look at these encoding suggestions:

http://www.wowza.com/forums/content....ideo-on-Demand

Richard

[rrlanham]

Also, be sure you are using one of the current AMIs, which fixed the problem with EU buckets

http://www.wowza.com/forums/content....achine-images)

Richard

[Adamski11]

Hi

Yes the sample movie works (v annoyed at myself for not testing with it).

How can I find out what it is that wowza doesn't like about the video files I've been using? Shouldn't it be adding something to the error log if it is unable to stream a file caysing playback to fail? Our application is the playback of user uploaded content (file uploads, not streamed to wowza to record) without re-encoding so I'm not sure what the easiest approach to solving this would be given that we want wowza to play H.264 recorded by a wide variety of devices? It is as simple as the file probably not being hinted properly or can there be other things that need to be solved?

Thanks
Adam

[rrlanham]

You can get a lot of info with FFmpeg, and compare files.

ffmpeg -i filename

Richard

[Adamski11]

You can get a lot of info with FFmpeg, and compare files.

ffmpeg -i filename

Richard

Is there any way to get wowza to report on what it didn't like about a file or is the only way to go through trial and error?

[rrlanham]

Look at the access and error logs for log messages associated with playback of problem file.

Does it play if the content is local (not using MediaCache) and the player is local or workstation on LAN?

Richard