1214842 - Unexpected Wowza Engine Behavior

Status: RESOLVED FIXED

(Air Mozilla :: Streaming, defect)

Description

[Richard A Milewski[:richard]]

During the FxOS Monthly Meeting multiple users reported stalled streams.  Inspection of the Wowza1's network graph showed normal input bitrates but a collapse of the output traffic.

Switching the stream to the Wowza2 engine remedied the problem.

The Wowza1 engine was restarted and appeared to function normally after the restart. The Joy of Coding event which immediately followed the FxOS Monthly Meeting was carried on the Wowza1 engine without incident.

A new revision of the Wowza engine software has been released and is in the process of being installed.

Comment 1

[Richard A Milewski[:richard]]

Attachment: Wowza1 Traffic Graph showing output collapse.

Comment 2

[Richard A Milewski[:richard]]

Attachment: Akamai Session and Edge Bandwidth Graphs for the event period.

Comment 3

[Richard A Milewski[:richard]]

Filed a request with the moc for any available info. See bug #1214854

Comment 4

[Richard A Milewski[:richard]]

Attachment: Wowza 1 error log for the relevant period.

Comment 5

[Richard A Milewski[:richard]]

Attachment: Wowza1 access log for the relevant period

Comment 6

[Richard A Milewski[:richard]]

Attachment: Wowza1 access log for the relevant period

Comment 7

[Richard A Milewski[:richard]]

Akamai logs have been requested.  Won't be available for a bit yet.

Comment 8

[Richard A Milewski[:richard]]

Reducing frame-rate and ensuring only a single encoder is in use on any one Wowza Engine seems to have solved the problem.