Lmgrd Download

0 views
Skip to first unread message

Author Metcalfe

unread,
Aug 4, 2024, 2:39:09 PM8/4/24
to inralale
Im having trouble migrating my FlexNet Publisher onto a Linux server. I am running the command nohup lmgrd -c license.dat in the directory of where the Flexnet Publisher software is downloaded but I would get this error:

I have tried using nohup ./lmgrd -c license.dat -l debug.log which throws an error where the port number in the license is already in use. But after it attempts to run again, it will successfully start the FlexNet. However, I still can't use the floating license. The log file says under Startup/Restart Info that "Is FlexNet Licensing Service installed and compatible: No" which makes me believe that the initial command I ran is incorrect.


The other problem with conflicting port number was that the main service (lmgrd) was running on 8224 and if you don't specify the port for the vendor daemon (armlmd), armlmd will attempt to run on 8224 as well. So lmgrd will complain that it's port is in use.


We are running the lmgrd license server on a bare metal linux system. From my understanding, a Linux-based lmgrd uses the MAC address of the primary ethernet board as the parameter from which the keys are generated against (as indicated by lmhostid). BTW, on a SunOS machine there is the hostid that is derived from the eeprom on the motherboard.


Ok, what we want to do is put the lmgrd licensing server on a VM. Afterall, its a heck of a waste for a single bare metal server system just to support a license server. However, it seems that the support person for the software vendor using the lmgrd licensing model says that it is not possible to operate in this manner. As there is a MAC address for the installed ethernet board, the support person would seem to be in error. To what I see, there should be no differences between the VM and the bare metal linux server.


ADDITION: lmhostid returns the MAC address from only eth0! If the interface in the VM is not named eth0, then it returns nothing! It is easy to rename the interface in SuSe linux ...so no problem there.


I run FlexLM, which leverages lmgrd on a Windows server in a VM for Matlab and Maple and have zero issues. Virtual adapters (typically) have their own MAC address, so the software generates the necessary values from that. I did get push back from someone at Simio, which also uses a LM that is similar. I made enough noise that they waived the restriction for me. All they had to do was issue a different license.


It's not entirely analogous to your system, but your hunch is likely right. The support person is probably only slightly above clueless. You'll probably be able to get a definitive answer if you post the software in question.


I've been trying everything I can think of (specified port for ptc_d and matched firewall rules, manually installing everything according to instructions, tried different versions) and has searched for an answer but have found none where it wasn't the firewall. I've tested the firewall for port 7788 by configuring another software to listen to the port and it was reachable.


After reading a lot about other vendors installations using lmadmin I created the directory \licensing\ptc and copied ptc_d.exe and ptc.opt to that directory, for good measure i also copied ptc_d.exe to \licensing.


This should have no effect without changing the DAEMON line in license.dat, then I restarted the lmadmin service (I wanted to trace the log output).. and suddenly it worked. Other then that I have not changed anything else.


Is the fix to eliminate all spaces in the installation/daemon/license path? Or do I need to set an LM_LICENSE_FILE environment variable or use a different version of the FlexLM software? All other options (firewall rules, hostID, etc) are as they should be.


I am not sure how both got installed, whether it is by default or if I screwed up . lmadmin_ptc is a Web based license manager, PTC FlexNet the familiar lmtools. I did not want to use the Web service license manager so we disabled lmadmin_ptc. (The naming convention seems somewhat counterintuitive to me...)


So, check the services running on your license server. If you have BOTH lmadmin_ptc and PTC FlexNet running, you have to disable one of them, and make sure all the configs are pointing to the correct paths for the other. (PTC FlexNet is the old familiar LMTOOLS and is what I wanted to use.)


2. There is another license manager running on the server (CW License Manager). It also uses lmgrd.exe for communication. But it uses port 27000, so that should not be the problem, because lmgrd of FlexLm uses port 7788.


I'm doing my best to wrap my puny artist brain around the procedure to get the Autodesk NLM running so I can use the Arnold renderer in Cinema 4D. After two hours of reading through the directions and jumping from site to site I'm asking for help.


I'm on a Mac running 10.11.6. I downloaded the nlm11.13.1.2_ipv4_ipv6_mac_universal.pkg and ran that installer. My first problem was that it didn't look like anything had been installed on my system, but once I entered some terminal commands to show hidden files I could see the files being referred to in the setup instructions.


