Thru Node Installation Linux
Navigate to the Organization that needs Node access
Select "Thru Node" from the available options
To add a new Node:
Click the Add button
Enter a name for your Node
Find your newly created Node in the list and click "Download Thru Node"
Select the linux-x64 option to download
The Linux Thru Node installation script is provided in two forms :
Crontab install for non root/sudo users
Systemd install script which requires sudo permissions.
Which method should you use?
If you don’t have root access, use the Crontab installation.
If you do have root access and want better service management, use the Systemd installation.
If sudo is required in your environment please contact relevant parties to acquire sudo access before installing.
Copy the shell script from the Thru Node Installation window.
When you execute the script, the package is downloaded and extracted.
This will then guide you through the rest of the setup.
You will be prompted to confirm the installation location :
Enter location to install node Default location is /home/user/Thru/{NodeID}/
You will be prompted to confirm the TempRepository. (This is using as a cache for the node - make sure you have enough space.)
Enter working directory location Default location is /home/user/Thru/{NodeID}/TempRespository
You will be prompted to confirm the location of the log directory.
Enter log directory location Default location is /home/user/Thru/{NodeID}/logs
Note : When a Thru Node is deleted in the UI, the corresponding running Thru Node will automatically uninstall the next time it attempts to check for an update.
TempRepository : Varies depending on the type of flow configurations. For LAN transfers only, a minimum of 100GB is recommended. For high file volumes and large files, storage may need to be as much as 1TB. Retention of files and configuration of retention policies will also affect storage requirements.
Check if the Thru Node service is running:
systemctl status thru-node # For Systemd installsIf using Crontab, confirm the scheduled job exists by running:
crontab -l