Server Installation

The currently supported software platforms for YarraServer are Ubuntu 12.04 LTS 64bit and Ubuntu 14.04 LTS 64bit, which can be downloaded here. It is possible to use both, the Server edition as well as the Desktop edition. It will be easier for users less familiar with Linux to use the Desktop edition (e.g., ubuntu-12.04.4-desktop-amd64+mac.iso) as it includes many helpful tools including graphical editors.

Note
At the moment, Ubuntu 12.04 LTS and Ubuntu 14.04 LTS are the only officially supported platforms for Yarra. Other Ubuntu versions and other Linux distributions might work, but may require modified installation and configuration steps, and have not been tested so far.

Please see these notes regarding the compatibility with Ubuntu 14.04 LTS.

Note
The initial installation of the server should be done by a person with at least basic knowledge of the Linux operating system.

 

General Server Installation

Install Ubuntu 12.04 or 14.04 using default installation options. After the installation has been finished and Ubuntu shows the graphical user interface, open a terminal shell (e.g., by typing “terminal” into the Ubuntu launcher “Dash home”).

Ubuntu 12.04: Upgrading GCC
When running YarraServer on Ubuntu 12.04, it is necessary to first upgrade the GCC compiler and runtime libraries to version 4.8. This can be achieved by typing the following commands in the command shell:

Install the following additional packages (sendmail is only required if the server should send notifications about the task status, which, however, is recommended):

Add the user “yarra” for access from the Yarra clients, and the user “yarraserver” to run the YarraServer software. Both users should be added to the user group “yarra”. By setting the shell to “/bin/false” for the user yarra, it is prevented that users can open a shell login on the server (note that the password for user yarra can be seen in the configuration file of the Yarra client). Therefore, the user yarra must have access only to the Yarra queue share. The users yarra and yarraserver must never have the same password! It is not recommended to run the YarraServer software with root rights.

 

Installation of QT 5.2.1

YarraServer requires the QT 5.2.1 runtime libraries, which are not shipped with Ubuntu and require manual installation. The easiest way is to open a graphical shell (terminal) and login as the user yarraserver:

Download and install QT 5.2.1 (for user yarraserver) using the following commands:

Go through the graphical installer and use all default options (there is no need to change anything). If you are connected to your server via ssh, you may see the following error message:

In this case, you have to install a local X server application for your client computer (e.g. Xming for Windows or XQuartz for Mac OS) and restart your ssh session (with the -X option, as listed above).

After the installation, edit the file .bashrc in the home directory of user yarraserver using the following command:

or, in case of a non-graphical ssh connection, using:

and add the following line at the end of the file:

 

Installation of the YarraServer package

Login with the account yarraserver and create the subfolder in the home directory, e.g. ~/yarra. It is recommended to set the permission of the folder to 750, so that only the user yarraserver and users of the group yarra can access the folder. Depending on the configuration/installation of your server, it can be advantageous to install the software at a different location (e.g., if the disk drives have been partitioned with only limited space for the home directories). In the following, it is assumed that the installation location is /home/yarraserver/yarra.

Download and extract the YarraServer installation zip file into this folder:

In most cases, the files will be extracted with correct file permissions. The folder ~/yarra should now look like this:

If the file and directory permission are equivalent to the settings shown above (except for the T in the permissions of queue/), no changes need to be made. Otherwise, the following command can be used to obtain a working configuration, which will set the permissions for all extracted files to 750:

Next, set special permissions for the “queue” directory:

In addition, lock the write permissions for the files “queue/YarraModes.cfg” and “queue/YarraServer.cfg”, so that clients under no circumstances can delete this file:

Logout of the ssh session, which brings you back to the user shell of the administrator account:

 

Installation and Configuration of SAMBA

Yarra clients connect to the server using the SMB network share. To provide the share, install the samba package with:

Set the SAMBA password for the user yarra. This should be the same password that was used when creating the user:

Edit the file /etc/samba/smb.conf. When the desktop edition of Ubuntu has been installed, this can be conveniently done using the editor gedit:

Add the following section to the end of the file:

In addition, change the following settings in the file (these are located at different positions in the file):

Save and close the file. Then restart the samba server.

 

Test Client Connectivity

It should now be possible to access the SAMBA share of the server from any Windows client in your network. To test this, open a command shell at a Windows client in your network and type the following command:

where [server IP] is the IP address of the server and [pwd of yarra] is the selected password of the user yarra. If the return value is “The command completed successfully.” then the server connection could be established. You should see now a network drive Y:\, containing the files YarraServer.cfg and YarraModes.cfg.

It is recommended to reboot the server when these steps have been finished. Afterwards, continue to configure the YarraServer, which is described in the next section.

Server Security
Note that additional configuration steps might be needed to properly securing your server. The steps described here are the minimum required procedures to bring the server into operation, but it is not said that these steps sufficiently secure the server. Please review the server configuration with your local IT department and review related documentation.