• Manuals

Browse the manual

• Introduction
  • System requirements
  • Licensing
  • Latest improvements
• Installation
  • Quick installation guide
  • Installing and running the Server
    • Installing the Server software
  • Silent installation
  • Upgrading an existing installation
    • Upgrading major versions
  • Allowing access through your firewall
  • Downloading a license
    • Windows license download
    • Mac OS license download
    • Linux license download
  • Starting and stopping the server
    • Microsoft Windows
    • Mac OS X
    • Linux
  • Installing relevant plugins in the Workbench
• Configuring and administering the server
  • Logging into the administrative interface
  • Adding locations for saving data
    • Adding a file system location
    • Rebuilding the index
  • Accessing files on, and writing to, areas of the server filesystem
  • Changing the listening port
  • Changing the tmp directory
    • Job node setups
  • Setting the amount of memory available for the JVM
  • Limiting the number of cpus available for use
  • Other configurations
    • HTTP settings
    • Audit log settings
    • Deployment of server information to CLC Workbenches
  • Server plugins
  • Queue
• Managing users and groups
  • Logging in the first time and the root password
  • User authentication using the web interface
    • Managing users using the web interface
    • Managing groups using the web interface
  • User authentication using the Workbench
    • Managing users through the Workbench
    • Managing groups through the Workbench
    • Adding users to a group
  • User statistics
• Access privileges and permissions
  • Controlling access to data
    • Setting permissions on a folder
    • Recycle bin
    • Technical notes about permissions and security
  • Global permissions
  • Customized attributes on data locations
    • Configuring which fields should be available
    • Editing lists
    • Removing attributes
    • Changing the order of the attributes
  • Filling in values
    • What happens when the sequence is copied to another data location?
    • Searching
• Job Distribution
  • Model I: Master server with execution nodes
    • Master and job nodes explained
    • User credentials on a master-job node setup
    • Configuring your setup
    • Installing Server plug-ins
  • Model II: Master server submitting to grid nodes
    • Requirements for CLC Grid Integration
    • Technical overview
    • Setting up the grid integration
    • Licensing of grid workers
    • Configuring licenses as a consumable resource
    • Configure grid presets
    • Controlling the number of cores utilized
    • Other grid worker options
    • Testing a Grid Preset
    • Client-side: starting CLC jobs on the grid
    • Grid Integration Tips
    • Understanding memory settings
• External applications
  • External applications integration: Basic configuration
  • External applications integration: Post-processing
  • External applications integration: Stream handling
  • External applications integration: Environment
    • Environmental Variables
    • Working directory
    • Execute as master process
  • External applications integration: Parameter flow
  • External applications integration: Velvet
    • Installing Velvet
    • Running Velvet from the Workbench
    • Understanding the Velvet configuration
  • External applications integration: Bowtie
    • Installing Bowtie
    • Understanding the Bowtie configuration
    • Parameter overview
    • Setting path for temporary data
    • Tools for building index files
  • Troubleshooting
    • Checking the configuration
    • Check your third party application
    • Is your Import/Export directory configured?
    • Check your naming
• Workflows
  • Installing and configuring workflows
  • Executing workflows
  • Automatic update of workflow elements
• Appendix
  • Use of multi-core computers
  • Troubleshooting
    • Check set-up
    • Bug reporting
  • Database configurations
    • Getting and installing JDBC drivers
    • Configurations for MySQL
  • SSL and encryption
    • Enabling SSL on the server
    • Logging in using SSL from the Workbench
    • Logging in using SSL from the CLC Server Command Line Tools
  • DRMAA libraries
    • DRMAA for LSF
    • DRMAA for PBS Pro
    • DRMAA for OGE or SGE
  • Consumable Resources
  • Third party libraries
• Bibliography

Linux

You can start and stop the CLC Genomics Server service from the command line. You can also configure the service to start up automatically after the server machine is rebooted.

During installation of the CLC Genomics Server a service script named CLCGenomicsServer is placed in /etc/init.d/ This script includes the name of the custom user account specified during installation for running the CLC Genomics Server process.

Starting and stopped the service using the command line:

To start the CLC Genomics Server:

sudo service CLCGenomicsServer start

To stop the CLC Genomics Server:

sudo service CLCGenomicsServer stop

To restart the CLC Genomics Server:

sudo service CLCGenomicsServer restart

To view the status of the CLC Genomics Server:

sudo service CLCGenomicsServer status

Start service on boot up:

On Red Hat Enteprise Linux and SuSE this can be done using the command:

sudo chkconfig CLCGenomicsServer on

How to configure a service to automatically start on reboot depends on the specific Linux distribution. Please refer to your system documentation for further details.

Troubleshooting

If the CLC Genomics Server is run as a service as suggested above, then the files in the installation area of the software and the data files created after installation in CLC Server File Locations will be owned by the user specified to run the CLC Genomics Server process. If someone starts up the CLC Genomics Server process as root (i.e. an account with super-user privileges) then the following steps are recommended to rectify the situation:

1. Stop the CLC Genomics Server process using the script located within the installation area of the CLC Genomics Server software. You can do that using the full path to this script, or by navigating to the installation area and running:

   sudo ./CLCGenomicsServer stop

2. Change ownership recursively on all files in the installation area of the software and on all areas specified as Server File Locations.

3. Start the CLC Genomics Server service as the specified user by using the service script:

   sudo service CLCGenomicsServer start

---