Hi @Mohamed999 RHEL 8 support was added since 11.16.4 and a higher version of FNP.
So the less version should be upgraded to any latest version of FNP to run on RHEL 8.
-> FNP services need to be installed and then running the server with the same binaries would work.
Best Regards,
... View more
Hi @rvalcla Yes, you can use lmreread to re-validate the license rights however it's up to the Flexnet owner to give access rights or not based on the requirement and it's not mandatory.
Best Regards,
... View more
Hi @DeepakKokate can you please make sure the LM_LICENSE_FILE is set correctly? Also please check the registry entry if any and remove it or update correctly and then check.
are you using lmtools?
Best Regards,
... View more
Introduction
Secure communication failed with error Ecomms: Startup failed, res=-279 when using the default builds for fnpssl static version, how to fix it?
Instructions
With ls_secure_comms = 1; in vendor c file and using the default builds if getting the below error in the daemon logs 18:14:03 (demo) Ecomms: Starting 18:14:03 (demo) Ecomms: SSL/TLS initialization failed 18:14:03 (demo) Ecomms: Startup failed, res=-279 18:14:03 (demo) Ecomms: Disabled 18:14:03 (demo) Changing message security level from -1 to 0 If getting SSL/TLS initialization failed then as per the documentation
-279 LM_ECOMMS_ERROR “the libfnpssl shared library is not available in the current working directory”
The library is not available to enable secure communication.
Find the error code documented already.
More Information
Find more information at FlexNet Publisher 2024 R1 (11.19.6) Programming Reference for License File–Based Licensing page number 107
... View more
Hi @avgera somehow we missed this post, however thanks for the support case 02844260, as of now there is no REST API to import and replace the file in the server.
Best Regards,
... View more
Hi @MikeSpragg can you please raise a support case, and share all these details, this needs further investigation to answer more.
Best Regards,
... View more
Hi @MikeSpragg Understand that, however, we had this issue in the past where the same feature was added in many license files with the FEATURE keyword which is why this issue was reported. So, if you check the server and see the server is using more than one license file? if yes then check how many times the feature was added with FEATURE line?
Best Regards,
... View more
Hi @npenneti This is possible using TIMEOUT in the options file,
TIMEOUT is enabled in the options file of the License Server
lc_idle() is set to true by the client app. So it stops sending the heartbeats to the Server (I am using Automatic Heartbeat)
Due to this, the license is reclaimed by the License Server once the TIMEOUT is reached
After reclaimed, how to handle the application on the client side is up to the developer joice.
Best Regards,
... View more
Hi @MikeSpragg The problem was the feature was added as FEATURE line
FEATURE SI9000e POLAR 0200240306 30-oct-2024 1 \ VENDOR_STRING=MaxVer=24;Polarcare=Yes;PCN=PINC9222 \ HOSTID="a4bb6d66dff9 ac82473b6ee2"
I am not sure how many license files are on this server however can you update the FEATURE line to the INCREMENT line and give it a try.
Best Regards,
... View more
Hi @nityapraveen
If you want to check the overall status of the CLS module, whether it is reachable, and the build version you might want to use the GET on "https://flexXXXX.compliance.flexnetoperations.com/GlobalLicensingService/api/1.0/health". If you want the same information about the build from individual CLS instances, you can use "https://flexXXXX.compliance.flexnetoperations.com/api/1.0/instances/<CLS_ID>/health". Having the above said, if you want to confirm whether a CLS instance is ready to serve license, you can fire the URL " https://flexXXXX.compliance.flexnetoperations.com/api/1.0/instances/<CLS_ID>". But this endpoint will work with the Bearer token which you will get from the endpoint ""https://flexXXXX.compliance.flexnetoperations.com/api/1.0/instances/<CLS_ID>/authorize"
You can do the get call on the same endpoints from your code to get the health status of the CLS.
There is no specific API from SDK side to check for CLS health as CLS health endpoints are different.
Best Regards,
... View more
Hi @nityapraveen As of now LLS support primary and secondary server mechanisms for failover with quite a few limitations. However, there is a plan for High Availability LLS (configured as a cluster with a load balancer in front) and this is in the Road map item of FNE.
Best Regards,
... View more
