In this section, we’ll discuss some tips for solving problems with iceberg. It is suggested that you work through some of the ideas here before contacting the service desk for assistance.
When you get a username on the system, the first thing you need to do is to syncronise your passwords which will set your password to be the same as your network password.
Symptoms include many of the commands not working and just
bash-4.1$ being displayed instead of your username at the bash prompt.
This may be because you’ve deleted your
.bash_profile files - these are ‘hidden’ files which live in your home directory and are used to correctly set up your environment. If you hit this problem you can run the command
resetenv which will restore the default files.
If you are confident that you have no password or remote-access-client related issues but you still can not log onto iceberg you may be having problems due to exceeding your iceberg filestore quota.
If you exceed your filestore quota in your
/home area it is sometimes possible that crucial system files in your home directory gets truncated that effect the subsequent login process.
If this happens, you should immediately email
email@example.com and ask to be unfrozen.
Most of the time such problems arise due to due to Java version issues. As Java updates are released regularly, these problems are usually caused by the changes to the Java plug-in for the browser. Follow the trouble-shooting link from the iceberg browser-access page to resolve these problems. There is also a link on that page to test the functionality of your java plug-in. It can also help to try a different browser to see if it makes any difference. All failing, you may have to fall back to one of the non-browser access methods.
I cannot see my folders in /data or /shared
Some directories such as
/data/<your username> or
/shared/<your project/ are made available on-demand:.
For example, if your username is ab1def and you look in /data straight after logging in, you may not see /data/ab1def.
The directory is there, it has just not been made available (via a process called mounting) to you automatically.
When you attempt to do something with the directory such as
ls /data/ab1def or
cd /data/ab1def, the directory will be mounted automatically and will appear to you.
The directory will be automatically unmounted after a period of inactivity.
When a batch job that is initiated by using the
qsub command or
runabaqus commands, it gets allocated specific amount of virtual memory and real-time.
If a job exceeds either of these memory or time limits it gets terminated immediately and usually without any warning messages.
It is therefore important to estimate the amount of memory and time that is needed to run your job to completion and specify it at the time of submitting the job to the batch queue.
Please refer to the section on hitting-limits and estimating-resources for information on how to avoid these problems.
Each user of the system has a fixed amount of disk space available in their home directory.
If you exceed this quota, various problems can emerge such as an inability to launch applications and run jobs.
To see if you have exceeded your disk space quota, run the
quota Size Used Avail Use% Mounted on 10.1G 5.1G 0 100% /home/foo11b 100G 0 100G 0% /data/foo11b
In the above, you can see that the quota was set to 10.1 gigabytes and all of this is in use.
Any jobs submitted by this user will likely result in an
The recommended action is for the user to delete enough files to allow normal work to continue.
Sometimes, it is not possible to log in to the system because of a full quota,
in which case you need to contact
firstname.lastname@example.org and ask to the unfrozen.
There are two types of memory resources that can be requested when submitting batch jobs using the qsub command. These are, virtual memory (
-l mem=nnn) and real memory (
Virtual memory limit specified should always be greater than equal to the real memory limit specification.
If a job exceeds its virtual memory resource it gets terminated. However if a job exceeds its real memory resource it does not get terminated but an email message is sent to the user asking him to specify a larger
rmem= parameter the next time, so that the job can run more efficiently.
Running a program always involves loading the program instructions and also its data i.e. all variables and arrays that it uses into the computer’s memory. A program’s entire instructions and its entire data, along with any dynamic link libraries it may use, defines the virtual storage requirements of that program. If we did not have clever operating systems we would need as much physical memory (RAM) as the virtual storage requirements of that program. However, operating systems are clever enough to deal with situations where we have insufficient real memory (physical memory, typically called RAM) to load all the program instructions and data into the available RAM. This technique works because hardly any program needs to access all its instructions and its data simultaneously. Therefore the operating system loads into RAM only those bits (pages) of the instructions and data that are needed by the program at a given instance. This is called paging and it involves copying bits of the programs instructions and data to/from hard-disk to RAM as they are needed.
If the real memory (i.e. RAM) allocated to a job is much smaller than the entire memory requirements of a job ( i.e. virtual memory) then there will be excessive need for paging that will slow the execution of the program considerably due to the relatively slow speeds of transferring information to/from the disk into RAM.
On the other hand if the RAM allocated to a job is larger than the virtual memory requirement of that job then it will result in waste of RAM resources which will be idle duration of that job.
It is therefore crucial to strike a fine balance between the virtual memory and the physical memory allocated to a job:
-l memcluster scheduler parameter defines the maximum amount of virtual memory your job will be allowed to use. If your job’s virtual memory requirements exceed this limit during its execution your job will be killed immediately.
-l rmemcluster scheduler parameter and defines the amount of RAM that will be allocated to your job. The way we have configured SGE, if your job starts paging excessively your job is not killed but you receive warning messages to increase the RAM allocated to your job next time by means of the
It is important to make sure that your
-l mem value is always greater than your
-l rmem value so as not to waste the valuable RAM resources as mentioned earlier.
By default, an interactive session provides you with 2 Gigabytes of RAM (sometimes called real memory) and 6 Gigabytes of Virtual Memory.
You can request more than this when running your
qsh -l mem=64G -l rmem=8G
This asks for 64 Gigabytes of Virtual Memory and 8 Gigabytes of RAM (real memory). Note that you should
If your program fails with an Illegal Instruction error then it may have been compiled using (and optimised for) one type of processor but is running on another.
If you get this error after copying compiled programs onto Iceberg then you may need to recompile them on Iceberg or recompile them elsewhere without agressively optimising for processor architecture.
If however you get this error when running programs on Iceberg that you have also compiled on the cluster then you may have compiled on one processor type and be running on a different type.
You may not consistently get the illegal instruction error here as the scheduler may allocate you a different type of processor every time you run your program.
you can either recompile your program without optimisations for processor architecture or force your job to run on the type of processor it was compiled on using the
qsh parameter e.g.
-l arch=intel*to avoid being allocated one of the few AMD-powered nodes
-l arch=intel-x5650to use the Intel Westmere CPU architecture
-l arch=intel-e5-260to use the Intel Sandy Bridge CPU architecture
If you know the node that a program was compiled on but do not know the CPU architecture of that node then you can discover it using the following command (substituting in the relevant node name):
qhost | egrep '(ARCH|node116)'
If you prepare text files such as your job submission script on a Windows machine, you may find that they do not work as intended on the system. A very common example is when a job immediately goes into
Eqw status after you have submitted it.
The reason for this behaviour is that Windows and Unix machines have different conventions for specifying ‘end of line’ in text files. Windows uses the control characters for ‘carriage return’ followed by ‘linefeed’,
\r\n, whereas Unix uses just ‘linefeed’
The practical upshot of this is that a script prepared in Windows using Notepad looking like this:
#!/bin/bash echo 'hello world'
will look like the following to programs on a Unix system:
#!/bin/bash\r echo 'hello world'\r
If you suspect that this is affecting your jobs, run the following command on the system:
If you receive the error message:
error: no DISPLAY variable found with interactive job
the most likely cause is that you forgot the
-X switch when you logged into iceberg. That is, you might have typed:
ssh -X email@example.com
macOS users might also encounter this issue if their XQuartz is not up to date.
Some users have reported issues while connetcing to the system using WinSCP, usually when working from home with a poor connection and when accessing folders with large numbers of files.
In these instances, turning off
Optimize Connection Buffer Size in WinSCP can help:
Site Managerdialog click on the selected session and click edit button
Optimize Connection Buffer Size
Certain programs require esoteric fonts to be installed on the machine running the X server (i.e. your local machine).
Example of such programs are
qmon, a graphical interface to the Grid Engine scheduling software, and Ansys.
If you try to run
qmon or Ansys on a Linux machine and see strange symbols instead of the latin alphabet or get an error message that includes:
X Error of failed request: BadName (named color or font does not exist)
then you should try running the following on your own machine:
for i in 75dpi 100dpi; do sudo apt-get install xfonts-75dpi pushd /usr/share/fonts/X11/$i/ sudo mkfontdir popd xset fp+ /usr/share/fonts/X11/$i done
Note that these instructions are Ubuntu/Debian-specific; on other systems package names and paths may differ.
Next, try connecting to a cluster using
ssh -X clustername, start a graphical session then try running
If you can now run
qmon/Ansys without problems
then you need to add two lines to the
.xinitrc file in your home directory on your own machine
so this solution will continue to work following a reboot of your machine:
FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi
The RSA key fingerprint for Iceberg’s login nodes is:
If you have multiple mpirun commands in a single batch job submission script, you may find that one or more of these may fail after complaining about not being able to communicate with the orted daemon on other nodes. This appears to be something to do with multiple mpiruns being called quickly in succession, and connections not being pulled down and new connections established quickly enough.
Putting a sleep of e.g. 5s between mpirun commands seems to help here. i.e.
mpirun program1 sleep 5s mpirun program2