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

All commands (including azcopy --version) takes ~8 seconds #2482

Closed
carlsmedstad opened this issue Dec 7, 2023 · 3 comments · Fixed by #2498
Closed

All commands (including azcopy --version) takes ~8 seconds #2482

carlsmedstad opened this issue Dec 7, 2023 · 3 comments · Fixed by #2498

Comments

@carlsmedstad
Copy link

Which version of the AzCopy was used?

Note: The version is visible when running AzCopy without any argument
$ azcopy --version
azcopy version 10.22.0

Which platform are you using? (ex: Windows, Mac, Linux)

Arch Linux.

What command did you run?

Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
$ time azcopy --version
azcopy version 10.22.0
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xc6a2a3]

goroutine 1 [running]:
github.com/Azure/azure-storage-azcopy/v10/common.(*lifecycleMgr).Exit(0xc0001dca20, 0x0?, 0x0)
	github.com/Azure/azure-storage-azcopy/v10/common/lifecyleMgr.go:375 +0xc3
github.com/Azure/azure-storage-azcopy/v10/cmd.Execute({0xc0000e8a08?, 0x18b91b0?}, {0xc0000eb4c0?, 0x10c1337?}, 0x74?, {0x638f2c95, 0x1d76, 0xea43, {0x6e, 0x56, ...}})
	github.com/Azure/azure-storage-azcopy/v10/cmd/root.go:214 +0x17f
main.main()
	github.com/Azure/azure-storage-azcopy/v10/main.go:84 +0x4fa

real	0m8.032s
user	0m0.233s
sys	0m0.247s

What problem was encountered?

There seems to be some kind of deadlock. Every command takes ~8 seconds. Also the stack trace.

See the attached strace.log.

How can we reproduce the problem in the simplest way?

Unsure.

Have you found a mitigation/solution?

Unfortunately, no.

@carlsmedstad
Copy link
Author

The issue seems to be in the version check. Running the following is near-instant:

$ time azcopy --skip-version-check --version
azcopy version 10.22.0

real	0m0.017s
user	0m0.010s
sys	0m0.007s

archlinux-github pushed a commit to archlinux/aur that referenced this issue Dec 7, 2023
Also, apply patches for the following issues in 10.22.0:

* Azure/azure-storage-azcopy#2483
* Azure/azure-storage-azcopy#2482

The second one by removing the version check entirely - I doubt many
Arch Linux users are interested in such a feature, especially if it adds
8 seconds to every invocation.
@siminsavani-msft
Copy link
Contributor

Hi there! Thank you for bringing up this issue. I was able to repro this, and we are working on a fix. In the meantime, please use --skip-version-check to minimize the 8 second lag.

@gapra-msft
Copy link
Member

Hi! This has been fixed in our latest release. Please feel free to open a new issue in case you hit any other issues with AzCopy!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants