You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

This is a page collecting answers to requests arrived to the HPC Helpdesk.

Please check here before sending a specific request.

In this page:

General:

  • How I can add a collaborator to my project?

Project group leaders can also manage their user's membership on their UserDB page. 

  • I still didn’t receive the username and the password for the system access?

You have to do the complete registration on the UserDB page and to be associated with a project (PI has to add you). Once you have inserted all the necessary information and you are associated with a project a new access button will appear, just click on it and you will receive in two mails the username and the password.

  • Backup Policy 

  • Information about my account (end data, total end monthly amount of hours, how much I have already consumed/usage?)

  • Which filesystems do I have available? Which usage is intended?

  • How can I check how much free disk have I available? 

Come stiamo messi con cindata?

 

Connection/login

  • I haven't been login for a while, recently I found I couldn't login it and return me a message: access denied.

  • How to change my password?

Executions/scheduler:

  • I was copying data/compiling/executing something in the login and the process was killed. Why?

  • My job has been waiting for a long time. How can I see when will it be executed?

  • My job exits with some error just after starting. What is wrong?

  • How can I see if there are any problems with my job? / How can I check the status of my jobs? 

  • Which queue should I use?

  • Troubles running a dynamically linked executable

In order to use the available libraries dynamically, you have to add the library directory to the path list of the environment variable $LD_LIBRARY_PATH before the execution of your job starts. E.g. for /user/lib64 you would export it as below:

  • export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib64 (bash)

  • set LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/usr/lib64    (csh)

The compiler wrappers link statically by default unless you use the option -dynamic or set ... 

  • Error invalid account when submitting a job: Invalid account or account/partition combination specified.

  • How can I list all my jobs currently in the queue?

  • Can I modify slurm settings of a waiting job?

  • How can I place and release a job from hold state?

  • What is the meaning of the status of my job?

Several job states are displayed by the slurm “squeue” command:

  • CA (CANCELLED): the job was explicitly cancelled by the user or system administrator. The job may or may not have been initiated.

  • CD (COMPLETED): the job has terminated all processes on all nodes.

  • CF (CONFIGURING): the job has been allocated resources, but are waiting for them to become ready for use (e.g.booting).

  • CG (COMPLETING): the job is in the process of completing. Some processes on some nodes may still be active.

  • F (FAILED): the job terminated with non-zero exit code or other failure condition.

  • NF (NODE_FAIL): the job terminated due to the failure of one or more allocated nodes.

  • PD (PENDING): the job is awaiting resource allocation.

  • PR (PREEMPTED): the job terminated due to preemption.

  • R (RUNNING): the job currently has an allocation.

  • S (SUSPENDED): the job has an allocation, but the execution has been suspended.

  • TO (TIMEOUT): the job terminated upon reaching its time limit.

Performance:

  • I have found performance problems, what should I do?

First, you should find a method to reproduce the problem and confirm after some tests that it is reproducible. After that, you should provide all relevant information to the Support Team by e-mail together with instructions on how to reproduce your tests. Support Team will investigate the issue and contact you as soon as possible.

  • No labels