- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- Re: Problem with adding new license file to three-server redundancy (FlexNet license cluster)
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Problem with adding new license file to three-server redundancy (FlexNet license cluster)
Hello,
After I add new license file to the FlexNet license cluster through its admin panel, new licenses only become available to our software after I restart lmadmin service on node Vendor Daemon (Stop | Start and Reread license file actions) do not help.
We expect that it should not be necessary to restart lmadmin service and newly added license should immediately become available.
Why is that necessary?
Cordially
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi, @jcduprey Let me know what are all the changes in the new license file? Ideally, reread should if not then we need to investigate more to find the issue.
Best Regards,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi, changing an existing license file works when we reread it, but if we add a new license file, then we need to restart lmadmin.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
ok understood, the question was why is that necessary?
The problem for us is that the restart makes unavailable the license checking for all the other applications during the time of the restart and yes this is a problem...
No way to take it into account by a simple reread?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
@jcduprey If the license file is new then the server has to re-read the full file from the server line to Increment lines and that needs a restart to use the current config of lmgrd and VD unlike the old file has only updates then license re-read only read the license details.
Better to get downtime and restart will resolve this issue.
Best Regards,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
@jcduprey - You shall be good with a simple Server reread on all 3 instances of the triad. Given that you are updating the contents of the existing license file - even if it's a complete over-write.
So, the daemon will be unable to serve the licenses for a few seconds while rereading and rebuilding the feature configuration list.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Thanks for your replies.
So you confirmed that a restart is required in case of usage of several license files, where a simple reread should be enough with a single license file - correct?
and in our case, we prefer having several license files to manage all our products and customers because this is safer and more convenient as well.
We don't have much options then... Are we the only one to have this problem?