Skip to content

Commit 9a54bc9

Browse files
authored
Merge pull request #96398 from adreed-msft/patch-1
[AzCopyV10] Include edge-cases for exit codes
2 parents 35bd364 + 2de64c5 commit 9a54bc9

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/storage/common/storage-use-azcopy-troubleshoot.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ If the exit code is `1-error`, then examine the log file. Once you understand th
2424

2525
If the exit code is `2-panic`, then check the log file exists. If the file doesn't exist, file a bug or reach out to support.
2626

27+
If the exit code is any other non-zero exit code, it may be an exit code from the system. For example, OOMKilled. Check your operating system documentation for special exit codes.
28+
2729
## 403 errors
2830

2931
It's common to encounter 403 errors. Sometimes they're benign and don't result in failed transfer. For example, in AzCopy logs, you might see that a HEAD request received 403 errors. Those errors appear when AzCopy checks whether a resource is public. In most cases, you can ignore those instances.

0 commit comments

Comments
 (0)