Open adam-ah opened 2 years ago
SSL errors always boil down to a connectivity or firewall issue on your machine or network. Make sure you have reliable connectivity and that no firewall on your machine or network is blocking GYB then try again.
@jay0lee, uploading messages may take several hours to days and network errors can and do occur. In fact, network errors are the norm, not the exception when performing long operations.
It is not unreasonable for gyb, similarly to most apps performing long network operations, to implement automatic retry if the error did not occur on the very first attempt (i.e., when the error occurs after a successful start).
I cannot think of any apps that has the ability to resume (just like gyb resumes when manually restarted), but crash rather than implement automatic retries on long network operations - can you?
Can this please be addressed? We are archiving a large number of mailboxes and they cannot complete them.
PRs are welcome.
I just posted to the Google Group about this same issue. I really hope this can be addressed somehow. Don't have any programming skills, but happy to donate!
It looks like there is some retry mechanism in the function in question (https://github.com/GAM-team/got-your-back/blob/main/gyb.py#L754) -- I guess that might help a bit and this issue might no longer be relevant?
Please confirm the following:
I have upgraded to the latest GYB release from https://github.com/jay0lee/got-your-back/releases and I still have this issue. Yes.
I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/got-your-back/wiki Yes.
Full steps to reproduce the issue: I don't have a specific easy-to-reproduce and isolated bug. Hopefully a more robust exception handling / retry mechanism around the problem below would solve it.
Steps I took:
Expected outcome (what are you trying to do?): As above - restoring local backup to a new address
Actual outcome (what errors or bad behavior do you see instead?): As above - unhandled exception, gyb quit.