installation note hexpress 25 4 unix-acrov5

N U M E R I C A L M E C H A N I C S A P P L I C A T I O N S

Installation Notefor LINUX and UNIX platforms

Hexpress™ v2.5

Unstructured Grid Generator

- December 2007 -

N U M E R I C A L M E C H A N I C S A P P L I C A T I O N S

Installation Notefor LINUX and UNIX platforms

Hexpress™ v2.5

Documentation v2.5-a

NUMECA International

5, Avenue Franklin Roosevelt

1050 Brussels

Belgium

Tel: +32 2 647.83.11

Fax: +32 2 647.93.98

Web: http://www.numeca.com

Contents

INSTALLATION NOTE iii

CHAPTER 1: Introduction 1-1

CHAPTER 2: System Requirements 2-1

2-1 Overview 2-1

2-2 Supported Platforms & Operating Systems 2-1

2-3 Hardware Requirements 2-2

2-4 Memory & Disk Space Requirements 2-3

2-5 Graphics Requirements 2-3

CHAPTER 3: Installation 3-1

3-1 Introduction 3-1

3-2 Install Hexpress™ 2.5-4: no Hexpress™ Installed 3-1

3-3 Install Hexpress™ 2.5-4: Multi-Version Environment 3-2

CHAPTER 4: License Management 4-1


4-2 Installation of Node-locked License 4-1

4-3 Installation of Floating License 4-2Floating License on UNIX/LINUX License Server 4-2Floating License on UNIX or LINUX Client 4-3

4-4 Update of License File 4-3Update of Node-locked License 4-4Update of Floating License 4-4

4-5 Dedicated License for CATPart Files Import 4-4How to Get Dedicated License ? 4-4How to Install Dedicated License ? 4-4How to Update License ? 4-5

CHAPTER 5: User Configuration 5-1

5-1 Overview 5-1

5-2 User Configuration 5-1

5-3 Software Launch 5-1

CHAPTER 6: Uninstallation 6-1

6-1 Overview 6-1

6-2 Uninstall Hexpress™ 2.5 (Mono-Version Environment) 6-1

6-3 Uninstall Hexpress™ Partly (Multi-Version Environment) 6-2

6-4 Uninstall Hexpress™ Fully (Multi-Version Environment) 6-2

6-5 Uninstall License Service 6-2

iv INSTALLATION NOTE

Contents

CHAPTER 7: Troubleshooting 7-1


7-2 Hexpress™ Not Starting 7-1

7-3 Graphical Problems & System Crashes 7-2

7-4 Hexpress™ Screen Flashes 7-3

7-5 Hexpress™ Drivers Not Detected 7-3

INSTALLATION NOTE 1-1

CHAPTER 1: Introduction

This note details the installation procedure of the unstructured grid generator Hexpress™ v2.5 developedby NUMECA.

The package is delivered with full options, except for the direct importation of CATPart files (gener-ated by CATIA v5) which requires a dedicated external license from TTF NUMECA partner. Moredetails about this dedicated license can be found in section 4-5.

This installation note consists of six parts respectively dedicated to:

• general information for all platforms, including system requirements,

• the installation procedure itself,

• the license installation,

• the user configuration and launch procedure,

• the uninstallation procedure,

• possible troubleshooting.

The user is strongly advised to consult the system requirements described in the firstpart of this note prior to start any installation of the Hexpress™ v2.5 package. Troublesmay indeed appear during the installation and configuration phases in case the listedhardware and software requirements would not be fully satisfied.

The installation procedure and the license installation should be carefully followed to ensure a fast andsmooth installation. In case problems occur during the installation or configuration phases, the trouble-shooting section should give a step by step analysis to detect and help solving the cause of the problem.Please do notice that the documentation attached to Hexpress™ v2.5 is NOT installed during the installa-tion procedure.

Please contact NUMECA support team at +32-2-647.83.11 or send an e-mail to [email protected] formore information or in case of persistent problems. To allow NUMECA support to help you out within theshortest delays, please provide a detailed description of the observed behaviour and performed analysisusing the troubleshooting section of this installation note.

Introduction

1-2 INSTALLATION NOTE


