doh-stub mode Runtime error
Closed this issue · 7 comments
Hello, I observed the log. Occasionally, after a few days of running, there will be such a warning, and the connection will be cut off.
<<ERROR: Fatal read error on socket transport>>
Query the next google, most people say it is a problem with python itself.
What do you think?
I hope you can check this question, thank you!
Two more log records appeared after the next clock. The first one was recurring, and the second one was seen for the first time.
(1)WARNING: Remote peer sent GOAWAY [ERR: ErrorCodes.NO_ERROR], disconnect now.
(2)ERROR: Task was destroyed but it is pending!
I hope to get your reference.
Thank you for checking my information.
The connection really broke for about two minutes.
Is this an accidental running error in the program, or is it caused by the Internet vendor's tentative blocking port behavior?
I mean the error that is read will affect the work.
Hi @WakamizuLee
I am not sure which of those error is causing actual operational issues. The GOAWAY should be totally fine, this is the remove server that tells us that the connection is going down. I don't think the "Task was destroyed but it is pending" is an issue either.
ERROR: Fatal read error on socket transport
I am less sure about this one.
So, can you please clarify which error/warning exactly is an actual issue. And can you provide more context around the logs, just the error message on itself is going to be hard to narrow down where this is coming from.
Also, just to set the expectation right, this is an experimental repository, I will try to look into it as time permits, but unless I have a good way to reproduce the issue, it will be harder to get it fixed.
Ok, thank you for your review and recovery. I will observe it for a while. There are not too many error logs to refer to.
If there is new progress, I will contact you again.Thank you!
@WakamizuLee I am going to close this issue. If you have more detail, please open a new issue.