Reporting Errors

HOWTO make an error report

When reporting an error or problem encountered on HPC machines we kindly request that you:

# Tell us the machine you were working on
yes, you have one and only one account, so you were obviously on <younameit>; and yes, of course we know how to find out where your only account is located; but it is a (relatively) long and boring task for us, while it costs nothing at all to you
# Always attach the complete error message
we can do really little with generic reports of “MPI errors” or “memory allocation problems”
# Always tell us the job number
this is the most important piece of information
# Always attach the complete PBS/torque script
not just the resources, or just the launch command; if you work interactively, post the session history on the masternode (“history” command); if your job is qsub’ed by another script, please attach that script too
# Add optional information
information that you consider helpful for us to pinpoint (and possibly solve) your problem e.g.: nodes on which your job is/was running, compiler and optimization flags used for compilation, libraries linked, ...
# Use e-mail, not phone
‘’‘ALWAYS’‘’ send your reports to elcid-support(AT), error codes are quickly corrupted by AWGN on phone lines (and silently dropped by content filters on private accounts)

Please note that it is really difficult for us to diagnose problems if we do not know where and when they happened, so please follow this micro-HOWTO. Error reports not complying to these guidelines will be dropped without further action.

Thank you for your understanding.