HydraIssues

Venue team summary

The Cloud Seven livestream unit (Epiphan Pearl-2, serial TSKB03679) has an identified repair route. We have shared its serial number with an Epiphan-certified repair provider, who will confirm the total expected cost. The serial number will determine whether the repair is covered by warranty.

The next livestream event is 8 October. We will run a full trial on 6 October, so the Pearl must be repaired, returned, installed, and tested by 2 October. The immediate next step is to review the provider’s cost and warranty response and approve the repair without delay if needed. Until that repair is complete, the Pearl is out of service and no temporary livestream workaround will be used.

Master tracking issue for the Cloud Seven Epiphan Pearl-2 (serial TSKB03679) being out of order. Origin symptom (web UI dropping GET requests) was #684, resolved by reboot; the real incident (failed SSD + livestream egress) is tracked here.

CONTINGENCY PLAN — Cloud Seven Epiphan Pearl-2 (TSKB03679) out of order (updated 2026-09-10)

The internal SSD has failed (state fsfail): recording is down and the disk cannot be checked or formatted. The Pearl is out of service until repaired; no temporary livestream workaround will be used. The earlier YouTube-egress investigation remains recorded in #687 and #688, but is not an active recovery route.

Workstreams (sub-tickets of this issue):

• #686 — forwardable write-up for Epiphan support (SSD replacement / RMA).
• #687 — livestream contingency (network egress). The Pearl already ingests the camera, mixes audio, and encodes; only the last hop to YouTube is broken. Fix = restore egress, then it goes live automatically (publisher is configured with the correct key and started).
  • #688 — investigate the network issue (gateway/DNS revert, Citymesh AV-subnet egress). Holds Tom's gateway clue.
• #689 — identify the streaming account (cloudsevenstream@gmail.com) recovery phone number ending in 78.
• #690 — Tom to check with Pascal for a replacement/loaner Pearl unit while this one is out of order.
• #691 — Tom to email his Epiphan contact to understand the SSD fsfail fixing procedure.