Overview

The just:in linux appliance ships preinstalled with following components:

• Minimal CentOS installation (CentOS 7.x)

• Video card driver (AJA)

• just:in linux engine (TOA Media Engine = tme)

• just:connect (TOA just:connect = tjc)

just:in linux engine (tme) and just:connect (tjc) start automatically after the OS boot process. If they are configured properly, both services can communicate with the macOS based Just Control application immediately.

Deployment

The just:in linux appliance comes preinstalled with a specific CentOS 7.x release:

• 7.4 (1708)

• 7.5 (1804)

• 7.6 (1810)

• 7.7 (1908)

• 7.8 (2003)

• 7.9 (2009)

User and Password

The system can be accessed with following credentials via ssh.

Network Settings

By default em1 is set to DHCP and em2 gets configured with a static IP-Address (172.17.17.10/24). The IPMI port gets set to DHCP as well.

Open

When connected to the just:in linux appliance with ssh, the IP addresses can be displayed with one of the following commands:

or

The IP address for the IPMI port gets shown at startup, when there is a monitor connected to the server (VGA port) or the address can be displayed with following command, when connected with ssh:

IPMI

As mentioned above, the server can also be accessed via the IPMI port. Open a browser and enter the IPMI IP-Address (Username: ADMIN, Password: will be provided upon request).

Open

Blackmagic Firmware Updater

In some situations the Blackmagic video card needs a Firmware update. Verify if the card is working properly with the installed driver version by using the following command:

No Firmware update is required if all inputs display the status ok. If the status is not ok use following command to update the firmware. Restart the system afterwards.

just:connect Configuration File & Logs

Config File

just:connect (tjc) stores all Channel related information (channel settings, presets, etc.) in following configuration file:

Delete this file if there is a major problem with the system. After deleting the config file, tme and just:connect (tjc) must be restarted.

Logs

just:connect (“tjc”) saves log files for each recording channel independently. There is log file for each just:connect start and the just:connect log files are located at:

The just:in linux engine (“tme”) saves logs files for each channel as well. These log files get saved at:

Restarting the just:in linux engine and just:connect service

With following commands the just:in linux engine and/or the just:connect service can be restarted:

just:in linux engine

just:connect

Both just:in linux engine and just:connect:

The tme status script

In order to get an overview about the server and the current running processes, there is a “tme” status script available, which provides information like system information, running processes, internal RAID state, AJA driver, etc. Run following command to execute the tme status script:

The output will look like this:

Automatic Server Restarts

If the services should be rebooted automatically, a cronjob has to be activated. This can be done with the following command as root:

This command restarts the services (“tme” and “tjc”) everyday at 2 A.M.

Daylight saving time

The typical implementation of DST is to set clocks forward by one hour in the spring and to set clocks back by one hour in autumn to return to standard time. This could affect recording workflows when working with Computer Time as Timecode Source and especially when working in Schedule Mode and NTP synchronised setups.

In order to get the correct new time applied to the recording engine, the services (“tme” and “tjc”) have to be restarted. Afterwards restart the Just Control application as well. Please beware that by restarting the recording services, possible ongoing recording will be stopped. Therefore we recommend to stop recording manually before restarting the recording services.

Software Updates

Please contact your local ToolsOnAir reseller or ToolsOnAir directly, if you want to update your just:in linux appliance.