-
-
June 17, 2019 at 6:21 pm
aliborhan
SubscriberWe have been using an old version (v 11) of License Manager on our Linux server for many years. We just renewed our license and tried installing version 19.2 of the License Manager. Upon installation, we get the following error and cannot open the license manager:
Problems were encountered running the licensing configuration.
Updating /home/ansys_inc/shared_files/licensing/init_ansysli ...
We tried installing the new LM in the same directory as the old one. Do we have to uninstall the old license manager first? I would appreciate any help to resolve this issue.
-
June 17, 2019 at 9:04 pm
tsiriaks
Ansys EmployeeHmm, then it's likely that your OS is very old. What is the output of this command
cat /etc/*release
Do you have ANSYS products installed under /home/ansysinc/ ? If not, I would recommend to wipe out this entire folder before trying the License Manager v19.2 installation. Also, make sure there is no ansysli_server, ansysli_monitor, lmgrd (from ANSYS), and ansyslmd running before you try the reinstall.
If issue persists, please post the entire content of install.err file under /home/ansysinc/
Thanks,
Win
-
June 18, 2019 at 12:14 am
aliborhan
SubscriberYes, our OS is old. The output is
CentOS release 5.4 (Final)
Our old LM is installed under /home/ansys_inc/ and that is where we tried to install 19.2. Should we wipe out the ~ansys_inc directory and then install under /home/ansysinc/ ? We had stopped the license manager before installing. Below, I have attached the contents of install.err and install_licconfig.err from our first two installation attempts.
Thank you for your help.
Ali
>>>
>
ANSYS installation: Fri Jun 14 16:57:59 2019
Revision: Release 19.2
###### Warnings/errors #######
Warnings/errors were encountered while running the ANSYS License Manager configuration. Please check the install_licconfig.err file in the installation directory for details.
>>>
>
>>>
>
ANSYS installation: Fri Jun 14 17:02:44 2019
Revision: Release 19.2
###### Warnings/errors #######
Warnings/errors were encountered while running the ANSYS License Manager configuration. Please check the install_licconfig.err file in the installation directory for details.
>>>
>
-
June 18, 2019 at 12:44 am
aliborhan
SubscriberAnd here is install_licconfig.err
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
2019/06/14 16:57:49 ...FATAL ERROR: The Tomcat server currently is running either from another installation directory or in a way that cannot be stopped.
It must be stopped before the licensing configuration can continue. Exiting.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
2019/06/14 17:020 ...ERROR: Attempt to execute the command to retrieve information used to determine whether the following file should be moved failed with exit code 127 and process status 0:
"/home/ansys_inc/shared_files/licensing/linx64/update/ansysli_client"
Therefore, this file will not be processed even though it may need to be moved. It will remain in the update directory.
2019/06/14 17:024 ...ERROR: Attempt to execute the command to retrieve information used to determine whether the following file should be moved failed with exit code 127 and process status 0:
"/home/ansys_inc/shared_files/licensing/linx64/update/ansysli_util"
Therefore, this file will not be processed even though it may need to be moved. It will remain in the update directory.
2019/06/14 17:02:40 ...ERROR: Attempt to run the following command failed with exit code 1 and process status 0:
"/home/ansys_inc/shared_files/licensing/linx64/ansysli_util" -updatesiteprefs
2019/06/14 17:02:40
Start of update site preferences (product order) processing output
ERROR: Unknown option: -updatesiteprefs
Usage : /home/ansys_inc/shared_files/licensing/linx64/ansysli_util [-option argument] [-option] ...
[-log] Logs the ansysli_util output to a file instead of stdout.
[-getlicpath [>]] Retrieve the license path for this installation.
[-printlicpath []] Retrieve the license path for this installation and print to screen.
[-parseflexlog] Parse the usage from the passed FLEXlm log.
[-parseflexlogusers] Parse the usage from the passed FLEXlm log and include remaining user list.
[-help] Display this usage summary.
[-version []] Display the ansysli version information (long, short, build, or ali).
[-envvar []] Displays the value for the passed env var if passed or the values of several licensing related
environment variables.
[-hostinfo []] Displays information on this [default] or supplied host.
[-timezone] Displays the ANSYS timezone value for this system.
[-statli []] Display the status information on the ansysli_server running on this system unless the port@host of
another system is supplied.
The following command line options pertain to site license preferences:
[-getsiteprefs] Retrieve site license preferences and write them to the designated file.
[-savesiteprefs] Save updated site license preferences from the designated file.
[-deletesiteprefs] Deletes the currently save site preferences.
The following command line options pertain to user preference retrieval/update for the designated revision (-revn):
[-revn] Identify the ANSYS, Inc. revision to use for license preferences.
[-getuserprefs] Retrieve current user's license preferences and write them to the designated file.
[-saveuserprefs] Save current user's license preferences from the designated file.
[-deleteuserprefs] Deletes the current user's saved license preferences.
[-getavail] Retrieve the list of available licensed features in an XML format.
[-cap] The capability to retrieve usage for.
[-getcapdef] Retrieve the capability availability in an XML format.
[-printcapdef []] Show capability availability.
[-capcount] Retrieve the number of available tasks for the given capability.
[-printliccapdef []] Show licensed capability availability.
[-getqueueusage] Retrieve the list of queued capabilities in an XML format.
[-purge_wb_usage] Cleaning up the usage data that is older than the Specified number of days.
[-printqueueusage []] Show current queue usage.
[-printavail] Print an easy to read list of available licensed products.
[-printusage] Show current usage.
[-getcn] Print the list of available customer numbers.
The following options are for license test checkouts:
[-prefsvr] Specify a preferred server to connect to.
[-preffeat] Specify a preferred feature to checkout.
[-andcap] Capability(ies) to AND with the checkout capability. Separate multiple values with ':'.
[-checkloop <#>] Number of times to loop requesting the following checkout(s) (see -checkout option).
[-checkcount <#>] Number of tasks to checkout per request with the following checkout(s) (see -checkout option).
[-checkout] Checkout specified capability or feature.
The following options are for reserved licenses:
[-reserve_list] Display the active list of license reserves.
[-return_reserve_by_id] Return Reserve for the ID specified.
[-return_reserve_by_user] Return Reserves for the specified user.
[-return_reserve_all] Return all outstanding Reserves for all users.
The following options are to list/remove used licenses:
[-liusage [<user]@[host]:[pid]:][feature]> Display the list of used licenses.
[-liremove <[user]@[host][id]>] Return the license used by the specified user.
2019/06/14 17:02:40
End of update site preferences (product order) processing output
...ERROR: The automatic updating of any existing site preferences (product order) failed. If site preferences have not been set on this
license server machine, you may ignore this error. If site preferences have been set or you're not sure, please refer to the following
Troubleshooting section in the ANSYS Licensing Guide for additional details:
License Manager Installation's Licensing Configuration Step to Update Site Preferences (Product Order) Failed -
June 18, 2019 at 7:29 pm
tsiriaks
Ansys EmployeeYou can use /home/ansys_inc/ , I just copied the path that you posted earlier, maybe there was some issue during the post.
Let's neglect the fact that the OS is not supported for now (this might be the issue).
Try kill all ANSYS processes including Tomcat
wipe the entire /home/ansys_inc/
install LSB (yum install redhat-lsb)
then install ANSYS License Manager 19.2
do you still get any error ?
Thanks,
Win
-
June 19, 2019 at 5:21 am
aliborhan
SubscriberDo I need to uninstall the old license manager or is it sufficient to just remove the directory /home/ansys_inc?
We have a large number of cases that run in v14.5 and that is why we have not updated the software. If I remove the /home/ansys_inc directory, would I lose the ansys 14.5 program files?
I tried installing LSB using the command you provided, but got the following error message:
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=5&arch=x86_64&repo=addons error was
[Errno 4] IOError:
Error: Cannot find a valid baseurl for repo: addons
Thanks,
Ali
-
June 19, 2019 at 6:53 pm
tsiriaks
Ansys EmployeeHi Ali,
Ah, I didn't know that the same machine is also running ANSYS products (v14.5) .
You don't need to uninstall License Manager but you definitely can't remove the /home/ansys_inc/
For issue installing LSB, I'm not sure about this but you can check some suggestions here
https://unix.stackexchange.com/questions/22924/how-can-i-fix-cannot-find-a-valid-baseurl-for-repo-errors-on-centos
The LSB is required for later versions of ANSYS License Manager, so you would need to get this installed successfully first.
Thanks,
Win
-
June 21, 2019 at 3:43 pm
aliborhan
SubscriberHi Win,
We installed LSB and tried to install the LM, but got an installation error again. Here are the contents of install.err and install_licconfig.err
>>>
>
ANSYS installation: Fri Jun 21 11:06:29 2019
Revision: Release 19.2
###### Warnings/errors #######
Warnings/errors were encountered while running the ANSYS License Manager configuration. Please check the install_licconfig.err file in the installation directory for details.
>>>
>
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
2019/06/21 11:06:20 ...FATAL ERROR: The Tomcat server did not stop correctly. Please check permissions and the Tomcat log files at the following location:
/home/ansys_inc/shared_files/licensing/tools/tomcat/logs
The licensing configuration cannot continue until this issue is resolved. Exiting.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Any suggestions? Thanks.
Ali
-
June 21, 2019 at 4:30 pm
tsiriaks
Ansys EmployeeHi Ali,
Let's do this
kill all ANSYS related processes including any tomcat processes
remove the /home/ansys_inc/shared_files folder
reinstall
does this make any difference ?
Thanks,
Win
-
June 21, 2019 at 5:06 pm
-
June 21, 2019 at 8:45 pm
tsiriaks
Ansys EmployeeHi Ali,
Please post the error from /home/ansys_inc/*.err files
Also, try starting this manually from command to see more error. You can use the following command with root privileges
/home/ansys_inc/shared_files/licensing/start_ansysli
If issue persists, post the content of
/home/ansys_inc/shared_files/licensing/ansysli_server.log
and
/home/ansys_inc/shared_files/licensing/license.log
Thanks,
Win
-
June 22, 2019 at 12:21 am
aliborhan
SubscriberHi Win,
Starting from command line results in the following error:
[root@head ~]# /home/ansys_inc/shared_files/licensing/start_ansysli
/home/ansys_inc/shared_files/licensing/linx64/ansysli_server: error while loading shared libraries: liblber-2.4.so.2: cannot open shared object file: No such file or directory
There are no *.log files in /home/ansys_inc/shared_files/licensing.
[root@head licensing]# ls /home/ansys_inc/shared_files/licensing
ansysli_data init_ansyslm_tomcat linx64 start_lmcenter
ansys_pid language logs_backup stop_ansysli
gatherdiagnostics lic_admin prodord stop_lmcenter
init_ansysli license_files start_ansysli tools
I will post the contents of /home/ansys_inc/*.err files in the next post.
Thanks.
Ali
-
June 22, 2019 at 12:25 am
aliborhan
SubscriberHere are the contents of /home/ansys_inc/*.err files:
>>>
>
ANSYS installation: Fri Jun 21 12:44:24 2019
Revision: Release 19.2
###### Warnings/errors #######
Warnings/errors were encountered while running the ANSYS License Manager configuration. Please check the install_licconfig.err file in the installation directory for details.
>>>
>
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
2019/06/21 12:44:24 ...ERROR: Attempt to run the following command failed with exit code 127 and process status 0:
"/home/ansys_inc/shared_files/licensing/linx64/ansysli_util" -updatesiteprefs
2019/06/21 12:44:24
Start of update site preferences (product order) processing output
/home/ansys_inc/shared_files/licensing/linx64/ansysli_util: error while loading shared libraries: liblber-2.4.so.2: cannot open shared object file: No such file or directory
2019/06/21 12:44:24
End of update site preferences (product order) processing output
...ERROR: The automatic updating of any existing site preferences (product order) failed. If site preferences have not been set on this
license server machine, you may ignore this error. If site preferences have been set or you're not sure, please refer to the following
Troubleshooting section in the ANSYS Licensing Guide for additional details:
License Manager Installation's Licensing Configuration Step to Update Site Preferences (Product Order) Failed
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
-
June 24, 2019 at 4:46 pm
tsiriaks
Ansys EmployeeThe systems does not have liblber-2.4.so.2 which is included in openldap package. I can't find the exact version for your CentOS 5.4 as it's too old, ref:
https://www.rpmfind.net/linux/rpm2html/search.php?query=liblber-2.4.so.2
or
https://pkgs.org/download/liblber-2.4.so.2()(64bit)
I strongly recommend updating your OS version.
But if you want to try and push through this, this forum might help (with this current issue)
https://www.linuxquestions.org/questions/linux-server-73/libldap-2-4-so-2-cannot-open-shared-object-file-no-such-file-or-directory-4175548855/
Thanks,
Win
-
June 24, 2019 at 4:54 pm
aliborhan
SubscriberHi Win,
We uninstalled the old license manager and then installed version 17 of LM. It installed without any errors. No errors in the *.err files. When tried to read the license file it shows the following error:
We then started ansysli manually as you suggested and the command was executed without error. However, when we tried to start from the license manager center, we still got the same error as shown above. Now we do have an ansysli_server.log file. I am sending you the content in the next post. It complains that no initialization file is found. I noticed that init_ansysli and init_ansyslm_tomcat are not in the /etc/init.d directory. Shouldn't they be there?
Thanks.
Ali
-
June 24, 2019 at 5:57 pm
aliborhan
SubscriberHi Win,
We were able to install LM 17.0 without any OS issues. The problem is getting the license manager to start. I posted the log file that you had asked for. Thanks.
Ali
-
June 24, 2019 at 8:52 pm
tsiriaks
Ansys EmployeeAli,
The initialization file (ansyslmd.ini) is required only when you try to launch product (Mechanical, Fluids) , it's not required to start License Manager. You still have issue starting ansysli_server successfully (please make sure port 2325 is open, which is used by ansysli_server)
Kill all ANSYS related processes, then try this command
/home/ansys_inc/shared_files/licensing/linx64/ansysli_server -k start
what error do you see ?
Thanks,
Win
-
June 25, 2019 at 1:49 pm
aliborhan
SubscriberHi Win,
It does not like the "-k start" option. Here is the error:
[root@head ~]# /home/ansys_inc/shared_files/licensing/linx64/ansysli_server -k start
ERROR: Unknown option: -k
Usage : /home/ansys_inc/shared_files/licensing/linx64/ansysli_server [-option argument] [-option] ...
[-help] Show help/usage information.
[-log
] Log debug ansysli_server usage information to the designated file.
[-logtype
] Indicates the level of debug (either STANDARD [default] or CONNECTIONS or VERBOSE) that should be logged.
[-ijou
] Specify the input journal file
[-ojou
] Specify the output journal file
[-monitorlog
] Sets the log file for the monitor.
[-port_timeout
] Specifies the time to wait for the server's port to clear.
[-restart_port_timeout
] Specifies the monitor's wait time for the server's port to clear.
[-nodaemon] Do not daemonize the server.
[-noflex] Forces ansysli_server to NOT start FLEXlm, the default is to start it.
[-cacheflexlic] Designates the FLEXlm license file to cache. This option is valid only when used with -noflex option.
[-cache_srv
] License servers to be cached at startup.
[-UseFlexOpts
] Indicate if the ANSYS Licensing Interconnect should process the FLEXlm options file entries.
[-UseClientIp
] Indicate if the ANSYS Licensing Interconnect should use the IP address passed by the client when handling
FLEXlm options file entries.
[-UseLmProject
] Indicate if the ANSYS Licensing Interconnect should use the LM_PROJECT passed by the first client when
checking out licenses.
[-IpOverride
] Indicate if the ANSYS Licensing Interconnect should override the IP passed to FLEXlm. Default is to
override.
[-nomonitor] Do not start the ansysli monitor.
[-ini
] Read the startup options from the designated ansysli initialization (ansyslmd.ini) file.
[-report
] Log usage information to the designated directory.
[-version [
]] Display the ansysli version information (long, short, build, ali, or revn).
[-user] Only the user who started the server can shut it down.
[-group
] Only a member of the given group can shutdown the server.
[-reservegroup
] Identify the group or (comma separated list of) groups that are allowed to return reserved licenses for all
users.
[-reserveuser
] Identify the user or (comma separated list of) users that are allowed to return reserved licenses for all
users.
[-queuing_interval
] Specify the queuing interval when checkout attempts are performed on queued requests.
[-max_queued_requests
] Specify the number of maximum queued requests.
[-usage_archive_interval
] Specify the number of minutes before archiving WB license usage tracking information, defaults to 60
minutes.
[-purge_wb_usage
] Specify the number of days to keep archived WB license usage tracking information before purging it,
defaults to 28 days.
[-dp_reserve
] Indicate if the ANSYS Licensing Interconnect should allow the DesignPoint Reserve or not. It is "on" by
default.
[-wb_usage
] Specify whether or not WB license usage tracking is supported, default is to support it.
[-ignore_flexsvr
] Identifies the host name, ip, or comma separated list of FLEXlm server or servers that should be
ignored for all FLEXlm operations.
[-IdleTimeoutMax
] Specify the maximum timeout value before an idle license is returned. Defaults to 1200 seconds (20 minutes).
[-fnp_ip_env
] Bypass hostname resolution during the checkout call.
[-fnp_restart_attempts
] Specify the number of times the ANSYS Licensing Interconnect should attempt to restart the FlexNet server.
[-c
] Forwarded to FLEXlm lmgrd: Designates the FLEXlm license file.
[-l
] Forwarded to FLEXlm lmgrd: Designates the FLEXlm debug log file.
[-local] Forwarded to FLEXlm lmgrd: See FLEXlm End User's Guide for description.
[-x
] Forwarded to FLEXlm lmgrd: See FLEXlm End User's Guide for description.
[-k info [port@host]] Return information on the server running at port@host(*)
[-k reread [port@host]] Reread information for the server running at port@host(*).
[-k stop [port@host]] Stop the server running at port@host(*)
[-k stop_triad [port@host]] Stop the server running at port@host(*) and its associated triad servers.
* If port@host is not given, tries to detect
a running server on the localhost automatically.
-
June 25, 2019 at 6:58 pm
tsiriaks
Ansys EmployeeTry this instead
/home/ansys_inc/shared_files/licensing/linx64/ansysli_server &
-
June 26, 2019 at 7:01 pm
-
June 26, 2019 at 9:22 pm
tsiriaks
Ansys EmployeeHi Ali,
What is showing in the ansysli_server.log ?
-
June 26, 2019 at 11:33 pm
aliborhan
SubscriberHi Win,
Here is the ansysli_server.log:
NORMAL STARTUP 2019/06/26 14:503
ANSYS Licensing Interconnect version 1.7.0 (20151130) for linx64. Updated at ANSYS Build 17.0. Started on 2019/06/26 14:50
3 by root@head:linx64 with pid 13649.
(C) 2015 SAS IP, Inc. All Rights Reserved.
Unauthorized use, distribution, or duplication is prohibited:
Built Using FlexNet Publisher v11.13.1.2 build 173085 x64_lsb
Please note that entries in this debug log have the following format:
TIMESTAMP ACTION FEATURE REVISION (BUILD DATE) A/B/C/D W/X/Y/Z PID:MPID:APP:USER@HOST
LATFORM
ISPLAY SOCKET:IP
Licenses statistics:
A is the number of licenses requested by this ACTION.
B is the number of licenses used by this USER.
C is the number of licenses used by all users.
D is the number of licenses available in the local license pool.
License server performance statistics:
W is the number of currently connected client applications.
X is the maximum number of connected client applications.
Y is the unique serial number of this client application.
Z is the number of all client applications served by this Licensing Interconnect server.
2019/06/26 14:50
3 INFO ANSYSLI_CMD=/home/ansys_inc/shared_files/licensing/linx64/ansysli_server
2019/06/26 14:50
3 INFO ANSYSLI_INITIALIZATION_FILE=No initialization file found.
2019/06/26 14:50
3 INFO ANSYSLI_MONITOR=/home/ansys_inc/shared_files/licensing/linx64/ansysli_monitor
2019/06/26 14:50
3 INFO ANSYSLI_PRODORD_FILE='/home/ansys_inc/shared_files/licensing/prodord/ansysli.prodord.xml'
2019/06/26 14:50
4 INFO FLEXLM_LICENSE_FILE='/home/ansys_inc/shared_files/licensing/license_files'
Thanks,
Ali
-
June 27, 2019 at 3:46 pm
tsiriaks
Ansys EmployeeAli,
Do you have any kind of security or Firewall running (like SELinux , Iptables, Firewalld , etc.) ?
Can you try turning them all off before starting the License Manager ?
It's odd that it doesn't show any error but ansysli_server never starts.
Thanks,
Win
-
June 28, 2019 at 12:22 am
aliborhan
SubscriberHi Win,
I have stopped lptables so it does not seem to be a firewall issue. It seems like the license manager cannot find the license server. When I try to set license preferences, I get the error "could not connect to any license server". The head node on our cluster is the license server and the external IP address for the cluster was recently changed. Could that be causing a problem? The first few lines in the license file are as follows:
SERVER head 003048dc8258 1055
VENDOR ansyslmd
USE_SERVER
The host name "head" is associated with the cluster's internal IP address in the /etc/hosts file so the external IP should not make a difference when I try to start the license manager right on the head node. Correct? Any other suggestions?
Thanks.
Ali
-
June 28, 2019 at 1:16 am
tsiriaks
Ansys EmployeeHi Ali,
I don't think this would be related to IP resolution issue but you can try this
create /home/ansys_inc/shared_files/licensing/ansyslmd.ini file
with content
SERVER=1055@localhost
ANSYSLI_SERVERS=2325@localhost
ANSYSLI_EXTERNAL_IP=your_external_ip
then modify the content of license file in /home/ansys_inc/shared_files/licensing/license_files
from
SERVER head 003048dc8258 1055
to
SERVER 127.0.0.1 003048dc8258 1055
and try starting the ansysli_server again
Thanks,
Win
-
June 28, 2019 at 8:49 pm
tsiriaks
Ansys EmployeeHi Ali,
So, it's like what I thought. This has nothing to do with IP resolution. It's just ansysli_server couldn't start on port 2325 for some reason.
If everything is working correctly, your next line is supposed to show
INFO ANSYSLI_PORT=2325
Because ansysli_server couldn't start, you can't use any feature that would call it. That includes setting license preferences.
It's something on the systems preventing this or it's just because of the OS incompatibility.
Thanks,
Win
-
June 30, 2019 at 9:06 pm
aliborhan
Subscriber
Hi Win,
If it were an OS incompatibility, wouldn't the installation of the license manager lead to error? CentOS 5 was still being updated when LM 17 came out so I would think it should be compatible with LM 17. The only change to our server from last year is that it has been moved to a new data center and has a new external IP address. I was told that the data center firewall is allowing communication to ports 2325 and 1055. Would the external IP play any role here? Does the license file have to be changed? The Hostid is the same as before.
If we were to use a new Windows machine as our license server instead (to bypass the current problem), could we still use our linux cluster to run fluent in parallel using our HPC licenses or does that introduce new issues?
Thank you for your help.
Ali
-
July 1, 2019 at 6:36 pm
tsiriaks
Ansys EmployeeHi Ali,
Installing is a different story than running.
Here is the link for platform support dated back to v16.0
https://www.ansys.com/solutions/solutions-by-role/it-professionals/platform-support/previous-releases
Particularly the link for 17.0 is here
https://www.ansys.com/-/media/ansys/corporate/files/pdf/solutions/it-professionals/platform-support/platform-support-by-application-17.pdf?la=en&hash=552BB2920F630DEB9EB6428D2D4AC48A3659C8AD
Again, IP has nothing to do with this issue (and no, you do not need a new license file just for IP change). Even if port 2325 was not open, it'd have shown an error about it but, in your case, it just disappears.
All licensing functionality is the same regardless of where you host the license as long as you have network communications configured with it.
Thanks,
Win
-
July 8, 2019 at 5:19 am
aliborhan
SubscriberHi Win,
We installed LM17 on our Windows server (E5-CHE-ANSYSLIC) and started the license server. On our Linux cluster, we specified the new license server and tried running fluent. We get the following error:
ANSYS LICENSE MANAGER ERROR: Could not connect to any license server.
The server is down or is not responsive.
ANSYSLI_SERVERS: 2325@E5-CHE-ANSYSLIC
FLEXlm Servers: 1055@E5-CHE-ANSYSLIC
Cannot find license file.
The license files (or license server system network addresses) attempted are
listed below. Use LM_LICENSE_FILE to use a different license file,
or contact your software provider for a license file.
Feature: fluent
Filename: /home/ansys_14.5.7/ansys_inc/v145/fluent/license/lnamd64/../license.dat
License path: /home/ansys_14.5.7/ansys_inc/v145/fluent/license/lnamd64 -
/ ../license.dat
FLEXnet Licensing error:-1,359. System Error: 2 "No such file or directory"
We can ping E5-CHE-ANSYSLIC from the cluster so the error that it cannot connect to the license server is puzzling. It looks like the cluster is trying to find the license file in its old location on the Linux machine (when we were using the Linux head node as the license server). Can you tell us what we need to do on the client side (the Linux cluster) with LM17?
Thank you for your help.
Ali
-
July 9, 2019 at 2:21 pm
ANSYS_MMadore
Ansys EmployeeHello Ali,
Can you make sure that the Windows server is open for communications? If there is a firewall, you will need to have exceptions for these licensing executables.
lmgrd
ansyslmd
ansysli_server
ansysli_monitor
ansysli_client
You can test by running a telnet from the Linux side to the Windows server on these specific ports.
telnet E5-CHE-ANSYSLIC 1055
telnet E5-CHE-ANSYSLIC 2325
Thank you,
Matt
-
- You must be logged in to reply to this topic.

Boost Ansys Fluent Simulations with AWS
Computational Fluid Dynamics (CFD) helps engineers design products in which the flow of fluid components is a significant challenge. These different use cases often require large complex models to solve on a traditional workstation. Click here to join this event to learn how to leverage Ansys Fluids on the cloud, thanks to Ansys Gateway powered by AWS.

Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.

Ansys Blog
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- Error with workbench SceneGraphChart
- How can I renew ANSYS student version license?
- License Error
- Workbench error
- Workbench not opening
- Sizing on Ansys Workbench 19.2
- Error: Exception of type ‘Ansys.Fluent.Cortex.Cortex not availableException’ was thrown
- Ansys2021R2 ansys212 seg faults immediately on RHEL8.2
- Licensing error while opening ANSYS Mechanical
- An error occurred when the post processor attempted to load a specific result.
-
3744
-
2573
-
1803
-
1236
-
594
© 2023 Copyright ANSYS, Inc. All rights reserved.