Summary
How do the lmgrd and lmdown processes work to start and stop vendors on Windows?
Question
It appears that our license server has an lmgrd process for each vendor daemon. We have our XXX vendor and there's a second YYY vendor. The Windows Task Manager shows 2 lmgrd processes running. When we attempt an lmdown process, it's killing both those lmgrd processes. How do we go about just shutting down our lmgrd and vendor so we only stop the stuff we started with our license server without interrupting the other one?
Answer
There's some confusion here regarding how it works. Please note, there is *NOT* 1 lmgrd process per vendor daemon (see KB 000027955). On running 'lmgrd' as service, two 'lmgrd' processes can be seen in Task Manager. One of which represents the 'lmgrd' service and the other represents the 'lmgrd' process created by the service.
If lmgrd is not installed as a service, only 1 lmgrd process will be observed in the Task Manager on Windows, and that single (1) license manager (lmgrd) process runs/manages all vendor daemons on the system in question.
Additional Information
The 'lmdown' utility can be used to shut-down either 'lmgrd' (which in-turn shuts-down the vendor daemon/daemons) or only 'vendor daemon' (lmgrd continues running).
The point here is that without the use of '-vendor', the 'lmdown' request is sent to 'lmgrd' (irrespective of whichever vendor daemon is running).
So 'lmdown' switches need to be carefully used.
For Ex:
1. To shutdown a specific 'lmgrd':
$lmdown -c <lmgrd port>@<lmgrd server ip address/hostname>
or
Use specific port for each 'lmgrd' by mentioning in the license file and use that license file in 'lmdown'.
SERVER this_host 27010 ANY
2. To shutdown a specific 'vendor daemon':
$lmdown -c <vendor license file> -vendor <vendor name>Related Articles
From v11.11.1, the service-startup type for lmgrd is set to Automatic (Delayed Start) in the Windows Services Manager. 3Number of Views Unable to stop FNMEA services in the Windows Services 12Number of Views Reasons for lmgrd Service not Getting Started 25Number of Views What is the difference between Automatic VS Automatic (Delayed Start) for Windows Services? 9Number of Views EXITING DUE TO SIGNAL 32 Exit Reason 9 10Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago