Highlighted
Honored Contributor.
Honored Contributor.
1695 views

UD: software caused connection abort : recv failed

Jump to solution

Hi,

Test connection using Universal Protcol is throwing an error 

Error: java.net.SocketException: Software caused connection abort: recv failed

Host Connection by Shell job is throwing an below error
UDA: Internal error. Details: java.net.SocketException: Software caused connection abort: recv failed

1. UD Agent service is running fine on target server.

2. Telnet to port 2738 for target server (from probe server) is successful.

 

But still test connection is failing and HCbS job is failing to discover the server. Attached screenshots and communication log for reference.

Note:

1. We also tried for uninstalling and re-installing UD Agent but still the error is same (i.e. java.net.SocketException: Software caused connection abort: recv failed)

2. MF Support case SD02422804 is also raised.

Any help is appreciated!! 

 

Thanks & Regards,

Rohit S

0 Likes
1 Solution

Accepted Solutions
Highlighted
Honored Contributor.
Honored Contributor.

Re: UD: software caused connection abort : recv failed

Jump to solution

Hi,

 

The issue is resolved after

1. System Admin team has configured proper zoning for SAN 

2. Network Admin team has configured proper gateway routes.

 

Thanks & Regards,

Rohit S

View solution in original post

0 Likes
5 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UD: software caused connection abort : recv failed

Jump to solution

You have to check the UDA log on the discovered server to see what's wrong. It may be incorrectly installed certificates for the credentials.

 

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

Likes are appreciated!
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: UD: software caused connection abort : recv failed

Jump to solution

Hi Popadiyski,

Based on suggestion, I checked the logs and found that connection is getting reset(check below logs) by UD Agent even though certificates are installed are same (one which are working for other nodes). Even verified checksum using md5sum, resulting same output is same as one where discovery is working.

#cd /opt/HP/Discovery/bin

#cat nohup.out

SSL request failed, continue with next call...

SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"Error observed by underlying BIO: Connection reset by peer"

Detail: SSL_accept() failed in soap_ssl_accept()

SSL request failed, continue with next call...

 

Any idea, how to resolve this issue.

Note: I have tried with agent reinstallation ( uninstallation and re-installation) but still the same error.

 

Thanks & Regards,

Rohit S

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UD: software caused connection abort : recv failed

Jump to solution

It looks like SSL negotiation fails. When you reinstall the UD, do you physically remove all the installation and config folders from the server? What is the operating system of the server? If it is too old, it may not support the same SSL ciphers as the DFP. This can be verified if you take and read the network traffic dump (with tcpdump or wireshark) from the DFP to the server and see why the SSL negotiation fails. 

 

Petko

Likes are appreciated!
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: UD: software caused connection abort : recv failed

Jump to solution

Hi Petko,

The issue is present on some of Windows 2012 R2 and RedHat Enterprises Linux 7.x servers.

Though SSL negotiation issue is present but its not because of UD Agent.

SSL negotiation was checked using below command from UD probe.

#OpenSSL> s_client -connect server:2738 

and the reponse of above SSL query was write:errno=10054

Further troubleshooting is in progress with Server, Network and Security Admin teams for connection reset/failure. 

Thanks and Regards,

Rohit S

Highlighted
Honored Contributor.
Honored Contributor.

Re: UD: software caused connection abort : recv failed

Jump to solution

Hi,

 

The issue is resolved after

1. System Admin team has configured proper zoning for SAN 

2. Network Admin team has configured proper gateway routes.

 

Thanks & Regards,

Rohit S

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.