That path doesn't correspond to what's on my system. There is a hidden private/var/flexlm folder on my system drive. I have no idea where that came from or what it's for. Is it supposed to be in the local folder?


This is insanely frustrating, confusing and NON-customer friendly. In our two-person company I'm the co-owner, animator and IT-guy. Paraphrasing Dr. McCoy, "I'm an artist, not a computer software engineer." Adobe, Maxon, Insydium, etc. don't force me to jump through these Terminal-centric hoops.


Similarly, you have to replace debug_log_path with the path you want to use for your log file. The file doesn't have to exist, lmgrd will create it. You do need write permissions for the file.


Thank you so much for this! Spent a whole night reading different versions of documentation for this process to no avail! Then thankfully I stumbled on this! Please update your documentation for this process AUTODESK, so unclear and cryptic!


Any resolution to this? Glad I found your post, same frustrating experience for me as well. I still can't get the watermark removed. Inside of C4D when launching the connect to license server, it at least now says there's 1 NLM license (0 in use). So the server is at least running, still can't figure out how to assign it.


Basically I ended up contacting Stephen Blair at Solid Angle, giving him control of my Mac Pro via Team Viewer and letting him set up everything. IIRC it took him a while. I think my problem stemmed from the C4D R19 installer really wanting to install C4D into my Username/Applications folder rather than the usual System Drive/Applications folder. That made it tricky to properly install Arnold, and some file paths got messed up.


Having a guy manually install license servers and such for so many users of a piece of software seems crazy to me. I'm very glad Stephen's available to do that, but I sure would like a system that simply requires typing in some serial numbers or logging in to a subscription service, like, literally, every other piece of software I use.


OS I have tried are Windows server 2003 R2 and windows server and windows server 2003 R2 64bit. Both come back with the same error. I have installed the required C++ redist as suggested. I've also restarted the host machines to see if that helped to no avail.


Oliver,


I have been doing some searching and I think the problem is that hte Flex tools 11.12 are not compatible with Windows Server 2003. We will have to get you an older version. I believe we still have these but I will have to search around and fine the files.


Regards,

John


I have tried older versions of lmgrd etc I have other licenses running on one of the Server 2003 machines without issue. From the log files the lmgrd is starting without problem and the issue seems to be with tidspssw.exe


The license manager daemon lmgrd handles the initial contact with the client application programs, passing the connection on to the appropriate vendor daemon. It also starts and restarts the vendor daemons.


The lmgrd program is the main daemon program for FLEXlm. When you invoke lmgrd, the program looks for a license file that contains information about vendors and features. On UNIX and Linux platforms we recommend that you run lmgrd as a non-privileged user (not root).


See The FLEXlm End User's Guide Version 9.2 listed under Support & ServicesTechnical SupportLicensing on the ABAQUS Home Page for more information on FLEXlm licensing. Syntax and Optionslmgrd [-c license_file_list] [-l [+]debug_log_path] [-2 -p] [-local] [-x lmdown] [-x lmremove] [-z] [-v] [-help]-c license_file_listSpecifies the license files to use.


-x lmdownDisables the lmdown command (no user can run lmdown). If lmdown is disabled, you need to stop lmgrd via kill pid (UNIX platforms) or stop the lmgrd and vendor daemon processes through the Windows Task Manager or Windows service. On UNIX platforms, verify that the kill command does not contain the -9 option.


-zRuns in foreground. The default behavior is to run in the background. If -l debug_log_path is present, no windows are used. If no -l options are specified, separate windows are used for lmgrd and each vendor daemon.


In this particular case, lmgrd was being run by a different user than the one who created the license file. Therefore it did not have permission to chmod the license file and the chmod failed. This resulted in the error reported and failure to start up.


The error was resolved by having the license file's owner manually change the permission of the license file from 755 to 644. In that case, when lmgrd reads the file it does not attempt to change the permission and starts up as expected.


The operation of license server requires an internet connection between the server computer and the client computer(s). The server must accept incoming connections from the clients on two TCP ports: one for the license manager process lmgrd and one for the vendor daemon process plexim.

3a8082e126
Reply all
Reply to author
Forward
0 new messages