Service configuration

The vidispine service user

The post-installation script in the packages will create the vidispine user and group if they do not exist.

If you want to make sure that the vidispine user has a specific UID and GID, then create the vidispine user and group manually before installing any packages.

Service dependencies

If you’re running all components on the same server, then it can be beneficial to make sure that the transcoder and OpenSearch are started before VidiCore.

Create a systemd unit.d directory and override the service dependencies in a drop-in file:

$ vi /etc/systemd/system/vidispine.service.d/local.conf
[Unit]
Wants=transcoder.service opensearch.service

$ systemctl daemon-reload
$ systemctl enable vidispine

Setting JVM options

Create a systemd drop-in file and override the default JAVA_OPTS:

$ vi /etc/systemd/system/vidispine.service.d/local.conf
[Service]
Environment="JAVA_OPTS=-Xmx8192m -Xss256k -XX:+CrashOnOutOfMemoryError -Djava.security.properties=/etc/vidispine/java.security"

Please check the currently active values for JAVA_OPTS before setting JAVA_OPTS as shown above and ensure that no settings are accidentally removed.

In particular, these settings are highly important:

  • -XX:+CrashOnOutOfMemoryError ensures that VidiCore is restarted in case of an out-of-memory situation. Failing to do so may lead to an unstable internal state of VidiCore.
  • -Djava.security.properties=/etc/vidispine/java.security is relevant for ssh-based connections between VidiCore and the VSAs. Please do not remove it.