LUCI4HPC error codes

In case of an error, LUCI4HPC will output an error message containing the appropriate error type and matching error code.

Error type "M"

This error type indicates an error in the shared memory management system.
Error codes are: 101 102 103 104 201 202 203 204 205 206 301.
Errors of this type can occur during the startup of LUCI4HPC.

Possible solution:
Run

sudo ipcs -m
sudo ipcs -s
to list the shared memory segments and semaphores still present on your system.

Use
sudo ipcrm -m 
sudo ipcrm -s 
to remove them.
Alternatively you can reboot the machine, which will clear all shared memory segments and semaphores.

Error type "U"

This error type indicates an error in the mutex system.
Possible solution:
Restart the corresponding LUCI4HPC service:

- 221 : lft service
- 222 : lcache service
- 223 : lcp service
- 224 : lcfg service
- 225 : lgrid service
- 226 : the client on a node

Error type "T"

This error type indicates an error during the thread creation.
Possible solution:
Restart the corresponding LUCI4HPC service:

- 600 : LUCI4HPC
- 601 : lft service
- 602 : lcp service

Error type "D" and "K"

This error type indicates an exception in the standard c++ library. The corresponding error code is 911.

Possible solution:
- Check your c++ standard library installation
- Check whether there is enough free memory
- Check whether there could be faulty memory

Error type "L"

This error type indicates an error during the log file creation.
Error codes are: 901 (lnames), 902 (lhbeat), 903 (lft), 904 (lcache), 905 (lexec), 906 (lcp), 907 (lip), 908 (lcfg) and 909 (lgrid).

Possible solution:
- Check whether /var/log/luci4hpc exists and has the correct permissions

Error type "C"

This error type indicates an error during the command socket creation.
Error codes are: 801, 802, 803 and 899.

Possible solution:
- Check whether

/var/opt/luci4hpc/cmd.socket
exists and remove it before restarting LUCI4HPC

Error type "E"

This error type indicates an error during the exec service socket creation.
Error codes are: 804, 805, 806 and 899.

Possible solution:

- Check whether

/var/opt/luci4hpc/exec.socket
exists and remove it before restarting LUCI4HPC

Error type "S"

This error type indicates an error during a network socket creation.
Error codes are: 701, 702 and 703.

Possible solution:
- Check whether the failing port is already taken by another program
- Reboot your machine to clear all pending sockets

Error type "F"

This error type indicates a file access error.
The matching error code is: 501.

Possible solution:
- Check whether the file exists and is accessible.

Error type "P"

This error type indicates a parsing error.
Error codes are: 351 and 352,

Possible solution:
- Check the LUCI4HPC configuration files for syntax errors

Error type "R"

This error type indicates that the program does not have superuser privileges.
The corresponding error code is 99.

Possible solution:
LUCI4HPC needs to be executed as root (use sudo).

Error type "I"

This error type indicates an error with the license.

Possible solution:
- 70 : The license has expired, go to the members area on the LUCI4HPC website to request a new one
- 80 : The license is not valid, go to the members area on the LUCI4HPC website to download a license file
- 87 : No license file present, go to the members area on the LUCI4HPC website to download a license file
- 88 and 89 : Check the OpenSSL installation

Error type "G"

This error type indicates an error with the LUCI4HPC scheduler.
Error codes are: 401 and 402.

Possible solution:
- Check whether the LUCI4HPC scheduler configuration files exist and are accessible
- Check the LUCI4HPC scheduler configuration files for syntax errors

Error type "X"

This error type indicates an error with the LUCI4HPC process control.
Error codes are: 21 and 22.

Possible solution:
- Restart LUCI4HPC
- Reboot your machine

Error type "O"

This error type indicates an error with the LUCI4HPC client program.
The corresponding error code is 31.

Possible solution:
- Restart the LUCI4HPC client program
- Reboot the node

You are advised to visit our support forum for further help.

Back

Current version: 1.0beta1
 

Imprint