Maintenance Tasks
Maintenance tasks operate on instance state, online streams, and proxy cache. Before running them, decide whether online playback may be affected. Afterward, check health, logs, metrics, and user paths.
System State
Section titled “System State”synctv system statssynctv system stream listsynctv system stream kick <STREAM_ID>| Operation | Use |
|---|---|
system stats | Inspect service, connection, and internal state |
system stream list | Find active media streams or abnormal streams |
system stream kick | Disconnect a stuck or abusive stream |
Slice Cache
Section titled “Slice Cache”synctv slice-cache statssynctv slice-cache evict-expiredsynctv slice-cache purgeproxy_slice_cache.enableddecides whether slice cache is enabled.- CLI commands provide stats, expiration eviction, and purge; they do not dynamically enable or disable cache.
purgeclears cache data. It does not affect PostgreSQL business data, but it lowers cache hit rate afterward.
Validate After Maintenance
Section titled “Validate After Maintenance”/health/readysucceeds.- Sign-in, room list, WebSocket, chat, and playback controls work.
- Provider browse, direct playback, and proxy playback work.
- Metrics do not show sustained errors.
- Logs do not show sustained database, Redis, Provider, or Realtime errors.
Production diagnosis is in Troubleshooting. Metrics guidance is in Observability Runbook.