CHAPTER 2: System Requirements

2-1 OverviewIn this chapter, system requirements for a proper installation and use of Hexpress™ v2.5 are listed. In orderto guarantee a smooth and successful installation, the specifications of your system must match with the listof supported platforms and operating systems as described here below. The following system requirementsand limitations are listed in the next sections:

• supported platforms and operating systems,

• hardware requirements,

• memory and disk space requirements,

• graphics requirements.

2-2 Supported Platforms & Operating SystemsA detailed list of supported platforms and operating systems is proposed in the tables here below:

On LINUX:

Processor Formally tested on Also known to run ona

a. known from partners and/or customers. No official support offered on these combinations.

32 bits / 64 bits

x86b

b. 32 bits processors that are compatible with Intel 8086 set of instructions. Includes Pentium 4, Xeon, Pentium D, AMD Sem-pron, Athlon and Celeron.

Red Hat 9.0 - 32 bits

x86b Enterprise 2.x, 3.x - 32 bits

x86b - SuSe 9.x 32 bits

x86b - Mandrake 9 32 bits

System Requirements Hardware Requirements


Please contact NUMECA support team at [email protected] if your platform of preference is not listedin one of the tables above. Hexpress™ 2.5-4 does however explicitly not run on the following configura-tions:

• x86_64 processors running LINUX SuSe 10.3,

• HP Itanium 2 running HP-UX 11,

• IBM PowerPC running LINUX.

2-3 Hardware RequirementsNext to the standard hardware (monitor, keyboard and mouse), some specific recommendations apply inthe use of NUMECA software:

• a DVD-ROM drive is required for installation purposes.

• a 3-buttons mouse is strongly recommended to use all capabilities in Hexpress™.

• the monitor should support 24-bit colour graphics and have a 1280x1024 pixel resolution for suffi-ciently clear visualization of the interface and the graphics.

• an ethernet card is mandatory on LINUX when a node-locked license is used.

2-4 Memory & Disk Space RequirementsThe Read Only Memory (RAM) required to run Hexpress™ depends upon several factors, in particularincluding the number of grid points inserted in the grid, the introduction of full non matching connections(FNMB) and the number of viscous layers inserted in the final mesh.

The use of minimum 1 Gb RAM is mandatory, but the installation of 2 Gb is recommended. As a generalguideline, about 800 Mb RAM are generally required to run a one million nodes project

The suggested swap space should be equivalent to at least 3 times the RAM installed.

Processor Formally tested on Also known to run ona

a. known from partners and/or customers. No official support offered on these combinations.

32 bits / 64 bits

x86_64b

b. 64 bits processors that are compatible with Intel 8086 set of instructions. Includes Opteron, Athlon 64, Athlon 64 X2, Athlon 64 FX, Sem-pron, Turion, Xeon EM64T, Core2 Duo and Core2 Quad.

Enterprise 4.x - 64 bits

x86_64b SuSe 9.x - 64 bits

x86_64b SuSe 10.1, 10.2 - 64 bits

x86_64b - Enterprise 3.x 64 bits

IA-64c

c. 64 bits architecture proposed by Intel, that is not compatible with Intel 8086 set of instructions. Includes Itanium2.

Enterprise 2.x, 3.x - 64 bits

Graphics Requirements System Requirements


Similarly, a minimum disk space is required on the hard disk to allow the storage of the mesh files (includ-ing cache files). As a general guideline, about 900 Mb is required to store the mesh and cache directory fora one million nodes project.

2-5 Graphics RequirementsThe supported graphics cards are (according to HOOPS manual):

• NVIDIA GeForce(2)(256).

• NVIDIA GeForce(4)(256).

• NVIDIA TNT 2.

• 3DLabs Wildcat III.

Hexpress™ makes use of the advantages of the available Graphics Card. Some trouble may however comeup with the default driver OPENGL since it may not be supported by the user host computer and machinedisplay.

In order to set the system compatible with a more portable driver, typically X11 driver is used under UNIX(or LINUX) instead. Note however that the proposed drivers are usually less efficient in terms of graphicalspeed than the default driver.

To change the driver used by Hexpress™:

