Vods3 caching error

[Oliakaoil]

I recently tried to get vods3 working by manually applying the startup package to the default wowza configuration in my AMI, which is a customized version of ami-6b4fa902.

This was easy because all the files seemed to be in place for vods3 to work, and just required adding my keys to Server.xml (the vods3 Application.xml was already in place). I also verified that the bucket I'm trying to use is publicly accessible, as well as the sample file, and am NOT using any restrictions in the StreamNameAliasMap file.

However, I'm getting this error:

WARN server comment - Cannot find MediaCacheSource for (amazons3/[bucket-name]/sample-file.flv).
WARN server comment amazons3/[bucket-name]/sample-file.flv open: java.io.IOException: MediaCacheRandomAccessReader.open: Item not in cache: amazons3/[bucket-name]/sample-file.flv
INFO stream destroy amazons3/[bucket-name]/sample-file.flv -

I removed the actual bucket name and filename. I've also read this:

http://forums.rightscale.com/showthread.php?p=380

But was unable to make any progress. I also can't seem to find any documentation regarding what the Wowza user guide refers to as:

"...read through local disk cache to improve the performance of streaming media from S3. The configuration of the caching mechanism is done automatically and is adjusted based on the AMI instance type being used..."

and I assume this may be the source of the problem. Any help?

[rrlanham]

It should work to apply the vods3 package that way. Did you try to play the samples:

amazons3/wowzamediacache/sample/Extremists.flv
mp4:amazons3/wowzamediacache/sample/Extremists.m4v
mp3:amazons3/wowzamediacache/sample/Extremists.mp3

If you send me the EC2 public dns, I will give it a try.

Richard@wowzamedia.com

[Oliakaoil]

It should work to apply the vods3 package that way. Did you try to play the samples:

I tried the 3 links you sent using the FastPlay swf provided in one of the examples that comes with Wowza. I got "stream not found" for all three. My Wowza Server NC url:

rtmp://rtmp2.goodgametv.com/vods3

I used that value for the "Sever" input, and used the 3 samples just as you wrote them for the "Stream" input.

Also, please let me know if I'm not reading the uri right, but I assume amazons3 is the bucket name and the rest of it is the filepath to the media file in the bucket? Also, you ommited "flv:" for the first sample because that's the default?

Many thanks...

[rrlanham]

Doesn't work here. You didn't mention ServerListeners. You have to add two ServerListeners to /conf/Server.xml

<ServerListeners>
<ServerListener>
<BaseClass>com.wowza.wms.plugin.amazonaws.ec2.env. ServerListenerEC2Variables</BaseClass>
</ServerListener>
<ServerListener>
<BaseClass>com.wowza.wms.plugin.amazonaws.ec2.medi acache.MediaCacheServerListenerAmazonEC2</BaseClass>
</ServerListener>
</ServerListeners>

Richard

[Oliakaoil]

I checked and I definitely have those definitions in my Server.xml.

[rrlanham]

The "amazons3" part is the prefix for all content on S3.

In the following example, "wowzamediacache" is the name of the bucket.

mp4:amazons3/wowzamediacache/sample/Extremists.m4v

[rrlanham]

I tried to launch that AMI but it didn't work. Invalid manifest.

It is a Wowza Server 2 Advanced AMI -- but not the current Preview release. It might not be supportable in this case.

But vods3 is built into all EC2 instances now, if you are using default startup package (which is what is used if you do not use a startup package explicitly). For public content on S3 it should work with no changes. And for non-public content is should work with just the addition of your AWS keys in Server.xml

Richard

[Oliakaoil]

Well I guess I was hoping there was a better solution than "Use another AMI", Especially considering that I've already created a private AMI based off the public one I started with.

Obviously I could keep trying AMI's until one worked, but it seems to me, that given the actual error message I'm getting, there may just be a slight adjustment that needs to be made, like adding some path value to Application.xml or creating a directory (i.e. solving the problem of Wowza not finding the file in the cache). My Java's not so great so delving into source code is probably not gonna render much good, and I will probably end up just starting again from scratch with something that works, but it would be nice to know how the thing actually works.

Is anyone aware of any documentation/etc. concerning the automatic read-through local caching of media files that Wowza uses to stream from s3?

[rrlanham]

vods3 is based on the MediaCache package, and some additional documentation is included.
http://www.wowzamedia.com/downloads/...MediaCache.zip

Richard

[Oliakaoil]

Well I got going with the latest preview version of the ami and everything worked out of the box, including a test streaming from one of my own publicly accessible buckets. Thanks for all the help with this, to be honest I didn't even realize I had picked such an old version of Wowza when I booted up my first AMI.