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

custom upload failing with error="can't resume for remote_storage: custom" #1040

Open
mithunnutanix opened this issue Nov 4, 2024 · 6 comments

Comments

@mithunnutanix
Copy link

I am using the following custom upload script

#!/usr/bin/env bash
echo "Moving clickhouse backup to remote"
BACKUP_NAME=$1
echo "Backup name: $BACKUP_NAME"
cp -r /var/lib/clickhouse/backup/${BACKUP_NAME} /var/nfs
echo "Backup moved to /var/nfs"

And the upload script is failing with this error

cmd/clickhouse-backup/main.go:658 > error="can't resume for remote_storage: custom"

When i checked the code, there is a verification

if b.cfg.General.RemoteStorage == "custom" && b.resume {
	return fmt.Errorf("can't resume for `remote_storage: custom`")
}

can you share some insights on what is b.resum param. And how can we disable it when it is custom upload

@mithunnutanix
Copy link
Author

setting USE_RESUMABLE_STATE=false resolved the issue

1 similar comment
@mithunnutanix
Copy link
Author

setting USE_RESUMABLE_STATE=false resolved the issue

@Slach
Copy link
Collaborator

Slach commented Nov 4, 2024

yes, modification of config also works

general:
  use_resumable_state: false

@mithunnutanix
Copy link
Author

mithunnutanix commented Nov 4, 2024

@Slach can this be added to the documentation for custom option. Or the error output can be modified to suggest changing the parameter

@Slach
Copy link
Collaborator

Slach commented Nov 4, 2024

@mithunnutanix feel free to make PR

@Slach Slach reopened this Nov 4, 2024
@Slach
Copy link
Collaborator

Slach commented Nov 4, 2024

Slach added a commit that referenced this issue Nov 14, 2024
Modified the ReadMe and Error message for custom remote option. Closed issue #1040
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants