General
-The following error occurs immediately after the program runs:
unable to connect to forwarded X server: Network error: Connection refused |
The X server configration may be wrong. See the section 1 and 2 of the FAQ "X application doesn't work."
-The GUI program suddenly terminates
Please check the keep alive setting in the terminal you use. See the FAQ "Session suddenly disconnected while working on TSUBAME3."
-A job abruptly aborted
Although various reasons can be considered, please check the gollowing.
-Check of batch error file (usually script_name.e.$JOBID )
-Check program-specific log file
-Check the free space of the directory
reference: FAQ
About common errors in Linux
"Disk quta exceeded" error is output
The range of support by T3 Helpdesk about the program error such as segmentation fault
Maple
-The following error occurs immediately after the program runs:
|
It is due to the compatibility between the application and the X server. See the section 3 of the FAQ "X application doesn't work."
It has been confirmed that the error occurs with Xming but not occurs with mobaXterm.
ANSYS
-The GUI program freezes
It is due to the compatibility between the application and the X server. See the section 3 of the FAQ "X application doesn't work."
The trouble occurs with the X server that does not support GL, and it does not occur with the other supporting GL such as ASTEC-X.
In Ansys R18.2, the operation of GL version Xming (Xming-mesa) has been confirmed.
Fluent
-The following error occurs immediately after the program runs:
Reduce the number of used nodes / processes to be less than the license limit.
In the example below, we are using an HPC license of 94 tokens(f_node=3)
In case of 2 f_nodes, error will not occur because it is within limit.
Unable to spawn node: license not available. Hit return to exit. |
ex:Notification to apply the license restriction for ANSYS (Jan. 31)
ABAQUS
-The following error occurs immediately after the program runs:
|
It is the normal handling at the login node. The use of the solver license is prohibited at the login node.
ex:Notice of the restriction of using ABAQUS analysis on login node and temporary unavailable of it due to maintenance of the license server
Please run the job via the batch job scheduler.
See TSUBAME3.0 User's Guide for the batch job scheduling system.
-The following message is displayed while the program runs:
Analysis initiated from SIMULIA established products |
It is in waiting because of the license shortage.
Calculation starts as soon as sufficient licenses are secured.
Note that The TSUBAME points are consumed even in waiting.
-Abaqus / Explicit generates the following error at parallel execution
Abaqus Error: Abaqus/Explicit Packager exited with an error - Please see the |
As a workaround, please read the countermeasure module as follows
abaqus/2017 Execute the module purge command before executing if it is reading.
$ module load abaqus/2017_explicit |
COMSOL Multiphysics
-The following message is displayed while the program runs
It occurs with the X server that does not supoort GL. Please use the X server supporting GL or execute with software rendering mode.
$ comsol |
-The following message is displayed while the program runs
License error. Wait until the license is available and try again.
Please check the manual for checking the license.
|
Materials Studio
-The following message is displayed while the program runs
Please be sure to check the output file as multiple causes can be considered only with the error below.
The job has failed. Download any results generated so far? (Results files will be permanently removed from Server) |
ex: License error.
In the case of the example below it is a license error. Wait until the license is available and try again.
Laboratory etc. TSUBAME is executed by anything other than TSUBAME but it always occurs after the summer maintenance in 2018.
Reference:License restriction on ISV application usage
As a countermeasure, please use the batch job scheduler.
Please check the job scheduling system of TSUBAME3.0 User's Guide.
Output file (example of CASTEP)
Job started on host GSIC at Thu Aug 16 13:20:06 2018 +-------------------------------------------------+ | | | CCC AA SSS TTTTT EEEEE PPPP | | C A A S T E P P | | C AAAA SS T EEE PPPP | | C A A S T E P | | CCC A A SSS T EEEEE P | | | +-------------------------------------------------+ This version was compiled for x86_64-windows-msvc2013 on Dec 07 2016 Code version: 7217 Intel(R) Math Kernel Library Version 11.3.1 Fundamental constants values: CODATA 2010 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Licensing Error ! Error: Manual heartbeat setup for MS_castep license failed Failed to check out licenses Trace stack not available |
Output file (example of Dmol3)
=============================================================== Materials Studio DMol^3 version 2017 R2 compiled on Dec 7 2016 22:56:21 =============================================================== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DATE: Aug 16 13:20:06 2018 Job started on host GSIC This run uses 1 processors Licensing Error ! Error: Failed to checkout MS_dmol license Message: DMol3 job failed Error: DMol3 exiting Message: License checkin of MS_dmol successful |
ARM
ex: License error.
In the case of the example below it is a license error. Wait until the license is available and try again.
|