topic Re: Problem in DB agent installation in Splunk AppDynamics

Problem with DB agent installation

CommunityUser — Tue, 24 Jul 2018 10:48:53 GMT

Hi,

I am trying to install the DB agent in a machine(server) where App agent is running successfully.

But I am getting the below error at the time of DB agent installation

652 ERROR ControllerHttpRequestResponse - Fatal transport error while connecting to URL [/controller/instance/UNKNOWN_MACHINE_ID/systemagentregistration]: java.net.SocketException: Connection reset

Please help me with this.

Thanks,

Bindu

Re: Problem in DB agent installation

CommunityUser — Tue, 14 Aug 2018 19:00:39 GMT

Do you have ssl certificate installed on server? I am guessing it is Digi.cert provided by Appdynamics or you can download it from browser (controller URL)

Thanks

Sandeep

Re: Problem in DB agent installation

jefry_arch — Wed, 06 Jan 2021 06:18:49 GMT

Connection reset simply means that a TCP RST was received. This happens when your peer receives data that it can't process, and there can be various reasons for that. A reset packet is simply one with no payload and with the RST bit set in the TCP header flags. The simplest is when you close the java socket, and then write more data on the output stream. By closing the socket, you told your peer that you are done talking, and it can forget about your connection. When you send more data on that stream anyway, the peer rejects it with an RST to let you know it isn't listening.

There are several possible causes.

The other end has deliberately reset the connection.
Writing to a connection that the other end has already closed.
Closing a socket when there is unread data in the socket receive buffer.
In Windows, 'software caused connection abort', which is not the same as 'connection reset', is caused by network problems sending from your end.

Re: Problem with DB agent installation

Wilfer — Fri, 23 Jun 2023 19:17:45 GMT

Hello everyone,

In my case the same problem, leaving through a proxy, the solution was simple, they enabled the permissions for the PROXY to accept SSL connections without certificates, and it worked perfectly.

I hope it works for you, greetings.