Skip to main content

Hello,

Now I have problems with the dr backup policy. 
I am exporting data to an s3, all policies and dr policy are exported in the same s3.
But only the dr backup policy isn’t working.
The s3 has object lock disable

 

 Failed while waiting for actionSet
ActionSet Failed
{"message":"Failed to stream backup to remote kopia repository on Kopia API server","function":"kasten.io/k10/kio/kanister/function.moverBackupToServer","linenumber":243,"file":"kasten.io/k10/kio/kanister/function/mover_backup_to_server.go:243","cause":{"message":"Failed to exec command in pod","function":"github.com/kanisterio/kanister/pkg/kube.ExecWithOptions","linenumber":156,"file":"github.com/kanisterio/kanister@v0.0.0-20240627181416-b9b522b6fa79/pkg/kube/exec.go","cause":{"message":"command terminated with exit code 1.\nstdout: Snapshotting k10-admin@ff66c2ab-b5a4-4a6d-83f6-b2fa4904e0b5.catalog-svc.catalog-pv-claim:/mnt/k10state ...\r\nCreated snapshot with root k13b616c98feb759f3e21d02ea6242990 and ID 2af31c675935e61b2a7bcbe3eb38a0b0 in 30s\nstderr: kando stream push \u003csource\u003e 0flags]\r\nFlags:\r\n-d, --dirPath string Specify a root directory path for the data stream (required)\r\n-f, --filePath string Specify a file name or path for the data stream (required)\r\n-h, --help help for push\r\nGlobal Flags:\r\n-c, --config-file string Custom config file for object storage repository configuration\r\n-p, --password string Specify the password for object storage repository (required)\r\n-v, --verbosity string Log level (debug, info, warn, error, fatal, panic) (default \"warning\")\r\n{\"File\":\"kando/main.go\",\"Function\":\"main.main\",\"Line\":22,\"error\":\"Failed to create kopia snapshot: Get \\\"http://10.35.169.66:8000/v0/backup\\\": dial tcp 10.35.169.66:8000: i/o timeout\",\"hostname\":\"catalog-svc-6c4669ffdc-chb2f\",\"level\":\"info\",\"msg\":\"Kando failed to execute\",\"time\":\"2024-07-04T07:01:10.017997465Z\"}"}}}

Thank you in advance

Hello @alexiiii,

 

Would you know who this IP address belongs to. 10.35.169.66.

 

Thanks

Emmanuel


Hi,

This IP belong to the catalog-svc

Regards


And this problem only append on this kubernetes cluster. If I create another one, it work perfectly 


Hello @alexiiii,

 

Yes it looks like Catalog was unable to be accessed. Can you verify Catalog logs shows that the pod is in a running state. Also are there any Network Policies in the namespace. 

 

Thanks

Emmanuel


Comment