Sheng Cheng

@[giom-l](https://github.com/giom-l) Same here. Even I upgraded to 0.12.1 version. It seems like happen randomly to me. Have you tried that we erase the content of ~/.aws/config before Medusa run the...

We encountered this issue, too. Here is our goal below Cluster restore for 6 nodes (3 x seed nodes and 3 s non-seed nodes) from S3 via Medusa. Here is...

The same issue during the cluster-restore, only seed nodes (cass-01/02/03) were brought up but others were not. Finally, STDOUT is ERROR: Some nodes failed to restore. Exiting More details below...

Alexander, >A question though: is the native port (9042 by default) accessible between nodes? Medusa will check if the port is opened to ensure the node have restarted. (Sheng 03/19):...

> The same issue during the cluster-restore, only seed nodes (cass-01/02/03) were brought up but others were not. Finally, STDOUT is ERROR: Some nodes failed to restore. Exiting > >...

Looks like Medusa 0.13.4 is yet to resolve this duplicate issue. Short term solution is to wipe out all content of .aws/config for Medusa. -Sheng

Hi, All nodes includes seed nodes. -Sheng On Wed, Aug 30, 2023 at 11:03 nguyenthai0107 ***@***.***> wrote: > Hello @m934030039 > Have a nice day. > Just a question for...

Same symptom here and same actions we took but it always failed for all nodes. We are using awscli 1.19.x version and Medusa 0.13.4 version. -Sheng