---
title: List of alerts
url: https://doc2.pstreamer.tv/en/manual/extras/alert_codes.html
lang: en
product: Perfect Streamer
version: 2.0.2.423
---

# List of alerts

The manual refers to alerts by code, while the web interface shows an alert by its **token**, a short English name such as `no-data`. The code is shown instead of the token only until the list of codes has loaded. In the HTTP API, in external notification destinations and in script variables an alert arrives with its numeric code ([External alert delivery](../meshwork/alerts.md#meshwork-alert-delivery), [External scripts for alerts](alert_scripts.md#extras-alert-scripts)). The table below links the one to the other.

How an alert works, its levels and states are described in [How an alert works](../meshwork/alerts.md#meshwork-alerts-model), and the detailed conditions by group in [Alert code catalogue](../meshwork/alerts.md#meshwork-alert-codes). The level in the table is the one the alert is raised with; “warning, then error” means two configurable thresholds ([Alerter settings](../meshwork/alerts.md#meshwork-alerts-settings)). The “Since” column gives the version in which the code appeared.

## Streams: state and work cycle

| Code | Token | Level | Meaning and what to do | Since |
| --- | --- | --- | --- | --- |
| 1 | `io-error` | critical | An input or output has gone into the error state: the stream has lost its source or delivery. Check the source or the destination; the cause is in the input or output row. | 2.0.0 |
| 2 | `hard-error` | requires administrator action | Unrecoverable error in the stream’s work cycle. Reset it: pause the stream and start it again. | 2.0.0 |
| 3 | `no-data` | warning | A running stream has delivered no data for longer than the timeout. Check the source and the active input. | 2.0.0 |
| 4 | `low-bitrate` | warning | The stream bitrate stays below the set minimum. Check the source. | 2.0.0 |
| 13 | `admin-wait` | requires administrator action | The stream is stopped, waiting for the administrator: no usable input is left (there are no inputs or all are paused). Add an input or unpause one. | 2.0.0.3 |
| 14 | `io-admin-wait` | requires administrator action | An input or output has stopped by itself and retries do not restore it. Fix the cause and restart it. | 2.0.0.4 |
| 27 | `input-fallback` | warning | The stream is running on a backup input: the main input has failed. Check the main input. | 2.0.0.11 |
| 39 | `stream-thread-cpu` | warning | The stream’s processing worker thread is heavily loading a CPU core. | 2.0.0.70 |
| 58 | `sync-gap-resync` | error | A source PCR jump beyond the gap window broke the output; the buffered data was discarded. Check the source. | 2.0.2.336 |
| 59 | `sync-rt-resync` | warning | The output was resynchronised to real time: the feed does not sustain the configured delay. Increase the delay or check the source. | 2.0.2.336 |
| 60 | `stream-no-source` | critical | A running stream has no feeding input left. Check the inputs. | 2.0.2.340 |
| 61 | `sync-gap-absorbed` | information | A source PCR jump beyond the gap window was absorbed without loss. No action needed. | 2.0.2.348 |
| 62 | `cam-pipe` | error | A separate CI module is unavailable or has stopped returning packets; the input passes the stream on without descrambling. | 2.0.2.359 |
| 65 | `backup-input-error` | warning | The stream runs through one input while its other inputs are in error: the backup is faulty. Check the backup inputs. | 2.0.2.420 |

## Transport stream compliance (TR 101 290)

| Code | Token | Level | Meaning and what to do | Since |
| --- | --- | --- | --- | --- |
| 5 | `pcr-disc` | error | TR 101 290, 2.3: repeated PCR discontinuities. Check the source. | 2.0.0.2 |
| 6 | `pcr-int` | error | TR 101 290, 2.3a: PCR repetition interval above 40 ms. Check the source encoder or multiplexer. | 2.0.0.2 |
| 7 | `pat-int` | error | TR 101 290, 1.3: PAT repetition interval above 500 ms. Check the source. | 2.0.0.2 |
| 8 | `pmt-int` | error | TR 101 290, 1.5: PMT repetition interval above 500 ms. Check the source. | 2.0.0.2 |
| 9 | `pts-int` | warning | TR 101 290, 2.5: PTS interval above 700 ms. Check the source encoder. | 2.0.0.2 |
| 10 | `pcr-acc` | warning | TR 101 290, 2.4: PCR accuracy worse than 500 ns. Check the source and the network up to the node. | 2.0.0.2 |
| 11 | `tstd-video` | warning | TR 101 290, 3.3: video T-STD buffer. Since version 2.0.2.366 this alert is not raised; the metric remains diagnostic. | 2.0.0.2 |
| 12 | `pcr-drift` | warning | PCR drift above 30 ppm. The metric is sensitive to the node’s CPU load; compare with the load before blaming the source. | 2.0.0.2 |
| 15 | `cc-error` | warning | TR 101 290, 1.4: continuity counter errors above the threshold over a short window, i.e. packet loss. Check the network up to the node. | 2.0.0.6 |
| 46 | `psi-crc` | error | TR 101 290, 2.2: CRC errors in PSI tables. Check the source. | 2.0.0.94 |
| 47 | `transport` | error | TR 101 290, 2.1: the transport_error_indicator flag is set: errors at the source or in the reception path. | 2.0.0.94 |
| 48 | `si-repetition` | warning | TR 101 290, 3.2: SI table repetition interval exceeded (SDT, EIT, TDT, NIT). | 2.0.0.94 |
| 49 | `tr101290` | error | Overall verdict: the stream does not comply with TR 101 290. Details are in the stream’s TR 101 290 report. | 2.0.0.94 |

## Node resources and hardware

| Code | Token | Level | Meaning and what to do | Since |
| --- | --- | --- | --- | --- |
| 16 | `cpu` | warning, then error | Server CPU load above the threshold. Reduce the load or move streams. | 2.0.0.7 |
| 17 | `memory` | warning, then error | Server memory use above the threshold. | 2.0.0.7 |
| 18 | `pss-cpu` | warning, then error | Streamer process CPU above the threshold. | 2.0.0.7 |
| 19 | `pss-memory` | warning, then error | Streamer process memory above the threshold. | 2.0.0.7 |
| 20 | `tc-cpu` | warning, then error | Total transcoder CPU above the threshold. | 2.0.0.7 |
| 21 | `tc-mem` | warning, then error | Total transcoder memory above the threshold. | 2.0.0.7 |
| 22 | `net-load` | warning, then error | Network interface load above the threshold (per interface). Check the bandwidth. | 2.0.0.7 |
| 23 | `gpu` | warning, then error | GPU load above the threshold (per device). | 2.0.0.7 |
| 24 | `disk-usage` | warning, then error | DVR storage fill above the threshold. Free up space or reduce the archive depth. | 2.0.0.7 |
| 25 | `storage-error` | requires administrator action | The DVR storage file system is unavailable. Check the disk and its mount. | 2.0.0.7 |
| 40 | `dvb-thread-cpu` | warning, then error | The DVB adapter worker thread is heavily loading a CPU core. | 2.0.0.70 |
| 41 | `dvb-no-lock` | error | The DVB frontend has lost signal lock. Check the antenna, the cable and the tuning parameters. | 2.0.0.70 |
| 42 | `dvb-signal` | warning | DVB signal level below the threshold. | 2.0.0.70 |
| 43 | `dvb-snr` | warning | DVB signal SNR (quality) below the threshold. | 2.0.0.70 |
| 44 | `dvb-ber` | warning | DVB bit errors (BER) over the interval above the threshold. | 2.0.0.70 |
| 45 | `dvb-ucb` | warning | DVB uncorrected blocks over the interval above the threshold. | 2.0.0.70 |
| 63 | `dvb-no-pat` | error | The DVB frontend holds lock, but the multiplex is not received. Check the frequency and the transponder parameters. | 2.0.2.391 |
| 64 | `gpu-memory` | warning, then error | NVIDIA GPU video memory use above the threshold (per device). | 2.0.2.416 |

## Meshwork and node life cycle

| Code | Token | Level | Meaning and what to do | Since |
| --- | --- | --- | --- | --- |
| 26 | `node-down` | error | A Meshwork node has not responded for longer than the set delay. Check the node and the connection to it. | 2.0.0.9 |
| 28 | `service-started` | information | The streamer service has finished starting. No action needed. | 2.0.0.25 |
| 37 | `cluster-node-collision` | requires administrator action | Two nodes of one domain use the same name. Rename one of them. | 2.0.0.55 |

## DVR recording

| Code | Token | Level | Meaning and what to do | Since |
| --- | --- | --- | --- | --- |
| 29 | `dvr-write-error` | error | Writing DVR segments or the index fails. Check the disk space and permissions. | 2.0.0.27 |
| 30 | `dvr-recording-stalled` | warning | DVR recording has stalled: the input is working, but new segments have not been saved for a long time. Check the disk. | 2.0.0.27 |
| 31 | `dvr-archive-degraded` | warning | The recent DVR archive coverage has gaps. | 2.0.0.27 |
| 32 | `dvr-index-error` | requires administrator action | The DVR archive index is corrupted and cannot be recovered. Check the disk. | 2.0.0.27 |
| 50 | `dvr-rw-time` | warning | DVR chunk read or write time on the disk is high. Check the disk. | 2.0.0 |

## Configuration, transcoders, OTT, certificates and licence

| Code | Token | Level | Meaning and what to do | Since |
| --- | --- | --- | --- | --- |
| 33 | `config-load-error` | requires administrator action | The settings file failed to load at start-up; the service came up on the last good configuration. Fix the file. | 2.0.0.30 |
| 34 | `ott-audio-unsupported` | warning | In LL-HLS / DASH mode, audio tracks in an unsupported codec were dropped (AAC and AC-3 are supported). | 2.0.0.36 |
| 35 | `cert-acme-error` | warning | Failed to issue or renew the HTTPS certificate via ACME. Check the domain name and that the port is reachable. | 2.0.0.43 |
| 36 | `transcoder-config-error` | requires administrator action | A configured transcoder failed to load at start-up: no executable or device. Install the transcoder package. | 2.0.0.50 |
| 38 | `stream-missing-transcoder` | requires administrator action | The stream requires a transcoder that this node does not have. Install the transcoder or move the stream. | 2.0.0.56 |
| 55 | `lic-expiry` | warning | The licence is expiring: a warning two weeks ahead; after expiry, requires administrator action, and the service stops. Renew the licence. | 2.0.1.262 |
| 56 | `lic-tamper` | requires administrator action | The node’s licence has been found not to be genuine; the service will not start. Contact support. | 2.0.2.267 |
| 57 | `lic-unsupported` | requires administrator action | The licence is genuine, but this version no longer accepts its generation. Contact support. | 2.0.2.301 |

## Descrambling: CI/CAM and BISS

| Code | Token | Level | Meaning and what to do | Since |
| --- | --- | --- | --- | --- |
| 51 | `cam-module-removed` | requires administrator action | The CAM module has been removed. Insert the module. | 2.0.0.162 |
| 52 | `cam-no-subscription` | warning | The CAM module reports that the programme is not paid for. Check the subscription on the card. | 2.0.0.162 |
| 53 | `cam-ca-error` | error | Unrecoverable error of the CI channel or conditional access. | 2.0.0.162 |
| 54 | `dvb-descramble-fail` | error | A programme with a BISS key set or a CAM assigned remains scrambled. Check the key or the module. | 2.0.0.200 |