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

Error while copying data from ADLS to ADLS in azure #2546

Closed
sarav-ks opened this issue Jan 19, 2024 · 6 comments
Closed

Error while copying data from ADLS to ADLS in azure #2546

sarav-ks opened this issue Jan 19, 2024 · 6 comments

Comments

@sarav-ks
Copy link

sarav-ks commented Jan 19, 2024

Which version of the AzCopy was used?

2024/01/19 22:47:47 AzcopyVersion 10.22.2

Note: The version is visible when running AzCopy without any argument

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

2024/01/19 22:47:47 OS-Environment linux
2024/01/19 22:47:47 OS-Architecture amd64

What command did you run?

azcopy copy https://sasdlc1zaksxxxxx02.blob.core.windows.net/udaip-sre-adls https://sasdlc1zaksxxxxx01.blob.core.windows.net/udaip-sre-adls-backup/2024-01-19-full --overwrite=false --as-subdir=false --recursive=true --preserve-owner --preserve-permissions

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.

What problem was encountered?

Even though the data got successfully copied , overall job failed with the below error

2024/01/19 22:47:48 ERR: [P#0-T#5] COPYFAILED: (folder properties) https://sasdlc1zaks0xxxxx02.blob.core.windows.net/udaip-sre-adls : 000 : Invalid Service Client. Expecting Datalake Service client. When Grabbing source ACLs. X-Ms-Request-Id:

How can we reproduce the problem in the simplest way?

Try the above command with AZCOPY_AUTO_LOGIN_TYPE=SPN

Have you found a mitigation/solution?

None

@gapra-msft
Copy link
Member

Hi @sarav-ks Thank you for reporting this issue.

Could you try using the .dfs endpoint instead of the .blob endpoint? This should temporarily mitigate the problem.

I believe this PR should resolve this issue. @adreed-msft can you confirm?

@sarav-ks
Copy link
Author

Thanks for the reply . When i changed the endpoints to .dfs , my azcopy commands got stuck ..

Then i tried to a quick 'curl' check ,
curl -v https://sasdlc1zaks01xxxxx02.dfs.core.windows.net

and got the below error

{"error":{"code":"InvalidUri","message":"The request URI is invalid.\nRequestId:ea40e1f5-301f-005a-8047-4bcd8a000000\nTime:2024-01-20T02:20:18.3004496Z"}}

Is there any issue with my URL ?

@sarav-ks
Copy link
Author

when i try
curl -v https://sasdlc1zaks01xxxxx02.blob.core.windows.net

got a reasonable response

InvalidQueryParameterValueValue for one of the query parameters specified in the request URI is invalid. RequestId:3b4dbb42-a01e-000f-7049-4b29b3000000

@sarav-ks
Copy link
Author

sarav-ks commented Jan 20, 2024

Do i have to do anything specific on the storage account to enable the '.dfs' endpoint ?

I verified that the storage account has 'HNS enabled' , also i can see the '.dfs' URI listed on the 'Endpoints' blade of the storage account in azure portal

@gapra-msft
Copy link
Member

There is nothing you need to do to enable the .dfs endpoint, it should be supported if HNS is enabled. Could you share a screenshot of the account setting that states there is HNS enabled?

If your command got stuck, could you share the azcopy logs during the stuck state?

@gapra-msft
Copy link
Member

Closing due to inactivity from customer end. Please reopen with the requested details once available.

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

No branches or pull requests

2 participants