Skip to main content

reviving database error

  • November 3, 2017
  • 4 replies
  • 13 views

colin_loghin
Forum|alt.badge.img+2

Not sure why the revive operation fails.
The json file referenced seems present and accessible. Ideas?

aws s3 cp s3://eonpoc2/communal/metadata/VerticaDB/cluster_config.json -

[dbadmin@ip-172-31-46-62 ~]$ admintools -t revive_db --communal-storage-location=s3://eonpoc2/communal/ -s 172.31.46.62 --force -d VerticaDB

            Vertica Eon Mode Beta
    The operation you are performing is part of
    beta functionality. The terms listed in the beta
    agreement apply.

    Vertica Eon Mode Beta forum:
    https://forum.vertica.com/categories/verticabeta

Attempting to read database information from: [s3://eonpoc2/communal/metadata/VerticaDB/cluster_config.json]

Database could not be revived.
Error: Error while downloading file communal/metadata/VerticaDB/cluster_config.json from communal location: An error occurred (400) when calling the HeadObject operation: Bad Request

4 replies

Ben_Vandiver
Forum|alt.badge.img
  • Participating Frequently
  • November 6, 2017

Keys? Region issues?


asaeidi
Forum|alt.badge.img
  • Participating Frequently
  • November 7, 2017

Could you please provide the log file (vertica-download-file.log)?


skeswani
Forum|alt.badge.img
  • Participating Frequently
  • November 7, 2017

revive_db assumes us-east-1, which seem to be the problem. I have provided a workaround, lets see if it works


skeswani
Forum|alt.badge.img
  • Participating Frequently
  • November 7, 2017

try, in bootstrap_catalog.py
in _process_args(…)
add flags_list.extend([‘-X’, ‘pName:pValue’])
AWSRegion:us-xxxx-y