# Issues While Updating License File

This page addresses common issues faced while updating the license.lic file in different environments.

# Baremetal / VM Machines

# 1) I replaced the `license.lic` file, but the application still shows the old license. Why?

After replacing the license.lic file, you need to restart the yCrash server application for the new license to take effect.

# 2) Does the license file need to follow a specific name?

Yes. The file must be named license.lic. Any other filename (e.g., license-1.lic , license.txt or license) will not be recognized.

# 3) Why do I get errors when using the updated license file on Linux?

Sometimes the license.lic file may have DOS line endings (Windows format) instead of Linux format.

# Convert it to Linux format using dos2unix command
dos2unix license.lic

1
2

# 4) I uploaded the new license, but the system still shows it as expired. What’s wrong?

In many cases, the old license file is still being used instead of the renewed one. Double-check that you replaced it with the latest license file provided.

# 5) The license is still invalid after replacement when using remote storage (S3/GCS/Network Drive). Why?

If your license.lic is stored in remote storage (e.g., S3, GCS, or NFS), updating the file locally will not update it on the remote path. Ensure that the license file is updated in the remote storage location used by the application.

# Kubernetes / OpenShift / Docker / Podman

# 1) I updated the license in the secret YAML, but the application fails to read it. Why?

When updating the license.lic content in a Kubernetes Secret or YAML configuration, be careful with:

Indentation (extra spaces at the beginning of lines)
Special characters (such as quotes, tabs, or hidden characters)
Extra whitespace

Minor formatting mistakes in the YAML can cause the license to be unreadable. Here’s a sample skeleton structure of the YAML file.

apiVersion: v1
kind: Secret
metadata:
  name: ycrash-server-license
  namespace: yc-apps
stringData:
  license.lic: |
    Licensor=**********************
    Licensee=**********************
    UserNo=************************
    IPAddress=*********************
    Feature_1=*********************
    Feature_2=*********************
    Expiration=********************
    Signature=*********************

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

# Troubleshooting Commands

# Verify license file inside a Docker container

# Check if license.lic exists inside a running container
docker exec -it <container-id> ls -l /opt/workspace/yc/uploads/license.lic

# View contents of license.lic inside container
docker exec -it <container-id> cat /opt/workspace/yc/uploads/license.lic

1
2
3
4
5

# Verify license file inside a Kubernetes Pod

# Check if license.lic is mounted properly
kubectl exec -it <pod-name> -- ls -l /opt/workspace/yc/uploads/license.lic

# View contents of license.lic
kubectl exec -it <pod-name> -- cat /opt/workspace/yc/uploads/license.lic