VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hello Thanks for contacting Kasten Support. Could you please provide the results for the command below. kubectl get volumesnapshotclass -A ThanksEmmanuel
Hello Maximn,Thanks for contacting Kasten Support. Could you please provide the debug logs so that we may have a better understanding of your environment. The command is below.curl -s https://docs.kasten.io/tools/k10_debug.sh | bash;ThanksEmmanuel
Hello Anthony, Could you please gather your debug logs, and please look through the logging-svc to narrow down the cause? This could be related to multiple things, and looking for the “cause” in the logs should help narrow down the issue’s.You can now simply access the debug logs from within the support page in K10 UI. ThanksEmmanuel
Hello Anthony, That's great to hear. Doesn't sound like you would need the logs at this point. ThanksEmmanuel
HelloI just want to respond back to the message above, but at this time, K10 does not support Managed Identity in Azure. At this time, we only support Service Principle. This is likely to explain the error above. ThanksEmmanuel
Hello, Could you please provide the results of the commands below. kubectl get sckubectl get volumesnapshotclasskubectl get csidrivers ThanksEmmanuel
Hello ebsglobal,Is this PVC bound to any pods?ThanksEmmanuel
Hello TobiASS, Have you tried other means to access K10 dashboard other than Port Forward? ThanksEmmanuel
Hello TobiAss, Have you tried NodePort? ThanksEmmanuel
Hello, Lemassacre, That's great to hear. With the context deadline error, this would have been an issue within events, possibly an issue with PVC or pods. It's great to hear you have resolved your problem. ThanksEmmanuel
Hello SMT-Almato, Could you please rerun the policy and within the first ten minutes provide the events for kasten-io namespace. kubectl get events -n kasten-io ThanksEmmanuel
Hello Aaron, Could you please provide us your debug logs so that we may further look into your logs. You can find this by going to Settings>Support>Download Logs If you could please attach the executor-svc(all three), and logging-svc log file and lastly the k10_debug we will have a good bases to further troubleshoot. Thanks Emmanuel
Hello SBE, Could you please provide the results of the command below when you are running the snapshot with export.kubectl describe po copy-vol-data-xxxxx -n kasten-ioThere should be a pod that is failing during the exporting. ThanksEmmanuel
Hello @SBEAfter looking over the described above, this looks to be related to a lack of resources available on all of your nodes to start the new copy-vol pod during exporting. You may need to increase resources of the nodes or add a node (or two) based on the node's resources. This may help with understanding K10 requirements. “https://docs.kasten.io/latest/operating/footprint.html#requirement-guidelines” ThanksEmmanuel
Hello @JTI @SBE I am believing the issue is related to your Storage configuration. As you can see above in the PVC describe “waiting for a volume to be created, either by external provisioner "rook-ceph.rbd.csi.ceph.com" or manually created by system administrator" this is a sign that the storage is not able to provision a PV for the PVC. You might want to check events in the kasten-io namespace, to verify on your storage side why the PV are not being created. ThanksEmmanuel
Hello @SBE I am sorry, when looking for events you would have to grab them quickly after doing the failed task. Events only last for 1 hour by default. Also, this looks to be a storage issue if PVC are not able to be created. I would recommend taking a look into the csi-provisioner logs. ThanksEmmanuel
Hello KastenJohn, The way you can resolve this would be to delete the newly created namespace “kasten-io-mc” This will allow you to create a new name for the primary cluster. ThanksEmmanuel
Hello @Geoff Burke, Could you please perform the action that caused the above error and attach your debug logs. We will take a look into the process that is running during the time you are getting the error “Failed to exec command in pod: command terminated with exit code 1 ” ThanksEmmanuel
Hello @Matteo.GazzadiAt this time, we only use the lifetime of the access_token and do not use the lifetime of the refresh_token at the moment. We do have plans in the future to improve the auth-svc to be able to refresh a token before it expires. ThanksEmmanuel
Hello ibrahim, So looking at the above it seems to show that when primer is attempting to run the API’s that the primer is failing to access 10.96.0.1. Could you please let me know what 10.96.0.1 is in your environment. ThanksEmmanuel
Hello Aaron, If you know the date that you did the switch over to the new StorageClass, you could simply retire all snapshots prior to this point. ThanksEmmanuel
Hello ignazioc, If you're, cluster does not have access to your desired object storage. The main thing I could recommend is using a S3 local compatible object storage to create access to an object storage locally(Minio for example) or create a local NFS and use this for an object storage. I would not be able to tell you directly how you should set up your environment to gain network access to S3 bucket. ThanksEmmanuel
Hello ignazioc, If it's S3 compatible, this should be fine. ThanksEmmanuel
Hello Matteo.Gazzadi Could you please provide me your K10 debug logs. This will allow me to look into what Auth-SVC is doing during this error. I want to verify the error you are seeing is directly based around the size of the token.Please follow the below link to gather the logs. https://docs.kasten.io/latest/operating/support.html?highlight=debug%20logs#gathering-debugging-information ThanksEmmanuel
Hello lemassacre, The last error above looks to be related to DNS, so when the blueprint is attempting to run it's trying to find postgres-postgresql.authentication.svc.cluster.local there is no address correlating with this… What installs of PostgreSQL did you use to create the PostgreSQL. ThanksEmmanuel
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
