I have trouble in configuring High Availability, I searched a lot but I was unsuccessful in fixing it.
I got this error : "An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'."
I have 3 nodes in implementing AlwaysOn , One of them is Domain Controller and the others have implemented as Failover Clustering.
I configured firewall and windows authentication permission for all nodes but I have gotten the error yet.
Does anybody have any solution?
I found it.
my problem was installed same instance name.
Related
Am trying to connect vertica from DBeaver, but am getting below connection error. Initially it was working fine, but suddenly its throwing connection error.
Error Message:
[Vertica][VJDBC](100071) GSS authentication failed due to problems establishing a TGT with JAAS using configuration verticajdbc; reason: Message stream modified (41).
Message stream modified (41)
Message stream modified (41)
I am not able to establish the connection now. Can anyone please help me on it.
The main issue I see with vertica users struggling to connect relate to the drivers used or where the host has changed. Have you updated vertica recently or has there been a change to the host name are just a couple of things you should check.
Sorry I cant be more specific its hard to troubleshoot when I dont have all the information.
Thanks
we are getting ORA-12570: Network Session: Unexpected packet read error from our webapi written in .Net core 2.2. The API is hosted in Alpine Docker OS 3.11 in GCP using kubernetes. We are using Oracle.ManagedDataAccess.Core version 2.19.60.
The intrenal error message we get is
Oracle.ManagedDataAccess.Client.OracleException (0x80004005): ORA-12570: Network Session: Unexpected packet read error ---> OracleInternal.Network.NetworkException (0x80004005): ORA-12570: Network Session: Unexpected packet read error ---> System.Net.Sockets.SocketException (110): Operation timed out.
Per the website http://www.dba-oracle.com/t_ora_12570_tns_packet_reader_failure.htm, ORA-12570 occur due to listener configuration. IS that true? Also Let us know how if tracing works in linux for ODP.Net core.
Thanks
This is a generic error; it is not necessarily related to the Oracle Listener. The key here is "System.Net.Sockets.SocketException (110): Operation timed out." This could be a lot of things; you really need to do Oracle Net tracing to determine what's going on. Could be that your client can't see the network at all, or that network latency or packet routing are not what they should be, or several other things.
An WebMethods instance is trying to connect to the WebSphere server and WebMethods would get the following error:
(Note that the connection has been established before and has worked fine. Just from time to time the following error would show and would be good to know the reason why.)
Exception: CWSIP0471E: Unable to communicate with the messaging engine {a ...} where the destination MonthEndPIOutQueueDestination is Localised... [Linked Exception] com.ibm.websphere.sib.exception.SIResourceException: CWSIC8007E: An exception was caught from the remote server with Probe Id 3-010-0003. Exception: CWSIP0471E: Unable to communicate with the messaging engine {b ...} where the destination { c ...} is Localised..
Thank you for your time
This problem was happening every time there was a WAS restart. and web methods was not able to reconnect without resetting the connection settings.
Solution was to create a process in webMethods that checks every 15 minutes (depending on business requirements) and restarts the connections settings if there is no connection.
I am working on a Windows (Microsoft Visual C++ 2005) application that uses several processes
running on different hosts in an intranet.
Processes communicate with each other using TCP/IP. Different processes can be on the
same host or on different hosts (i.e. the communication can be both within the same
host or between different hosts).
We have currently a bug that appears irregularly. The communication seems to work
for a while, then it stops working. Then it works again for some time.
When the communication does not work, we get an error (apparently while a process
was trying to send data). The call looks like this:
send(socket, (char *) data, (int) data_size, 0);
By inspecting the error code we get from
WSAGetLastError()
we see that it is an error 10054. Here is what I found in the Microsoft documentation
(see here):
WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally
results if the peer application on the remote host is suddenly stopped, the
host is rebooted, the host or remote network interface is disabled, or the
remote host uses a hard close (see setsockopt for more information on the
SO_LINGER option on the remote socket). This error may also result if a
connection was broken due to keep-alive activity detecting a failure while
one or more operations are in progress. Operations that were in progress
fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
So, as far as I understand, the connection was interrupted by the receiving process.
In some cases this error is (AFAIK) correct: one process has terminated and
is therefore not reachable. In other cases both the sender and receiver are running
and logging activity, but they cannot communicate due to the above error (the error
is reported in the logs).
My questions.
What does the SO_LINGER option mean?
What is a keep-alive activity and how can it break a connection?
How is it possible to avoid this problem or recover from it?
Regarding the last question. The first solution we tried (actually, it is rather a
workaround) was resending the message when the error occurs. Unfortunately, the
same error occurs over and over again for a while (a few minutes). So this is not
a solution.
At the moment we do not understand if we have a software problem or a configuration
issue: maybe we should check something in the windows registry?
One hypothesis was that the OS runs out of ephemeral ports (in case connections are
closed but ports are not released because of TcpTimedWaitDelay), but by analyzing
this issue we think that there should be plenty of them: the problem occurs even
if messages are not sent too frequently between processes. However, we still are not
100% sure that we can exclude this: can ephemeral ports get lost in some way (???)
Another detail that might help is that sending and receiving occurs in each process
concurrently in separate threads: are there any shared data structures in the
TCP/IP libraries that might get corrupted?
What is also very strange is that the problem occurs irregularly: communication works
OK for a few minutes, then it does not work for a few minutes, then it works again.
Thank you for any ideas and suggestions.
EDIT
Thanks for the hints confirming that the only possible explanation was a connection closed error. By further analysis of the problem, we found out that the server-side process of the connection had crashed / had been terminated and had been restarted. So there was a new server process running and listening on the correct port, but the client had not detected this and was still trying to use the old connection. We now have a mechanism to detect such situations and reset the connection on the client side.
That error means that the connection was closed by the
remote site. So you cannot do anything on your programm except to accept that the connection is broken.
I was facing this problem for some days recently and found out that Adobe Acrobat Reader update was the culprit. As soon as you completely uninstall Adobe from the system everything returns back to normal.
I spent a long time debugging a 10054/10053 error in s3 pre-signed uploads
Turns out that the s3 server will reject pre-signed s3 uploads for the first 15 minutes of it's life.
So - If you're debugging s3 check it's not a new bucket.
If you're debugging something else - this is most likely a problem on the server side not client side.
we have a dot net application and it connecting to Oracle and fetching data and moving to SQL server. it was working very fine. just started giving error ORA-12560: TNS:protocol adapter error . Tnsping also giving this error. but if i stop this application and tnsping then its success. again starting the application on the first 10 minutes its working perfectly and gain giving same error. every 5 seconds this application connecting to Oracle databse.
any idea what is this error; and how to resolve. there is lots of questions over here,but didnt find a soulution .
highly appreciate your comments against this query
It seems you have some sort of resource leak. Do you close connections properly ?
Also, as ar said in comment, why don't you just keep this connection open ? IIRC Establishing conn is costly operation in any DBMS.
Also, from documentation:
ORA-12560 -- TNS:protocol adapter error
Cause: A generic protocol adapter error occurred.
Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete.
UPDATE:
Problem could be caused by overflow of Windows event journal. Check Oracle's events here:
Start menu => Control Panel => Administrative Tools => Event Viewer
You should either clear journal manually or increase its' size