From Beocat
Jump to: navigation, search
(How are the filesystems on Beocat set up?)
(How do I connect to Beocat)
Line 16: Line 16:
| style="text-align:right" | <tt>eID Password</tt>
| style="text-align:right" | <tt>eID Password</tt>
{| class="wikitable"
!colspan="2" | Supported Connection Software (Latest Versions of Each)
!rowspan="3" | Shell
| [ Putty]
| ssh from openssh
!rowspan="4" | File Transfer Utilities
| [ Filezilla]
| [ WinSCP]
| scp and sftp from openssh
!rowspan="2" | Combination
| [ MobaXterm]
== How do I compile my programs? ==
== How do I compile my programs? ==
=== Serial programs ===
=== Serial programs ===

Revision as of 09:02, 20 February 2015

How do I connect to Beocat

Connection Settings
Port 22
Username eID
Password eID Password
Supported Connection Software (Latest Versions of Each)
ssh from openssh
File Transfer Utilities
scp and sftp from openssh

How do I compile my programs?

Serial programs


ifort or gfortran


icc, gcc and g++

Parallel programs


mpif77 or mpif90


mpicc or mpic++

How are the filesystems on Beocat set up?

Mountpoint Local / Shared Size Filesystem Advice
/home Shared 350TB total glusterfs on top of xfs Good enough for most jobs
/tmp Local >100GB (varies per node) ext4 Good for I/O intensive jobs

Usage Advice

For most jobs you shouldn't need to worry, your default working directory is your homedir and it will be fast enough for most tasks. I/O intensive work should use /tmp, but you will need to remember to copy your files to and from this partition as part of your job script. This is made easier through the $TMPDIR environment variable in your jobs.

Example usage of $TMPDIR in a job script

 1 #!/bin/bash
 3 #copy our input file to $TMPDIR to make processing faster
 4 cp ~/experiments/ $TMPDIR
 6 #use the input file we copied over to the local system
 7 #generate the output file in $TMPDIR as well
 8 ~/bin/my_program --input-file=$TMPDIR/ --output-file=$TMPDIR/
10 #copy the results back from $TMPDIR
11 cp $TMPDIR/ ~/experiments/results.$SGE_JOBID

You need to remember to copy over your data from $TMPDIR as part of your job. That directory and its contents are deleted when the job is complete.

Help! When I submit my jobs I get "Warning To stay compliant with standard unix behavior, there should be a valid #! line in your script i.e. #!/bin/tcsh"

Job submission scripts are supposed to have a line similar to '#!/bin/bash' in them to start. We have had problems with people submitting jobs with invalid #! lines, so we enforce that rule. When this happens the job fails and we have to manually clean it up. The warning message is there just to inform you that the job script should have a line in it, in most cases #!/bin/tcsh or #!/bin/bash, to indicate what program should be used to run the script. When the line is missing from a script, by default your default shell is used to execute the script (in your case /usr/local/bin/tcsh). This works in most cases, but may not be what you are wanting.

Help! When I submit my jobs I get "A #! line exists, but it is not pointing to an executable. Please fix. Job not submitted."

Like the above, error says you need a #!/bin/bash or similar line in your job script. This error says that while the line exists, the #! line isn't mentioning an executable file, thus the script will not be able to run. Most likely you wanted #!/bin/bash instead of something else.

Help! My jobs keep dying after 1 hour and I don't know why

Beocat has default runtime limit of 1 hour. If you need more than that, or need more than 1 GB of memory per core, you'll want to look at the documentation here to see how to request it.

In short, when you run qsub for your job, you'll want to put something along the lines of '-l h_rt=10:00:00' before the job script if you want your job to run for 10 hours.

Help my error file has "Warning: no access to tty"

The warning message "Warning: no access to tty (Bad file descriptor)" is safe to ignore. It typically happens with the tcsh shell.

Help! My job isn't going to finish in the time I specified. Can I change the time requirement?

Generally speaking, no.

Jobs are scheduled based on execution times (among other things). If it were easy to change your time requirement, one could submit a job with a 15-minute run-time, get it scheduled quickly, and then say "whoops - I meant 15 weeks", effectively gaming the job scheduler. In fact, even the administrators cannot change the run-time requirement of a particular job. In extreme circumstances and depending on the job requirements, we may be able to manually intervene. This process prevents other users from using the node(s) you are currently using, so are not routinely approved. Contact Beocat support (below) if you feel your circumstances warrant special consideration.

Help! My perl job runs fine on the head node, but only runs for a few seconds and then quits when submitted to the queue.

Perl doesn't like getting called straight from the scheduler. However, there is a fairly easy workaround. Create a shell wrapper script that calls perl and its program.

For instance, I can create a script called that looks like this:

#$ -l h_rt=1:00:00,mem=1G
/usr/bin/perl /path/to/my/

Make this wrapper program executable:

chmod 755

Then submit it with


Of course, the name of this script isn't important, as long as you change the corresponding chmod and qsub commands.

Help! When using mpi I get 'CMA: no RDMA devices found' or 'A high-performance Open MPI point-to-point messaging module was unable to find any relevant network interfaces'

This message simply means that some but not all nodes the job is running on have infiniband cards. The job will still run, but will not use the fastest interconnect we have available. This may or may not be an issue, depending on how message heavy your job is. If you would like to not see this warning, you may request infiniband as a resource when submitting your job. -l infinband=TRUE

Common Storage For Projects

Sometimes it is useful for groups of people to have a common storage area. If you already have a project you can do the following:

  • Create a directory in one of the home directories of someone in your group, ideally the project owner's.
    • mkdir $directory
  • Change the group to the name assigned by the Beocat admins
    • chgrp -R $group_name $directory
  • Set the directory writeable and sticky for the group
    • chmod g+ws $directory
  • Change your umask to 002 (there will probably be a setting for it in your file transfer utilities, also). This step needs to be done by all group members.
    • umask 002 needs to go above if $- != *i*  ; then in your ~/.bashrc file
  • Finally logout and log back in

How do I get more help?

There are many sources of help for most Linux systems.

Unix man pages

Linux provides man pages (short for manual pages). These are simple enough to call, for example: if you need information on submitting jobs to Beocat, you can type 'man qsub'. This will bring up the manual for qsub.

GNU info system

Not all applications have "man pages." Most of the rest have what they call info pages. For example, if you needed information on finding a file you could use 'info find'.

This documentation

This documentation is very thoroughly researched, and has been painstakingly assembled for your benefit. Please use it.

Contact support

Support can be contacted here. Please include detailed information about your problem, including the job number, applications you are trying to run, and the current directory that you are in.