Reasons for common errors during enabling replication

Introduction

In this document we will aim to capture reasons for common errors observed during enabling of Replication. Please note this list is by no means exhaustive and is a living document and is bound to updated.

1.  Error - error response unwrapping secondary token; status code is 400, message is "400 Bad              Request" -

    Reason - This is because the secondary activation token is expired. We should generate a new              secondary activation token as they're essentially one-time use. So we can regenerate the new              token  using this guide

2. Error - error response unwrapping secondary token; status code is 500, message is "500 Internal        Server Error" -

    Reason - This is when the secondary activation token is invalid or malformed. Check if the token            copied is incorrect

3.  Error - error unwrapping secondary token: Post "http://127.0.12.3:8200/v1/sys/wrapping/unwrap":         dial tcp  127.0.12.3:8200: i/o timeout -

      Reason - When the primary_api_addr is not reachable.

Additional Information

• Monitoring Vault Replication 

• Generate a secondary token.
• DR Operation Token Strategy