LCS Grace Period in a Containerized Environment
Written By
Madeleine Clay
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- Once my LCS subscription expired, my containerized environment was disconnected immediately instead of entering the LCS grace period.
Environment
- Portal 6.2
- DXP 7.0
- DXP 7.1
- DXP 7.2
- DXP 7.3
Resolution
-
Because containerized environments destroy the existing server and spin up a new one every time they restart, LCS recognizes it as a new instance after a restart and no longer recognizes that the server is in its grace period.
-
To resolve this, the
lcsServerId file, located in the data/license/server folder, should be maintained permanently in the container images.
- The
lcsServerId file in the data/license/server folder contains the server's unique identifier and the time of the last LCS connection, so maintaining it will ensure that the LCS grace period is recognized.
- The
lcsServerId file can be copied over to a new instance, but to only one active instance (multiple instances cannot connect with the same ID at the same time, and multiple lcsServerId files cannot be concurrently present in a bundle). As such, this resolution cannot be used for environments using both LCS and clustering.
Did this article resolve your issue ?