(Wowza 4.2, EC2 medium instance)
I'm working with a site that records live streams. Recently we have noticed that there are times when we are unable to record certain streams unless we do a full restart of Wowza (restarting the Wowza app fixes the issue. No need to reboot the Linux instance).
Here you see 3 live streams on the system. The "problem" stream in this instance is the "local6b" one.
We can verify that the stream is actually working by going into the wowza test player (or attaching via a jwplayer)
We select the red record button and tell Wowza to record [basic settings: MP4, Start on key frame makes no difference, no segmentation, version option makes no difference]
Upon hitting the record button the stream comes back as "Waiting for stream" even though the stream is still playing, and no recording ever happens.
After restarting Wowza (restarting the live App has no effect and remains broken) the same stream, which was not stopped on the encoder side, is now able to record.
What would cause a stream to be able to live stream just fine, be listed as "Active", but go into a waiting state when asked to record (while in the "Waiting" state for record, the live stream is still working from a live player). We also think we might be seeing a coloration between this happening and a very high spike in CPU usage (as reported by both the enginemanger and linux "top") but we are not certain of that.