First start and activation¶
Temporary activation and startup¶
The temporary version has no limit on the number of streams. After installation the pss service is inactive, since activation is required to start it. For temporary activation, run the script:
$ /opt/pss/tools/activate.sh
The pss service will be started and set to start automatically. The script can be given the path to a licence file; without an argument the bundled trial licence is applied. The file itself is applied by the pss_lic utility, which also performs every other operation on the key — see PSS Lic Perfect Streamer Toolkit v2.1 — the node licence.
Check that the service has started:
$ systemctl status pss
If there are problems, read the service log. Where it is located, and why the cause of the service not coming up at all has to be looked for in the system journal rather than in the file, is described in Service log.
Initial settings¶
Connect to the web interface through a browser:
http://host:8808
Login: admin
Password: admin
Two web interfaces are available: the new (main) one at the path /admin and the classic one at the path /classic.
Default service ports:
Service |
HTTP |
HTTPS |
|---|---|---|
Web interface and HTTP API |
8808 |
43981 |
OTT distribution (HTTP server) |
43972 |
43982 |
EPG server |
43973 |
43983 |
Right after the installation only the HTTP port of the web interface, 8808, is available. It is set in the shipped pss_default.json file, from which the working pss.json is created at the very first start; that file describes no other service, so the remaining ports of the table are opened only after the corresponding service has been configured, and HTTPS only after TLS has been enabled and a certificate installed. If the web-server.bind-port key is absent from the settings, the service uses the built-in fallback value 43971.
Be sure to change the administrator login and password in the administrator list of the web interface. Accounts are assigned roles: Admin (full access), Restricted admin (viewing and pausing streams), Viewer (viewing only).
Change the web-interface port if you need to, in the web-server settings. This does not need a restart of the service: it closes the old port and opens the new one itself, so the current connection drops and you have to reconnect on the new port.
Information about the current licence is shown on the License screen.
Permanent activation¶
The protection system supports software (SL) and USB (HL) keys. Activation is performed in one of two ways: on the “License” screen of the web interface (License) or from the console with the pss_lic utility (PSS Lic Perfect Streamer Toolkit v2.1 — the node licence). The console procedure is described below — it does not depend on the web interface being reachable, and it lets you name the required key when there are several of them.
Export the C2V data for the activation request and send the file to the supplier:
$ /opt/pss/tools/pss_lic c2v --out host.c2v
Apply the V2C file sent by the supplier and restart the service:
$ /opt/pss/tools/pss_lic apply --in license.v2c $ sudo systemctl restart pss
Check the activation data on the License screen.
If the node sees several keys, the first step has to name the one you want — see Exporting the data for the supplier.
The key is chosen when the service starts, and the service does not revisit that choice while it runs. A USB key that is plugged in, whether the trial licence is still active or has already expired, is therefore picked up only from the next start: restart the service through the web interface or with sudo systemctl restart pss.
When the annual or trial licence expires¶
The node gives warning of the expiry in advance: two weeks before the end of the term it raises an alert, and once the term has run out, it escalates that alert to the level that requires administrator action and stops the service itself. The service will not come back up until a valid licence is on the node, so trying to restart it by hand achieves nothing.
If the pss service does not start, enter the command:
$ journalctl -u pss -n 20
The following error means that the Perfect Streamer licence has expired:
LDK Protection System: Feature has expired (H0041)
The node responds in the same way to a licence found not to be genuine: it stops the service, and the service no longer comes up. In the log this is the neighbouring line: it begins the same way, !!! Licensing error, but what follows speaks not of an expired term but of a licence not found to be genuine. These two refusals have to be told apart by the text, not by the start of the line; the remedy for the second is to install a genuine licence on the node (License, PSS Lic Perfect Streamer Toolkit v2.1 — the node licence).
