bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Unexpected Wowza Engine Behavior

RESOLVED FIXED

Status

Air Mozilla
Streaming
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: richard, Unassigned)

Tracking

Details

Attachments

(5 attachments)

(Reporter)

Description

3 years ago
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.
(Reporter)

Comment 1

3 years ago
Created attachment 8673857 [details]
Wowza1 Traffic Graph showing output collapse.
(Reporter)

Comment 2

3 years ago
Created attachment 8673861 [details]
Akamai Session and Edge Bandwidth Graphs for the event period.
(Reporter)

Updated

3 years ago
Depends on: 1214854
(Reporter)

Comment 3

3 years ago
Filed a request with the moc for any available info. See bug #1214854
(Reporter)

Comment 4

3 years ago
Created attachment 8673886 [details]
Wowza 1 error log for the relevant period.
(Reporter)

Comment 5

3 years ago
Created attachment 8673896 [details]
Wowza1 access log for the relevant period
(Reporter)

Comment 6

3 years ago
Created attachment 8673949 [details]
Wowza1 access log for the relevant period
(Reporter)

Comment 7

3 years ago
Akamai logs have been requested.  Won't be available for a bit yet.
(Reporter)

Comment 8

3 years ago
Reducing frame-rate and ensuring only a single encoder is in use on any one Wowza Engine seems to have solved the problem.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.