Upload to BOX fails with '502 Bad Gateway' after random amount of time

Help and Support
21

Yes, they did escalate again.

The transfer of 400GB usually takes 1-2 hours.
This transfer of 14GB has been running for 3 hours and has only transferred 6GB.

I don't believe that rclone is responsible for this delay or these problems. I am also seeing this behavior from different geographic locations within our network.

2022/11/02 09:38:45 DEBUG : pacer: Reducing sleep to 60ms
2022/11/02 09:44:24 DEBUG : pacer: low level retry 2/3 (error Error "502 Bad Gateway" (502))
2022/11/02 09:44:24 DEBUG : pacer: Rate limited, increasing sleep to 120ms
2022/11/02 09:44:24 DEBUG : pacer: low level retry 2/3 (error Error "502 Bad Gateway" (502))
2022/11/02 09:44:24 DEBUG : pacer: Rate limited, increasing sleep to 240ms
2022/11/02 09:45:30 DEBUG : pacer: low level retry 3/3 (error Error "502 Bad Gateway" (502))
2022/11/02 09:45:30 DEBUG : pacer: Rate limited, increasing sleep to 480ms
2022/11/02 09:45:30 DEBUG : pacer: low level retry 3/3 (error Error "502 Bad Gateway" (502))
2022/11/02 09:45:30 DEBUG : pacer: Rate limited, increasing sleep to 960ms
2022/11/02 09:50:00 DEBUG : pacer: Reducing sleep to 720ms
2022/11/02 09:57:30 DEBUG : pacer: Reducing sleep to 540ms
2022/11/02 10:00:19 DEBUG : pacer: Reducing sleep to 405ms
2022/11/02 10:00:19 DEBUG : pacer: Reducing sleep to 303.75ms
2022/11/02 10:00:19 DEBUG : pacer: Reducing sleep to 227.8125ms
2022/11/02 10:00:20 DEBUG : pacer: Reducing sleep to 170.859375ms
2022/11/02 10:00:26 DEBUG : pacer: Reducing sleep to 128.144531ms
2022/11/02 10:00:30 DEBUG : pacer: Reducing sleep to 96.108398ms
2022/11/02 10:00:30 DEBUG : pacer: Reducing sleep to 72.081298ms
2022/11/02 10:00:32 DEBUG : pacer: Reducing sleep to 54.060973ms
2022/11/02 10:00:34 DEBUG : pacer: Reducing sleep to 40.545729ms
2022/11/02 10:11:04 DEBUG : pacer: Reducing sleep to 30.409296ms
2022/11/02 10:11:04 DEBUG : pacer: Reducing sleep to 22.806972ms
2022/11/02 10:11:04 DEBUG : pacer: Reducing sleep to 17.105229ms
2022/11/02 10:12:21 DEBUG : pacer: Reducing sleep to 12.828921ms
2022/11/02 10:17:47 DEBUG : pacer: low level retry 1/3 (error Error "502 Bad Gateway" (502))
2022/11/02 10:17:47 DEBUG : pacer: Rate limited, increasing sleep to 25.657842ms
2022/11/02 10:17:47 DEBUG : pacer: low level retry 1/3 (error Error "502 Bad Gateway" (502))
2022/11/02 10:17:47 DEBUG : pacer: Rate limited, increasing sleep to 51.315684ms
2022/11/02 10:17:47 DEBUG : pacer: low level retry 1/3 (error Error "502 Bad Gateway" (502))
2022/11/02 10:17:47 DEBUG : pacer: Rate limited, increasing sleep to 102.631368ms
22

OK, perhaps the best strategy might be to stop it until things improve, this may also help Box getting back on their feet.

Thanks, good to know.

23

Also confirmed, this is happening in different geo-locations.

24

FWIW, I was able to get a root cause from BOX

**Root Cause of the Issue** : Between October 27, 2022 at 1:30 PM PDT and November 3, 2022 at 11:43 AM PDT, some
users may have experienced difficulties while working in Box. During this time, upload and download throughput during
peak usage periods was reduced by as much as 30%. The issue occurred following consolidation of uploads and
downloads traffic beyond the infrastructure capacity available. We were able to resolve the issue by adding infrastructure
capacity. In addition, we are improving our monitoring to detect the new constraint to prevent similar issues from occurring
in the future.
2 Likes
25

Great - well done @emboehm - I'll mark that as the solution.

26

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.