Restarting a Broadcaster or ZEC
A restart stops every input and output on the Broadcaster until it is running again. The software is back within seconds, plus the time it takes to load its configuration. The host does not reboot. A ZEC runs the same software and restarts the same way.
Before you restart
- Pick a quiet window.
- If the Broadcaster is in a ZEN Master cluster, set it to Maintenance first. ZEN Master then stops sending new connections to it. Pushes set to any Broadcaster in the cluster, and pull targets, move to another healthy member.
- Streams pinned to this Broadcaster, and pulls the Broadcaster makes itself, stay down until it is back.
Restart from the web interface
On the Status page, click Restart and confirm. The button is shown to admin users when the Broadcaster runs as a service.
Restart from the command line
Platform | Command |
|---|---|
Linux | sudo systemctl restart zixibc (older hosts: sudo service zixibc restart). Check with systemctl status zixibc. |
Windows | Restart the Zixi Broadcaster service in Services, or run Restart-Service "Zixi Broadcaster" in an administrator PowerShell. |
Docker | docker restart <container>. The web interface does not show a Restart button in a container. |
From ZEN Master
ZEN Master has no general restart button. It restarts a Broadcaster only when a configuration change needs it, and asks first with Save & Restart Broadcaster.
After restarting
- Wait for the Broadcaster to show online in ZEN Master.
- Check that inputs and outputs reconnect. Zixi pull inputs retry every 2 to 8 seconds, and Zixi push outputs within about 4 to 11 seconds. On a busy Broadcaster, pull targets through ZEN Master can take longer to all return.
- Take the Broadcaster out of Maintenance.
- Work through the Post Upgrade Verification ChecklistPost Upgrade Verification Checklist.