HTTPStreamerAdapterCupertinoStreamer.onPlaylist: Stream not found
Hi there I've spent more time with wowza this last week then my wife. She's pissed. Anyway, I think I finally got stuff working - she'll be happy now. I've kept on having issues with watching live video on an i-phone and a desktop pc. I think I've read the instructions enough times now to realize that I don't need to overwrite the application.xml file in the conf/live folder. According to the tutorials, there is only one setting I need to change and that is the "Set the Transcoder/LiveStreamTranscoder value to:Code:<LiveStreamTranscoder>transcoder</LiveStreamTranscoder>." I have noted over the past few days that I kept seeing "Stream not Found" in the error logs. I have been looking at other posts regarding this and can't seem to find the answer to get rid of this. I have not touched anything other then the transcoder value above. This is the exact error, "WARN server comment 2013-11-26 17:33:49 129.098 HTTPStreamerAdapterCupertinoStreamer.onPlaylist: Stream not found [live/sample_360p/chunklist_w1717532328.m3u8]: sample_360p. I noticed in other posts that people were asked to see if they could view the individual playlist files; 160p and 360p. I am able to view those. Can you please help on this.
On another note, when trying to figure these things out, I've been using the smaller server size on Amazon. Today, I upped it to the next level and didn't have any issues playing back the streams..... Is it that the smaller server doesn't have the capacity to run transcoder?
It sounds like you're making good progress. Migrating to a larger instance for transcoding and other more processor intensive workflows is always a good move. The smaller AMI's are capable of configuring the Transcoder AddOn, however, for best results, we strongly recommend using the larger instance sizes. Typically, running the transcoder on a small instance is problematic, as you have discovered, but there are some users with specialized workflows who are able to work through these constraints. Again, for best results, stick with a larger instance size.
When your server is under duress from limited resources, the WARN messages and other associated issues support the primary issue that your server is over-capacity - this is not a "normal" state of operation for Wowza. Now that you have upgraded your server size classification, you should run further tests and report on any issues, specifically, as needed. Do you continue to encounter this error?