Skip to main content
Solved

Sandbox install no license


I installed in as sandbox environment, all is working but getting ‘unable to validate license’. How do I activate the free 5 node license?

 

Best answer by jaiganeshjk

@kyle.moore Glad that the issue you were facing is sorted out.
Just for adding more information, let me explain the cause of the issue.

There are few problem that will cause the error that you mentioned in the post.

  • Metering-svc pod has some issues and is crashing/restarting/stuck. This pod is responsible for providing an endpoint to validate the license. One reason for the pod to be crashing is if the mode is not set to airgap in offline clusters as rightly mentioned by @JMeixner 

If metering.mode=airgap is not set in an offline cluster, some functionality will be disabled. A message warning that K10 is "Unable to validate license" will be displayed in the web based user interface. Errors containing messages "Could not get google bucket for metrics", "License check failed" and "Unable to validate license" will be logged.

https://docs.kasten.io/latest/install/offline.html
 

  • Other reason could be a network issue for K10 pods to reach metering-svc. Ideally from controllermanager-svc pods. These pods call metering-svc to validate the license.
  • Third one could actually be an expired license.

Let me know if I make sense and mark this as an answer as it could help others in the community.

View original
Did this topic help you find an answer to your question?

13 comments

Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • 602 comments
  • September 6, 2022

hi @kyle.moore 

Hi can you give more information about which product and related licensing?


MicoolPaul
Forum|alt.badge.img+23
  • 2358 comments
  • September 6, 2022

Hi @kyle.moore, which product are you talking about? Assuming you’re referring to Kasten due to 5 node comment. 
 

How did you deploy Kasten? In your own private lab or from a cloud marketplace? Normally you just don’t supply a license for it to be the free/community edition.


  • Author
  • New Here
  • 5 comments
  • September 6, 2022

I am running a sandbox environment on a home base esxi server running virtual machines. I installed k10 on Friday in a Rancher environment. All seemed to install just fine. I am running longhorn as well as backing up to a NFS server running on a VM. I installed by using the K10 helm chart repo within Rancher.


JMeixner
Forum|alt.badge.img+17
  • Veeam Vanguard
  • 2650 comments
  • September 6, 2022

Hello @kyle.moore ,

If metering.mode=airgap is not set in an offline cluster, some functionality will be disabled. A message warning that K10 is "Unable to validate license" will be displayed in the web based user interface. Errors containing messages "Could not get google bucket for metrics", "License check failed" and "Unable to validate license" will be logged.

https://docs.kasten.io/latest/install/offline.html


  • Author
  • New Here
  • 5 comments
  • September 6, 2022

Thank you for the help and I apologize if I wasn’t clear, my sandbox environment has full internet access. For the Free 5 node cluster, will that always be considered an airgap environment?


JMeixner
Forum|alt.badge.img+17
  • Veeam Vanguard
  • 2650 comments
  • September 6, 2022

Ok, I thought your sandbox environment would not have internet access, because of the name 😎

But the offline install is the only scenario I can find for this error message. Perhaps there is a firewall or similar preventing access to the internet for kasten K10?


JMeixner
Forum|alt.badge.img+17
  • Veeam Vanguard
  • 2650 comments
  • September 6, 2022

BTW, there is a group “Kasten K10 Support” here in Veeam Community, designated for Kasten questions.

Perhaps @Madi.Cristil can move this topic to this group. The the kasten experts can answer this question….


  • Author
  • New Here
  • 5 comments
  • September 6, 2022

Not sure that is the case, using Rancher I installed the helm repo for k10 then proceeded with the install pulling the helm charts directly from https://charts.kasten.io. All installed properly, I updated the URL to match a DNS name I gave the dashboard, I am using basic auth with the htpasswd, I am using Longhorn for storage and a local NFS server (running on a VM) for backups. I was able to log into the K10 dashboard just fine, I was able to set up my environment (meaning the disaster recovery, the nfs share under locations, etc). I set up a backup to start running over the weekend but when I came in this morning I am seeing the Unable to validate license error. Possibly just a service that needs to be restarted? Is the 5 Node license the default license if nothing else is entered?


Madi.Cristil
Forum|alt.badge.img+8
  • Community Manager
  • 616 comments
  • September 6, 2022
JMeixner wrote:

BTW, there is a group “Kasten K10 Support” here in Veeam Community, designated for Kasten questions.

Perhaps @Madi.Cristil can move this topic to this group. The the kasten experts can answer this question….

Moving this to Kasten K10 Support. 


  • Author
  • New Here
  • 5 comments
  • September 6, 2022

Thanks you @JMeixner  and @Madi.Cristil 


Geoff Burke
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • 1312 comments
  • September 7, 2022

Go to your settings tab and then check what it says about licensing. Also check your secrets 

kubectl get secrets -n kasten-io 

perhaps the license secret got deleted?


  • Author
  • New Here
  • 5 comments
  • September 7, 2022

turns out I  had a few pods stuck, I terminated them, they respawned and all is good.  Thank you for the quick responses!

 


jaiganeshjk
Forum|alt.badge.img+2
  • Experienced User
  • 274 comments
  • Answer
  • September 7, 2022

@kyle.moore Glad that the issue you were facing is sorted out.
Just for adding more information, let me explain the cause of the issue.

There are few problem that will cause the error that you mentioned in the post.

  • Metering-svc pod has some issues and is crashing/restarting/stuck. This pod is responsible for providing an endpoint to validate the license. One reason for the pod to be crashing is if the mode is not set to airgap in offline clusters as rightly mentioned by @JMeixner 

If metering.mode=airgap is not set in an offline cluster, some functionality will be disabled. A message warning that K10 is "Unable to validate license" will be displayed in the web based user interface. Errors containing messages "Could not get google bucket for metrics", "License check failed" and "Unable to validate license" will be logged.

https://docs.kasten.io/latest/install/offline.html
 

  • Other reason could be a network issue for K10 pods to reach metering-svc. Ideally from controllermanager-svc pods. These pods call metering-svc to validate the license.
  • Third one could actually be an expired license.

Let me know if I make sense and mark this as an answer as it could help others in the community.


Comment