1. Open the file ~\.numeca\.drivers

2. Type "host_name display_name possible_drivers chosen_driver" i.e. gauss.numeca.be gauss OPENGL:X11 X11

Furthermore, the driver can be manually specified through the following commands:

in csh, tcsh or bash shell:setenv NI_DRIVER X11

in korn shell:NI_DRIVER=X11export NI_DRIVER

The selection will take effect at the next session.

System Requirements Graphics Requirements



CHAPTER 3: Installation

3-1 IntroductionTo install Hexpress™ 2.5-4, it is important to check first whether previous versions of Hexpress™ wereinstalled on the machine:

• Providing no NUMECA package is installed on the machine, Hexpress™ 2.5-4 installation may be per-formed as described in section 3-2.

• Hexpress™ 2.5-4 can possibly be installed besides Hexpress™ 2.3. If so, all versions can be accessedthrough a unique multi-version environment. Please refer to section 3-3 for more details on the installationof Hexpress™ in a multi-version environment.

The installation procedure detects automatically the operating system on which the user islogged in. To install Hexpress™ 2.5-4 on other operating systems, the user must select thecorresponding tar file and log onto a workstation with such OS, otherwise the procedurewill be automatically stopped. Please refer to section 3-2 for more details.

3-2 Install Hexpress™ 2.5-4: no Hexpress™ InstalledProviding no Hexpress™ package is installed on the machine, Hexpress™ 2.5-4 installation may be performedon a UNIX or LINUX platform as follows:

1. Log onto the workstation corresponding to the selected OS. Although the installation procedure does notrequest absolutely the "root" permission, it is strongly recommended to check the permission of the disk anddirectory the user will select for the software installation.

2. The installation of Hexpress™ 2.5-4 package under LINUX requires about 350 Mb. Please check that thenecessary disk space is available prior to start the installation process.

3. The tar files included on the DVD-ROM (or accessible from www.numeca.be) are namedinstall_hexpress_25_4_OSname.tar (OSname is corresponding to the OS selected); they are located in thecorresponding "/platform/OS" sub-directories.

Installation Install Hexpress™ 2.5-4: Multi-Version Environment


4. Copy the tar file install_hexpress_25_4_Osname.tar into a temporary directory. Check that the file can beaccessed with full permission and extract it by typing the command line: tar -xvfinstall_hexpress_25_4_OSname.tar.

Do NOT extract the tar file in the target directoryNUMECA_INSTALLATION_DIRECTORY in which hexpress25_4 will be installed.

5. Go to the temporary directory containing the files extracted from the tar archive and type the command ./install_hexa <ENTER>.

6. The user will be asked to give the name of the installation directory, named'NUMECA_INSTALLATION_DIRECTORY' hereafter. A directory name that does not already exist must beused; otherwise the procedure will be automatically stopped.

7. At the end of the installation process, the user will be asked whether a previous version should or not belinked. Since no previous NUMECA package is installed on the machine (mono-version environment), theanswer is no.

8. Finally, the so-called 'HostName' and 'HostID' information required to generate a license key will be shown.This information should be sent at [email protected]. The HostName and HostID can also be obtained bytyping the commands NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/machine_type/install/lmutil lmhostid-hostname <ENTER> and NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/machine_type/install/lmutillmhostid <ENTER>, with machine_type corresponding to the OS selected.

9. In case NUMECA software should be installed on another OS, the previous seven steps must be repeated withthe new corresponding archive file corresponding to the other OS. In step 6 the sameNUMECA_INSTALLATION_DIRECTORY should be entered during the installation.

10. When receiving the license file from NUMECA, perform the license installation as described in the next chap-ter.

11. Perform the user configuration as described in Chapter 5.

12. Launch the software as described in Chapter 5.

3-3 Install Hexpress™ 2.5-4: Multi-Version EnvironmentHexpress™ 2.5-4 environment can possibly be installed besides Hexpress™ 2.3.

Providing Hexpress™ 2.3 package is adequately installed on the machine, Hexpress™ 2.5-4 can be straightfor-wardly installed in a multi-version environment on UNIX or LINUX as follows:

1. Log onto the workstation corresponding to the selected OS. Although the installation procedure does notrequest absolutely the "root" permission, it is strongly recommended to check the permission of the disk anddirectory the user will select for the software installation.

2. The installation of Hexpress™ 2.5-4 package under LINUX requires around 350 Mb. Please check that thenecessary disk space is available prior to start the installation process.

3. The tar files included on the DVD-ROM (or accessible from www.numeca.be) are namedinstall_hxepress_25_4_OSname.tar (OSname is corresponding to the OS selected); they are located in thecorresponding platform/OS sub-directories.

4. Copy the tar file install_hexpress_25_4_Osname.tar into a temporary directory. Check that the file can beaccessed with full permission and extract it by typing the command line tar -xvfinstall_hexpress_25_4_OSname.tar.

Do NOT extract the tar file in the target directoryNUMECA_INSTALLATION_DIRECTORY in which hexpress25_4 will be installed.

Install Hexpress™ 2.5-4: Multi-Version Environment Installation


5. Go to the temporary directory containing the files extracted from the tar archive and type thecommand ./install_hexa <ENTER>

6. The user will be asked to give the name of the installation directoryNUMECA_INSTALLATION_DIRECTORY in which Hexpress™ 2.3 has been previouslyinstalled, otherwise the multi-version installation will not be set-up adequately.

7. At the end of the installation process, the user will be asked whether previous versions should ornot be linked. A positive answer (’yes’) is required to enable concurrent launch Hexpress™ 2.3or Hexpress™ 2.5-4, in case (and only in case) these versions have been partially or com-pletely installed in separate NUMECA_INSTALLATION_DIRECTORY (e.g.: /usr/numeca23_1/ and /usr/numeca25_4). If so, links must be created towards Hexpress™ 2.5-4 andfull pathname of Hexpress™ 2.3 (e.g.: /usr/numeca23_1/hexpress23_1) should be specifiedupon request.

8. Finally, the so-called 'HostName' and 'HostID' information required to generate a license keywill be shown. This information can be ignored.

License file delivered with Hexpress™ 2.3 cannot be used for Hexpress™ 2.5,since security levels have been upgraded. Please send the Hexpress™ 2.3 licensefile at [email protected] for an upgrade of the license file.

9. In case NUMECA software should be installed on another OS, the previous six steps must berepeated with the new corresponding archive file corresponding to the other OS. At this stage,there is no need to create new links since they will already exist (if installed in the same installa-tion direction specified at step 6). When receiving the license file, perform the license installa-tion as described in the next chapter.

10. Perform the user configuration as described in Chapter 5.

11. Launch the software as described in Chapter 5.

Installation Install Hexpress™ 2.5-4: Multi-Version Environment



CHAPTER 4: License Management

4-1 IntroductionBefore using NUMECA software, a valid FlexLM license key is required. There are two different types oflicense:

• FlexLM node-locked license key. A node-locked license is dedicated to a given computer and allowsaccess to NUMECA software on this computer only. In section 4-2 it is described how to obtain andinstall such a license key.

• FlexLM floating license key. With a floating license each software component is managed by an inde-pendent maximum number of concurrent accesses (number of processes). Floating licenses are managedby a license server which checks if process access is free. The license can be accessed on the same com-puter but also on other computers (clients) which are connected through a network to the license server.To obtain and install a floating license on a license server see section 4-3.1. To configure the clients forthe use of the floating license see section 4-3.2.

Standard license keys for Hexpress™ 2.5-4 are based on the version 9.2 of the FlexLM tools. Type the com-mand .\lmutil lmver numeca into /NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install to know the FlexLM tools version used on the operating system of the license server.

License keys delivered with Hexpress™ 2.3 cannot be used with Hexpress™ 2.5, sincesecurity levels have been upgraded. Please send the Hexpress™ 2.3 license file [email protected] for an upgrade of the license file.

4-2 Installation of Node-locked LicenseNode-locked licenses are dedicated to a given computer. They allow access to the software componentsonly from the dedicated computer. At the end of installation on the dedicated computer, the license informa-tion (HostName and HostID of this machine) must be sent at [email protected]. Once the license key isgenerated, it must:

1. Be renamed as license.dat

2. Be copied into NUMECA_INSTALLATION_DIRECTORY/COMMON

3. Have read-execute access privileges (execute chmod 755 license.dat).

License Management Installation of Floating License


The license.dat file must be readable by every user.

4-3 Installation of Floating LicenseWith a floating license, each software component is managed by an independent maximum number of con-current accesses (number of processes). Floating licenses are managed by a license server. The licenseserver runs a license daemon that checks if process access is free. If so, when launching a software compo-nent, license access is given to the user process or access is denied otherwise.

The license can be accessed on the same computer but also on any other computer (client), with UNIX,LINUX or Windows, connected to the license server. The license server can be a UNIX, LINUX or Win-dows machine. To install a floating license:

• on a UNIX or LINUX license server: see section 4-3.1.

• on a UNIX or LINUX client: see section 4-3.2.

If a NUMECA license service is already active consult section 4-4 to replace the license file.

4-3.1 Floating License on UNIX/LINUX License Server

NUMECA software must be installed on the license server (see Chapter 3 for software installation). At theend of the installation, the license information (the HostName and HostID of this computer) must be sentat [email protected].

4-3.1.1 Configuration of License Service

To install the license service take the following steps:

1. Rename the license file as license.dat

2. Copy the license.dat file in the directory NUMECA_INSTALLATION_DIRECTORY/COMMON

3. Check that the license file has the read-execute access privileges (execute chmod 755 license.dat)

The license.dat file must be readable by every user.

4-3.1.2 Starting License Service

Before using NUMECA software, the license daemon should be started on the license server. This can bedone manually or automatically.

a) Manual Start of License Service

To start the license daemon manually, do the following operations:

1. Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/

2. Execute the command:

./lmgrd -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

In these lines, ’NUMECA_INSTALLATION_DIRECTORY’ should be replaced by the absolute directorypath where you have installed NUMECA software, while ’OSname’ should be replaced by LINUX.

The manual start operations must be repeated each time the server machine isrebooted.

Update of License File License Management


b) Automatic Start of License Service

The license daemon can be automatically started during the workstation boot process. To do so:

1. Login as "root"

2. Go to the /etc directory

3. Edit the inittab file

4. Add the following line at the end:

lmgr:35:wait:/

NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/lmgrd -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

In this line, ’NUMECA_INSTALLATION_DIRECTORY’ should be replaced by the absolute directorypath where you have installed NUMECA software, while ’OSname’ should be replaced by LINUX.

4-3.1.3 Verification of License Service Status

To verify that the license server is correctly running do the following:

1. Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/

2. Execute the command:./lmutil lmstat -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

If the license server is up this will be shown in the shell with the words: "license server UP (MASTER)v9.2". The vendor daemon numeca needs to be up as well as indicated with the words: "Vendor daemonstatus (on license_server_machine_name): numeca: UP v9.2. If the license server or vendor daemon is notup see Chapter 5.

To display the active users of a given feature, use the following command:

./lmutil lmstat -a -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

4-3.2 Floating License on UNIX or LINUX Client

When a floating license is installed on a UNIX, LINUX or Windows license server, this license may beused by other computers with a network connection to the license server. In this section, it is assumed thatthe license server is running. On each UNIX or LINUX client, the user should install NUMECA softwareand copy the license key file license.dat of the license server in the directoryNUMECA_INSTALLATION_DIRECTORY/COMMON.

Users willing to launch NUMECA software on a client should perform a user configuration on thismachine before first use as described in Chapter 5.

4-4 Update of License FileWhen a license file is expired, contact NUMECA at [email protected] to obtain a updated license file.Rename this license file as license.dat and follow the instructions in the sections below depending on thelicense type.

License Management Dedicated License for CATPart Files Import


4-4.1 Update of Node-locked License

Rename the updated license as license.dat and copy it in the directoryNUMECA_INSTALLATION_DIRECTORY/COMMON, thus overwriting the old license.dat file. Ensurethat read-execute access permission are adequately set on the new license file.

4-4.2 Update of Floating License

To replace a floating license on the license server, do the following operations on the server machine:

1. Copy the new file license.dat in the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/

It is strongly suggested to make a backup of the old license file, for safety, by renamingit to license.old.

2. Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install/where ’OSname’ is the OS corresponding to the server machine (LINUX).

3. Execute the command:./lmutil lmreread -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

To replace a floating license on the clients using the license server, simply replace the license.dat in thedirectory NUMECA_INSTALLATION_DIRECTORY/COMMON, for each NUMECA software.

4-5 Dedicated License for CATPart Files ImportHexpress™ includes a dedicated option enabling a direct importation of CATPart files, as generated byCATIA v5.

This option is however subjected to a separate license. It is generated by TTF NUMECA partner and isavailable on SGI, HP11, IBM AIX 4.3, LINUX and WINDOWS platforms (all platforms running 32-bitsarchitecture exclusively). Both node-locked and floating dedicated license file for importation of CATPartfiles can be obtained, under the constraint that licenses generated on WINDOWS are in the form of a hard-key.

4-5.1 How to Get Dedicated License ?

The dedicated license file can be requested to NUMECA (generic address [email protected]). The fol-lowing information must accompany the demand:

• the platform of preference for installation of the dedicated license,

• the type of license (node-locked, floating) with related HostID.

4-5.2 How to Install Dedicated License ?

The dedicated license file, named as "license_import.dat", must be located inNUMECA_INSTALLATION_DIRECTORY/COMMON.

In case a floating license has been requested, it is necessary to perform the additional operations:

• create a file named "ttf_server_information.dat". The file must include the two following lines and mustbe stored in NUMECA_INSTALLATION_DIRECTORY/COMMON.

SERVER server_name where server_name is the name of the serverPORT 10500

Dedicated License for CATPart Files Import License Management


• start the license server. This can be achieved through the execution of the command line./ttfstartsrv NUMECA_INSTALLATION_DIRECTORY/COMMON/license_import.dat 10500 -logfile ./LOG_FILE from the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/hexpress25_4/OSname/install/ttf

4-5.3 How to Update License ?

• stop the license server. This can be achieved through the execution of the command line./ttfstopsrv 10500 from the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/hexpress25_4/OSname/install/ttf

