Wowza Community

Transcoder stops at 3 hours

Hello,

Our self hosted Wowza Streaming engine server live stream transcoder is stopping after exactly 3 hours even with clients connected to the stream. We are using the transrate template. The live source (other encoder) is still up and running and Wowza logs the transcoder stop of all video and audio streams after x-duration of 65859.3xx. I didn’t see any time limits in the streaming engine manages. Where else should I check?

We are running Engine Version

4.1.1 (build 13180)

Engine Manager Version

4.1.1 (build 13180)

License

Wowza Streaming Engine 4 Perpetual Bundle Edition

Thanks,

Mike

Hi,

There aren’t any such time limits. Exactly 3 hours does seem suspicious though.

Do you see any significant messages in the error logs or access logs, located at [install-dir]/logs/wowzastreamingengine_access.log

or wowzastreamingengine_error.log around the time it stops?

Daren

Hi,

Glad you have that resolved. If you do need to use UDP you’ll need to open a range of such ports.

This guide section talks about what to open.

Daren

Daren,

After further review of the logs the issue happens at 2 hours and not 3. Also we were able to reproduce the issue without running the transcoder and with 2 different encoders, FFMpeg, and an Epiphan DVI Broadcaster DL . The Wowza logs show an orderly shutdown of the session even though the encoders were still running. It seems to be a firewall issue when sending the RTSP stream from the encoder to the Wowza server using UDP. With RTSP over TCP the encoder streams stay up as expected and our issue is solved. With FFMpeg we added “-rtsp_transport tcp” to the output command, and with the Epiphan there is a checkbox “Use TCP for RTP stream”.

Thanks,

Mike