Hi Arch Users!
I am trying to get an engineering package to work on my arch distro but having difficulty. I installed OpenSUSE in virtualbox and had the same issue, being the licensing program does not work. After some searching online it was down to lsb not being installed. After I installed lsb core in OpenSUSE I was able to get the licensing manager to work.
I would suspect it's not in Archlinux because when I stfw I see that LSB only comes as an RPM; however, it is an ISO standard, so if you stfw some more, you should be able to reproduce enough of the LSB to satisfy your software.
I do not get an error as such, the issue is that the license manager issues an ID that I need to give to software services at Uni to issue my license. That ID is blank. It was blank in OpenSUSE too but after I installed the package lsb the ID was issued (as suggested in some online forums).
The license manager (FlexLM) does not issue an ID (HostID). No error message is seen. The full package is ANSYS Fluent. Ubuntu users had a similar issue (seen at www.cfd-online.com) and resolved this issue by installing a package lsb-core.
I installed OpenSUSE on my virtual box to see if it worked there. Initially it did not. But after installing lsb and re-installing the application the license manager issued an ID, which is what I want.
So hopefully if there is any one out there wanting to run ANSYS Fluent and their other products on Archlinux, install the ld-lsb package from AUR. I will inform the maintainer to include the above mentioned.
ld-lsb 3-6 from AUR repo together with lib32-glibc from multilib and the above mentioned lsb-release and init-functions and a custom rpm-script (from CFD-Online forum [cfd-online.com/Forums/cfx/25236-ansys-workbench-uncertified-linux-distros.html]) solved all my problems which was getting lmutil to work so I can gather license statistics.
In order to connect to the CSE Computing Environment from an external device you must have the PulseVPN client installed and configured. Once the PulseVPN is setup, you can follow the below methods to connect to the CSE Computing Environment.
Users will need to know the FQDN name of their office computer in order to connect to it via RDP (e.g. cse-hncxxxxxxd.coeit.osu.edu). The computer name may be determined by right-clicking on "My Computer" and selecting "Properties". The full computer name will be listed at the bottom of the properties window. When prompted for login credentials, users should include the string COEIT\ at the beginning of their username, and use their Windows password.
The CSE Computing Staff maintain a firewall which only permits encrypted traffic from outside the CSE Instructional Network. In order to connect to the CSE UNIX environment, users must use encrypted protocols like ssh in conjunction with VPN.
where servername is faclinux for faculty and staff and stdlinux for students. X11 Forwarding has been disabled for compliance with University security policy. All users requiring a graphical session should use FastXv3 instead.
The Ohio State University Department of Computer Science & Engineering has replaced X-Win32 with FastX3 for remote Linux sessions. You would usually use this to open a remote session to stdlinux.coeit.osu.edu OR faclinux.coeit.osu.edu.
ANSYS offers a comprehensive software suite that spans the entire range of physics, providing access to virtually any field of engineering simulation that a design process requires. Supports are provided by ANSYS, Inc.
OSC has Academic Multiphysics Campus Solution license from Ansys. The license includes most of all the features that Ansys provides. See "Academic Multiphysics Campus Solution Products" in this table for all available products at OSC.
OSC has an "Academic Research " license for ANSYS. This allows for academic use of the software by Ohio faculty and students, with some restrictions. To view current ANSYS node restrictions, please see ANSYS's Terms of Use.
Due to the way our Fluent and ANSYS modules are configured, simultaneously loading multiple of either module will cause a cryptic error. The most common case of this happening is when multiple of a user's jobs are started at the same time and all load the module at once. In order for this error to manifest, the modules have to be loaded at precisely the same time; a rare occurrence, but a probable occurrence over the long term.
If you frequently submit large amounts of Fluent or ANSYS jobs, we recommend you stagger your job submit times to lower the chances of two jobs starting at the same time, and hence loading the module at the same time. Another solution is to establish job dependencies between jobs, so jobs will only start one after another. To do this, you would add the SLURM directive:
ANSYS Mechanical is a finite element analysis (FEA) tool that enables you to analyze complex product architectures and solve difficult mechanical problems. You can use ANSYS Mechanical to simulate real world behavior of components and sub-systems, and customize it to test design variations quickly and accurately.
When you log into owens.osc.edu you are actually logged into a linux box referred to as the login node. To gain access to the mutiple processors in the computing environment, you must submit your ANSYS Mechanical analysis to the batch system for execution. Batch jobs can request mutiple nodes/cores and compute time up to the limits of the OSC systems. Refer to Queues and Reservations and Batch Limit Rules for more info. Batch jobs run on the compute nodes of the system and not on the login node. It is desirable for big problems since more resources can be used.
Interactive mode is similar to running ANSYS Mechanical on a desktop machine in that the graphical user interface will be sent from OSC and displayed on the local machine. Interactive jobs are run on compute nodes of the cluster, by turning on X11 forwarding. The intention is that users can run ANSYS Mechanical interactively for the purpose of building their model and preparing their input file. Once developed this input file can then be run in no-interactive batch mode.
You may adjust the numbers per your need. This job will queue until resources becomes available. Once the job is started, you're automatically logged in on the compute node; and you can launch ANSYS Mechanical and start the graphic interface with the following commands:
A batch script can be created and submitted for a serial or parallel run. You can create the batch script using any text editor you like in a working directory on the system of your choice. For a given model, prepare the input file with ANSYS Mechanical commands (named ansys.in for example) for the batch run. Below is the example batch script ( job.txt ) for a serial run:
To take advantage of the powerful compute resources at OSC, you may choose to run distributed ANSYS Mechanical for large problems. Multiple nodes and cores can be requested to accelerate the solution time. Note that you'll need to change your batch script slightly for distributed runs.
Currently, there are in total 50 ANSYS base license tokens and 900 HPC tokens for academic users. These base tokens and HPC tokens are shared with all ANSYS products we have at OSC. A base license token will allow CFX to use up to 4 cores without any additional tokens. If you want to use more than 4 cores, you will need an additional "HPC" token per core. For instance, a serial CFX job with 1 core will need 1 base license token while a parallel CFX job with 28 cores will need 1 base license token and 24 HPC tokens.
When you log into owens.osc.edu you are actually logged into a linux box referred to as the login node. To gain access to the mutiple processors in the computing environment, you must submit your analysis to the batch system for execution. Batch jobs can request mutiple nodes/cores and compute time up to the limits of the OSC systems. Refer to Queues and Reservations and Batch Limit Rules for more info. Batch jobs run on the compute nodes of the system and not on the login node. It is desirable for big problems since more resources can be used.
Interactive mode is similar to running CFX on a desktop machine in that the graphical user interface will be sent from OSC and displayed on the local machine. Interactive jobs are run on compute nodes of the cluster, by turning on X11 forwarding. The intention is that users can run CFX interactively for the purpose of building their model and preparing their input file. Once developed this input file can then be run in no-interactive batch mode.
To run interactive CFX GUI, a batch job need to be submitted from the login node, to request necessary compute resources, with X11 forwarding. Please follwoing the steps below to use CFX GUI interactivly:
In addition to requesting the base license token ( -L ansys@osc:1 ), you need to request copies of the ansyspar license, i.e., HPC tokens ( -L ansys@osc:1,ansyspar@osc:[n] ), where [n] is equal to the number of cores you requested minus 4.
Currently, there are in total 50 ANSYS base license tokens and 900 HPC tokens for academic users. These base tokens and HPC tokens are shared with all ANSYS products we have at OSC. A base license token will allow FLUENT to use up to 4 cores without any additional tokens. If you want to use more than 4 cores, you will need an additional "HPC" token per core. For instance, a serial FLUENT job with 1 core will need 1 base license token while a parallel FLUENT job with 28 cores will need 1 base license token and 24 HPC tokens.
When you log into owens.osc.edu you are actually logged into a Linux box referred to as the login node. To gain access to the multiple processors in the computing environment, you must submit your FLUENT analysis to the batch system for execution. Batch jobs can request multiple nodes/cores and compute time up to the limits of the OSC systems. Refer to Queues and Reservations and Batch Limit Rules for more info. Batch jobs run on the compute nodes of the system and not on the login node. It is desirable for big problems since more resources can be used.
c80f0f1006