-
Notifications
You must be signed in to change notification settings - Fork 561
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
TCP error 104 #777
Comments
Hi, you'd need to post your API calls, etc as requested in the issue template. Thanks! |
Done. Sorry ;-) |
Still any idea of the problem ? |
You really need to post all docker and API calls, output logs, etc... so someone can try to reproduce to help you. Otherwise if you put yourself in our seat, it is difficult to understand what you are doing here. So it works on your laptop, but doesn't elsewhere ? Have you checked you have the same memory etc... |
Hi,
Problem description
I have a DD instance running on Debian with docker (CPU only), but when calling the "predict" endpoint I receive a TCP error code 104 ( Connection reset by peer).
I test on my local machine and it seems to work !
Here is the request on the predict API
Observations
Even in the worst case, I should receive an error... the DD server should not close the connection, right ?
I checked the logs and sometimes I got this, without any additional info:
l5sm0 [2020-08-25 16:54:50.150] [api] [error] 10.0.4.219 "POST /services/imageserv" 500 2
Notices
Error 104 :
This can happen if the other side crashes and then comes back up or if it calls close() on the socket while there is data from you in transit, and is an indication to you that some of the data that you previously sent may not have been received.
The text was updated successfully, but these errors were encountered: