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 just:control 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. The IPMI port gets a static IP-Address 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 (Legacy)

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 stores all Channel related information (settings, presets…) in following configuration file:

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

Logs

just:connect 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 here:

The just:in linux engine saves logs files for each channel as well. These log files get saved here:

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 (this command will delete all existing log files from both, just:in linux engine and just:connect and saves all logs to the internal RAID at /media/internal_raid/tools/):

Automatic Server Restarts

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

This command restarts the server everyday at 2AM.

Server Restart with Channels in Schedule Mode

If you have to restart the server, please make sure that you are following these steps, when you are working with Channels in Schedule Mode:

• Stop the Scheduled Recording for all Channels running in Schedule Mode

• Switch all Channels to Crash Mode

• Restart the server

• Switch the Channels back to Schedule Mode

Software Updates

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