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
Error 10054 [CORE6210] #6455
Comments
Commented by: @cincuranet This error code means WSAECONNRESET. Which happens when the connection is terminated from the client/other side without doing proper closing sequence. That probably mean your application ended unexpectedly or similar stuff. |
Commented by: Ivan Diez (ivandiez) is there a way we can do anything to solve it? keepalive parameter? or do we need to contact the software provider? |
Commented by: @mrotteveel The problem can only be fixed by the client application closing the connection correctly (assuming the problem is not in a connection library not closing the connection properly). In any case, error 10054 (connection reset by peer) is generally not a severe error, so if the only problem you have is that this error is logged, you could just ignore it, although it would be better of course if the client correctly closes the connection. |
Commented by: @livius2 Two things: |
Commented by: Sean Leyne (seanleyne) This is a support issue, this is not a support forum. Please post to the Firebird Support mailing list. |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] |
Commented by: Ivan Diez (ivandiez) ok. Sorry for the inconveniences |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Ivan Diez (ivandiez)
Good morning,
we have an issue with our firebird database. We are getting continuosly an error in the firebird.log file. We have a line "INET/inet_error: read errno = 10054" and don't know why. We check the network adapter and everything is ok. After some time we move the database to a new server and the error is still there.. can you help me in some way?
Thanks
The text was updated successfully, but these errors were encountered: