Running Simulations > High Performance Computing (HPC) Integration > Integration with Grid Engine (GE)           

Issue with MainWin Core Services for SGE

By default, SGE creates a temporary directory for each SGE batch job, and deletes this temporary directory and its contents when the job finishes. SGE sets the TMP and TMPDIR environment variables of the job environment to point to this temporary directory. ANSYS EM desktop software starts the MainWin Core Services on startup, if they are not already running. After the ANSYS EM desktop software finishes, the MainWin Core Services time out and automatically shut down. The MainWin Core Services use the TMP and/or TMPDIR directories to store temporary data. If this temporary data is removed before the services shut down, then the services do not shut down automatically. Normally, SGE will remove the temporary directory and its contents before the services time out. The result is that these extraneous service processes run forever. If this problem occurs, each Ansoft batch job starts an additional set of these services that never shut down. This can result in an excessive number of processes running on the host where the ANSYS EM desktop is started. The names of the service processes are:

• watchdog

• regss

• mwrpcss

Workaround for Issue with MainWin Core Services

One way to avoid this problem is to modify the environment in which the ANSYS EM desktop runs so that the TMP and TMPDIR environment variables do not point to the directory which will be immediately removed by SGE when the job finishes. This can be done by copying the value of the TMPDIR environment variable to the ANS_SGE_TMPDIR environment variable, and unsetting the TMPDIR and TMP environment variables. The services ignore the ANS_SGE_TMPDIR environment variable, but if this variable is set, then it will be used as the temporary directory for the rest of the ANSYS EM software.

Here is an example bash wrapper script that may be used to work around this issue. In this example, the product is hfss, but the same approach will work for any ANSYS EM product. In this example, the script is named sge_hfss and is in the AnsysEM software installation directory. When an Ansoft desktop job is submitted to the SGE scheduler, the script (sge_hfss, in this example) should be submitted instead of hfss. The script will modify the environment, as needed, then start hfss. When the analysis finishes, the script returns the exit status of hfss.

An alternative is to place the script in an arbitrary directory, and modify the script to include an absolute path to the product (hfss in this example).

Script contents:

#! /bin/bash

 

# This script will not correctly process arguments containing

# spaces or other characters special to the shell.

 

# Create hfss command line

# In this example, sge_hfss and hfss are in the same directory

# An alternative is to use an absolute path for the hfss command

cmd0=$0

cmd="${cmd0/%sge_hfss/hfss} $@"

 

# Fix environment variables

export ANS_SGE_TMPDIR=${TMPDIR}

unset TMPDIR

unset TMP

 

# Run the hfss command and return the exit status

${cmd}

exit $?

Related Topics

Integration with Sun Grid Engine (SGE)

Monitoring ANSYS EM SGE Batch Jobs

Ansoft Desktop -monitor Command Line Option for SGE

Example SGE qsub Command Lines

Recommended Practices for SGE Clusters