BGPVR Operator guide
Operator guide

Monitor: Technical tab

Monitor › Technical: the server's deeper detail in one tab, on every plan. AI Queue, Hardware Pool, Exposed Hardware, Storage, Stream Health and Security. Open it after Monitor › Now and System when you hunt a fault: is the AI helper working, can it see the recordings folder, which channels fail their stream checks, who was refused. It refreshes every 10 seconds while it is shown. The old Live Status page and its layout editor are gone (2.9.498); old links to it open this tab.

On this page
  1. Live Status is now Monitor › Technical (2.9.498)
  2. Check the AI jobs
  3. Inspect accelerators and the hardware pool
  4. Check that storage paths are mounted for the server and the AI helper
  5. Run and tune the stream checks
  6. Review security events
  7. Refusal codes in security events (2.9.503)
  8. Watch out

Live Status is now Monitor › Technical (2.9.498)

Sidebar › Monitor › Technical, or the address #monitor/technical. Old Live Status links and bookmarks open it. The tuners, frequencies on air (which channels share a tuner), timeshift buffers, disks and graphics cards are on Monitor › System; recordings in progress are on the Recordings page.

Check the AI jobs

AI Queue lists the latest jobs, pending, running, failed and done, with their task, title, status and progress. Stream checks and subtitles go through this queue, so a long pending list means the AI helper is not keeping up or not running.

Inspect accelerators and the hardware pool

Exposed Hardware lists the devices the server container sees (GPU, TPU, Hailo) with Enabled or Disabled and the last scan time. An NVIDIA card shows its load, memory, temperature and power, and the persistence-mode note. Rescan detects them again. Hardware Pool adds up the local devices and those of online nodes, with the local and node tuners.

Check that storage paths are mounted for the server and the AI helper

Storage lists every path in use (data, recordings, films, logs, picons and any recording-profile path) with Visible or Missing for the main server and for the AI helper, and OK or Needs Mount per row. The header reads "All Services" or "Check Mounts".

Run and tune the stream checks

In Stream Health tick Live Monitor, set Interval (60 to 86400 s), Sample (10 to 300 s) and Max Channels (1 to 20), then press Save. Run Now starts a pass at once and says how many checks it queued and skipped. Results show per source and as recent checks with a score from 0 to 100. The form is not refreshed while you type in it or while it holds values you have not saved; Save shows the saved values.

Review security events

Security shows the client and invite counts, the allowed and refused events of the last 24 hours, the locker modes and the latest events with the user, decision, reason, address and risk score.

Refusal codes in security events (2.9.503)

Every refused play is stored with a short numeric code. The apps and the web player get the same code beside a plain message (HTTP statuses are unchanged), and the earlier reason word still comes with it, so older apps and scripts keep working. A client's Devices & security tab (Activity) shows the matching line, for example "Refused: the server’s stream limit was reached"; Monitor › Technical › Security keeps showing the reason word under each event. What the codes mean for you: 201 the subscription has expired; 202 the account is not active; 210 the channel is not in the package; 211 live TV is not in the package; 220 the account already watches on every screen it allows; 221 the server’s stream limit was reached (the viewer reads "service busy"); 222 a family member is on as many screens as the account holder allows; 230 the IP address is not allowed; 231 the device (MAC) is not allowed; 232 a security block applies; 233 a place the locker does not know; 234 it looked like a shared account; 235 every trusted place is in use; 236 an unusual place; 240 adult content without the PIN; 250 the channel plays only in BGPVR Player; 260 Live+ is busy; 299 a temporary technical problem.

Watch out

  • The Edit Layout of the old page is gone: cards can no longer be dragged or hidden, and a layout saved there is not used. The order is fixed: AI Queue, Hardware Pool and Exposed Hardware, Storage, Stream Health, Security.
  • A group whose module is off or not in the licence (AI media, stream health, Security Locker, the node parts of the hardware pool) is not shown.
  • Storage is about which paths each container can see, not free space (free space is on System › Storage). If the AI helper cannot be reached, its whole column reads Missing and an "AI sidecar check failed" line appears: a helper problem, not a disk problem.
  • Stream Health only checks channels somebody is watching (connections seen in the last 90 seconds), at most Max Channels per pass, and skips a channel checked within Interval. Run Now works when Live Monitor is off, but not inside that wait: a pass that reports "queued 0" usually means the wait or nobody watching, not a failure.
  • Stream checks run as jobs in the AI queue, so they give results only while the AI helper runs. If scores never appear, look at AI Queue.
  • Local Tuners in Hardware Pool counts every adapter below number 2000, SAT>IP tuners included.
  • Saving the stream health monitor's settings needs Manage Channels or Manage Relay Streams: for other staff logins that Save button is greyed out, with a note. Run Now works for every staff login, and so does Clear idle, which is on Monitor › System › Timeshift now.
  • Stream Health results (2.9.348): a probe now completes with the stream's own verdict (healthy, notice, warning or critical), and that verdict is what the Stream Health card and its alerts show. Before 2.9.348 the queue failed every probe on that verdict ("unsupported status") and stored it as failed, so every probed channel looked critical; a probe that really failed (a timeout, for example) is still recorded as failed.