where 10500 is actually the port number (should be consistent with the port numberspecified when launching the server.

• replace the license file in NUMECA_INSTALLATION_DIRECTORY/COMMON (UNIX) orNUMECA_INSTALLATION_DIRECTORY/hexpress25_4/flexlm/ (Windows).

• start the license server. This can be achieved through the execution of the command line./ttfstartsrv NUMECA_INSTALLATION_DIRECTORY/COMMON/license_import.dat 10500 -logfile ./LOG_FILE from the directory NUMECA_INSTALLATION_DIRECTORY/COMMON/hexpress25_4/OSname/install/ttf

License Management Dedicated License for CATPart Files Import



CHAPTER 5: User Configuration

5-1 OverviewAt the end of the installation, each user willing to use NUMECA software must initially configure his/herworking environment by running an initialisation script. In the following:

• Section 5.2 describes how to configure the user environment.

• Section 5.3 describes how to launch the software.

5-2 User ConfigurationEach user is then allowed to configure his/her working environment as follows:

1. Login as user.

2. Go to the directory NUMECA_INSTALLATION_DIRECTORY/COMMON, and issue the command./configure. This operation will add a couple of lines in the user’s .cshrc or .profile file (located inuser’s home directory) and add the NUMECA software in user’s default path.

3. Log out and login again to apply the information in the .cshrc or .profile file.

5-3 Software LaunchHexpress™ 2.5-4 can be started through the commands hexpress25_4 in the shell window.

In a multi-version environment, access to Hexpress™ 2.3-1 is allowed through the commandhexpress23_1. Do however notice that valid links towards Hexpress™ 2.5-4 must apply during the instal-lation process.

User Configuration Software Launch


It is important to outline that no output is displayed by default in Hexpress™ 2.5-4 shells, in order to avoidunnecessary cluttering. The output is better redirected to a log file, located in the directory ~/.numeca/tmp/and named as startup_logfile_hexpress.

However, outputs can still be forced for display in the shells. To this end, the -print command shouldappend to the command line as for example hexpress25_4 -print. This will give additional information dur-ing software launch, especially during the initial configuration of the software.

In case of troubles when starting the software, please send these files (if present) to NUMECA support([email protected]) with a short description of the problem.


CHAPTER 6: Uninstallation

6-1 OverviewThis chapter details the steps required to properly remove an installation of NUMECA software. Depend-ing upon the configuration, several possibilities are offered:

• Providing Hexpress™ 2.5-4 is installed in a mono-version environment (only Hexpress™ 2.5-4 isinstalled), the uninstallation process can be performed as described in section 6-2.

• Providing Hexpress™ 2.5-4 is installed in a multi-version environment, a partial or complete uninstal-lation can be performed:

— to remove part of Hexpress™ environment, see section 6-3.

— to remove the complete Hexpress™ environment, see section 6-4.

No further action is requested to uninstall a node-locked license. In case of floating license, the licenseservice may be stopped if NUMECA software is not used on any machine connected to the license server(see section 6-5).

6-2 Uninstall Hexpress™ 2.5 (Mono-Version Environment)Proceed as follows to remove Hexpress™ 2.5-4 in a mono-version environment under UNIX or LINUX:

1. Verify that there are no running tasks on the machine.

� In case of floating license, the license service should be stopped before uninstalling NUMECAsoftware. More details in section 6-5.

2. Remove the lines from "#begin NUMECA configuration" to "#end NUMECA configuration" from theuser’s .cshrc or .profile file.

3. Remove the directory NUMECA_INSTALLATION_DIRECTORY and its contents.

Uninstallation Uninstall Hexpress™ Partly (Multi-Version Environment)


6-3 Uninstall Hexpress™ Partly (Multi-Version Environment)Proceed as follows to remove Hexpress™ 2.5-4 or Hexpress™ 2.3 (but not both) in a multi-version envi-ronment under UNIX or LINUX:



2. Check that an active and valid license file is present for Hexpress™ 2.5-4 or Hexpress™ 2.3 (dependingupon the version the user wants to keep installed). The license file must be installed in the directoryNUMECA_INSTALLATION_DIRECTORY/COMMON/.

3. Remove the directory NUMECA_INSTALLATION_DIRECTORY/hexpress# (where # refers to theversion to uninstall, either 23_1 or 25_4) and all of its contents.

6-4 Uninstall Hexpress™ Fully (Multi-Version Environment)Proceed as follows to remove Hexpress™ 2.5-4 and Hexpress™ 2.3 in a multi-version environment underUNIX or LINUX:



2. Remove the lines from "#begin NUMECA configuration" to "#end NUMECA configuration" from theuser’s .cshrc or .profile file.

3. Remove the directory NUMECA_INSTALLATION_DIRECTORY and all of its contents.

6-5 Uninstall License ServiceNo action is requested to uninstall a node-locked license.

In case of floating license, the license service should be stopped before uninstalling NUMECA software. Todo so, the following operations must be performed:

1. Go to the directory NUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install

2. Execute the command: ./lmutil lmdown -c NUMECA_INSTALLATION_DIRECTORY/COMMON/license.dat

Instructions related to NUMECA license service must be removed providing themachine has been configured to start automatically the license service at start up. Theseinstructions can be accessed in /etc/initab file.


CHAPTER 7: Troubleshooting

7-1 IntroductionIn most cases, a straightforward and careful execution of the instructions detailed in the previous chaptersenables the user to start Hexpress™ 2.5-4 smoothly. In case of problems, this chapter aims at providingguidelines on how to detect and solve possible troubleshootings. If the problems still persist, please con-tact and provide NUMECA support team with the following information:

• the license key file license.dat.

• the hostname and hostid. These information can be obtained by executing the commands lmutillmhostid -hostname <Enter> and lmutil lmhostid <Enter> in theNUMECA_INSTALLATION_DIRECTORY/hexpress25_4/OSname/install directory, where"OSname" refers to the operating system selected.

• the Hexpress™ version for which installation is causing problems.

• a description of the configuration (in terms of name, platform and OS for each machine on whichNUMECA software is installed).

• the .log file generated during the installation and located in the /tmp directory on the machine fromwhere the script ./install_hexa has been launched (as described in section 3-2, step 5).

• the "startup_logfile_*" files located in ~\.numeca\tmp

7-2 Hexpress™ Not StartingIn case Hexpress™ does not start, use the -print argument in the command line as: hexpress25_4 -print.

This argument will output information in the shell (including the location of the license file) which maybe helpful to understand the problem. With this information at hand, check the following items:

• Is the license file valid and active to start Hexpress™ ?

• Check if the license key, named as license.dat, is adequately copied into theNUMECA_INSTALLATION_DIRECTORY/COMMON directory

Troubleshooting Graphical Problems & System Crashes


• In case of floating licenses, check if the license server is up. On the license server, two active daemonsshould be present. This can be seen using the commands ps -ealf | grep lmgrd and ps -ealf | grepnumeca. If not, follow the instructions for license installation.

• In case of floating licenses, some license check problems may occur if the host computer cannot findthe server IP-address corresponding to the hostname information included in the first line of thelicense key. To solve this problem, replace the hostname by the IP-address of the license server. Thisoperation does not invalidate the license key.

• Check if the license key file is well readable by every user.

• Did the user configure his/her working environment? Before using NUMECA software, each usermust configure his/her working environment using the command ./configure within theNUMECA_INSTALLATION_DIRECTORY/COMMON directory; then log out and log in.

• Is the graphics driver appropriate for the display ? Try to activate the X11 driver as follows:

in csh, tcsh or bash shell:setenv NI_DRIVER X11

in korn shell:NI_DRIVER=X11export NI_DRIVER

If this solves the problem, it means that OPENGL driver is at the source of the problem. If so, make thechange to X11 permanent by editing the file ~/.numeca/.drivers and specifying the driver in thechosen_driver colon (last colon).

• Check if the TCP/IP protocol is installed on the machine. The protocol is mandatory to ensure the cor-rect function of the floating licenses.

• Are the NUMECA software components visible from the machine? If not, install them.

• Is the OS adequate? If not, copy the correct tar file and start the installation again.

• Are Unix permission sufficient for the user to access NUMECA software installed? Ask for the sys-tem administrator.

Please send the file ~/.numeca/tmp/startup_logfile_hexpress to NUMECA support team if problems stillpersist.

7-3 Graphical Problems & System CrashesHexpress™ makes use of the advantages of Graphics Card available. Some trouble may however comeup with the default driver OPENGL since it may not be supported by the user host computer and machinedisplay.

In order to set the system compatible with a more portable driver, refer to the following instructions. Notehowever that the proposed drivers are usually less efficient in terms of graphical speed than the defaultdriver. The driver can be manually specified through the following commands:

for csh, tcsh or bash shells:

setenv NI_DRIVER X11

for korn shells:

NI_DRIVER=X11

Hexpress™ Screen Flashes Troubleshooting


export NI_DRIVER

Ultimately, the user can force a specific driver by editing the file ~/.numeca/.drivers. The driver can then bespecified in the chosen_driver colon (last colon).

7-4 Hexpress™ Screen FlashesIn some circumstances, the graphical area can flash during interactive operations, depending upon thedriver selected. This mostly happens when using the X11 driver. Setting the environment variableNI_DOUBLEBUFFERING to ON into the user profile (.cshrc, .profile, .tcshrc,...) may solve the problemunder UNIX or LINUX. The variable can be manually specified through the following commands:

for csh, tcsh or bash shells:

setenv NI_DOUBLEBUFFERING ON

for korn shells:

NI_DOUBLEBUFFERING=ONexport NI_DOUBLEBUFFERING

7-5 Hexpress™ Drivers Not Detected Hexpress™ checks the available working drivers and updates automatically the .drivers file located inuser’s .numeca directory at first launch on a new machine/display. This operation is only completed duringthe first execution, since it may take some time. As a consequence, the upgrade of drivers on an existingmachine/display cannot be automatically detected by Hexpress™.

Troubleshooting Hexpress™ Drivers Not Detected


installation note hexpress 25 4 unix-acrov5

Documents