Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

br failed to backup #46

Open
kikimo opened this issue Jul 7, 2022 · 0 comments
Open

br failed to backup #46

kikimo opened this issue Jul 7, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@kikimo
Copy link

kikimo commented Jul 7, 2022

br failed to backup and report error as below:

      --debug                  Output log in debug level or not
      --log string             Specify br detail log path (default "br.log")
      --meta string            Specify meta server
      --s3.access_key string   S3 Option: set access key id
      --s3.endpoint string     S3 Option: set the S3 endpoint URL, please specify the http or https scheme explicitly
      --s3.region string       S3 Option: set region or location to upload or download backup
      --s3.secret_key string   S3 Option: set secret key for access id
      --spaces stringArray     (EXPERIMENTAL)space names.
                                   By this option, user can specify which spaces to backup. Now this feature is still experimental.
                                   If not specified, will backup all spaces.
                                   
      --storage string         backup target url, format: <SCHEME>://<PATH>.
                                   <SCHEME>: a string indicating which backend type. optional: local, s3.
                                   now only s3-compatible is supported.
                                   example:
                                   for local - "local:///the/local/path/to/backup"                                   for s3  - "s3://example/url/to/the/backup"
{"file":"./main.go:17","func":"main.main","level":"fatal","msg":"write meta to tmp path failed: open file /tmp/nebula-br/BACKUP_2022_07_07_14_22_24.meta failed: open /tmp/nebula-br/BACKUP_2022_07_07_14_22_24.meta: no such file or directory","time":"2022-07-07T14:25:57.630Z"}
Traceback (most recent call last):
  File "br_all.py", line 421, in new_run
    do_new_run(session)
  File "br_all.py", line 314, in do_new_run
    must_run_script('br-cli-remote-inc-backup.sh',
  File "br_all.py", line 236, in must_run_script
    subprocess.run([full_scripts, *params], check=True)
  File "/usr/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/nebula-cases/nebula-chaos-cluster/scripts/br-cli-remote-inc-backup.sh', 'BACKUP_2022_07_07_14_21_02\n', 'test', 'runtest-d45867f6f-4lqsx']' returned non-zero exit status 1.
root@runtest-d45867f6f-4lqsx:/nebula-cases/nebula-chaos-cluster/scripts# 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants