/
[JIL] Server Administration Dell v.6.0

[JIL] Server Administration Dell v.6.0

Owned by Christian Schabasser
Last updated: Nov 17, 2023
5 min read

Overview

The just:in linux appliance ships preinstalled with the 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)

If you require a specific CentOS version, when ordering a just:in linux appliance, please contact the ToolsOnAir support team.

User and Password

The system can be accessed with the following credentials via ssh.

User: justin Password: justin Example: ssh justin@IP-ADDRESS

Please note that there is no Linux GUI preinstalled on the just:in linux appliance, and that it is not recommended to install one. All set up processes can and should be done via the command line.

Network Settings

By default, the em1 Ethernet interface is set to DHCP, and the em2 Ethernet interface comes configured with a static IP Address (172.17.17.10/24). The iDrac port is set to DHCP as well.

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

ip addr

or

ifconfig -a

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

sudo ipmicfg -m

Integrated Dell Remote Access Controller (iDRAC)

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

Blackmagic Firmware Updater

IMPORTANT: Only update the Blackmagic Design driver if you have issues with the system. Please contact your local reseller or the ToolsOnAir Support System before applying any changes.

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

BlackmagicFirmwareUpdater status

No Firmware update is required if all inputs display the status “ok”. If the status is “not ok”, then use the following command to update the firmware. Remember to restart the system afterwards.

BlackmagicFirmwareUpdater update [device]

just:connect Configuration File & Logs

Config File

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

/var/justconnect/JustConnect.txt

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

sudo tme restart

Please note that you can save and restore the “JustConnect.txt” file within the Just Control user interface (Just Control Configuration panel -> System Tab -> Configurations) as well.

Logs

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

/var/log/justconnect

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

/var/log/tme

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

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

just:in linux engine

sudo systemctl restart tme

just:connect

sudo systemctl restart tjc

Both just:in linux engine and just:connect:

sudo tme restart

This command will also delete all existing log files from both, the just:in linux engine and just:connect and all the logs are saved to the internal RAID at “/media/internal_raid/tools/” automatically.

The tme status script

To get an overview of the server and the currently running processes, there is a “tme” status script available, which provides information such as system information, running processes, internal RAID state, AJA driver, etc. Run the following command to execute the “tme” status script:

sudo tme status

The output will look like this:

*****System Info**************************************************************************************************************************** Redirecting to /bin/systemctl status irqbalance.service Motherboard: X10DRW-iT CPU: Intel(R) Xeon(R) CPU E5-2660v4 @ 2.00GHz CPU Sockets: 2 CPU Cores: 14 Memory: 46G OS: CentOS Linux release 7.9.2009 (Core) Kernel: 3.10.0-1160.88.1.el7.toa.x86_64 IPMI Address: 10.39.1.47 CPU Governor Mode: Current active profile: throughput-performance mdadm: cannot open /dev/md127: No such file or directory Internal RAID State: Irqbalance State: inactive (dead) IrqAJA: ntv2dev0 2 *****Services******************************************************************************************************************************* smb.service loaded active running Samba SMB Daemon tjc.service loaded active running ToolsOnAir just:connect tme.service loaded active running ToolsOnAir Media Engine *****AJA Status***************************************************************************************************************************** ajantv2-dkms Version: 16.2.5 ajaretail Version: 16.2.5 *****Status TME Sessions******************************************************************************************************************** 1767 1798 1832 1885 1924 1969 2000 3074 *****TOA Media Engine Version*************************************************************************************************************** Error: No matching Packages to list *****TOA Config Version********************************************************************************************************************* Name : toa-config_testing Version : 0.9.24

Automatic Server Restarts

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

(crontab -l 2>/dev/null; echo "0 2 * * * /usr/bin/tme restart") | sudo crontab -

This command restarts the services (“tme” and “tjc”) every day at 2 A.M. (02:00h).

Please consult your local ToolsOnAir VAR or the ToolsOnAir Support Team before activating the cronjob.

Daylight saving time

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

To get the correct new time applied to the recording engine, the services (“tme” and “tjc”) have to be restarted. Thereafter, restart the Just Control client application as well. Please note that by restarting the recording services, any ongoing recording will be stopped. Therefore, we recommend stopping recording manually before restarting the recording services.

Software Updates

Please contact your local ToolsOnAir VAR or the ToolsOnAir Support Team directly, by creating a support ticket, if you want to update your just:in linux appliance.

Related content

→ Use the sidebar to navigate.